Skip to content
AI InterviewSearch…Search problems, topics, or pages…Ctrl KGet started

Debugging practice

Bug hunts: debugging challenges on real code

Trace the failure, find the root cause, ship the fix.

bugs in the catalogue bugs fixed remain

Frontend

UI state, async races, validation

Backend

APIs, auth, incidents that made headlines

Database

Queries, consistency, caching

Bug hunts: debugging challenges on real code

Fix more than 300 real, broken projects in JavaScript, Python and Java: a bug report, the code as shipped, and hidden tests that judge your fix. Free to read.

What is a bug hunt on CodeKairo?

A bug hunt is a debugging exercise on real code. You get a small project as it shipped — in JavaScript, Python or Java — and a bug report that says what is wrong, not where. You read the code, find the fault and fix it in the editor; hidden tests decide whether the fix is complete, and a partial fix shows as a partial pass count. There are more than 300 hunts, tagged by category (frontend, backend, database) and difficulty. A complete fix pays 50 XP and keeps your streak alive. Any hunt can be read without an account. From 1 January 2027, the Free plan allows one hunt a day.

Browse by language

  • JavaScript 190 hunts · 53 easy · 97 medium · 40 hard
  • Python 66 hunts · 20 easy · 37 medium · 9 hard
  • Java 55 hunts · 15 easy · 26 medium · 14 hard

Browse by layer

Every bug hunt

JavaScript (190)

Python (66)

Java (55)

How it works

  1. Read the report. Every hunt opens with the bug report and the project files. No line numbers, no hint about where — finding it is the exercise.
  2. Trace and fix. Edit the files in the workspace. The tests are hidden; run them as often as you like to see how many pass.
  3. Submit the fix. A complete fix awards 50 XP, counts as an active day for your streak and appears in your submission history with the code you sent.

Who it is for

Developers who want the skill interviews and jobs actually test — reading and reasoning about someone else's code — rather than another blank-function exercise.

Frequently asked questions

How is a bug hunt different from a challenge?
A challenge gives you a signature and asks for an implementation. A hunt gives you an implementation that already exists and asks what's wrong with it. The skill it trains is reading and reasoning about someone else's code.
Are the tests visible?
No. You see the bug report and the code. Hidden tests decide whether your fix is complete — partial fixes show as a partial pass count.
Can I filter hunts?
By difficulty and by category, so you can deliberately practise the kind of bug you're worst at.
Do hunts affect my rating?
Yes. The first complete fix of a hunt pays 50 XP and adds 50 to your rating, and it keeps your streak alive for the day. Fixing it again is practice and pays nothing more.