Nobody is born 10x.
They've just seen
this bug before.
So go and see it. A working codebase and a real ticket inside it — a race condition, a stale cache, an N+1 query. Clone it, fix it, open a pull request, get reviewed by a human.
- projects
- 1 projects
- tickets
- 6 tickets
- levels
- 4 levels
- review time
- 24h review time
Coupon discount is calculated incorrectly
Customers report a 10%-off coupon deducts a flat ₹10 instead, whatever the cart size. Support tickets are climbing.
- Applying "SAVE10" removes exactly ₹10 from any cart total
+ Applying "SAVE10" should remove 10% of the cart subtotalAcceptance criteria
- Percentage coupons deduct a percentage, not a fixed amount
- Fixed-amount coupons keep working as before
- The coupon API response shape stays backward-compatible
- A test covers both coupon kinds
Every challenge looks like this
Why this exists
Nobody's job is reversing a linked list.
Puzzle sites train pattern-matching on isolated problems. Real engineering is reading unfamiliar code, forming a theory, and proving it — inside a system you didn't write. That second skill is the entire gap between a good engineer and the one everybody calls when production is on fire.
Whole codebases, not snippets
Services with migrations, caching, queues and the accumulated mess of a system that shipped. The bug is in there somewhere.
Tickets, not problem statements
Business context, observed symptoms, acceptance criteria. Written the way your product manager would write them.
Human review, not a green checkmark
A person reads your diff and tells you what a senior reviewer would have said. Passing tests is the floor, not the goal.
The loop
Four steps, then repeat.
- 01
Pick a ticket
Browse projects by stack and difficulty. Every task reads like a ticket from a real backlog — business context, symptoms, acceptance criteria.
- 02
Download the project
Fork or clone the whole codebase and run it locally in your own editor. No browser IDE, no toy sandbox — the same environment you work in every day.
- 03
Fix it on a branch
Work on a branch named for the ticket, meet every acceptance criterion, add the test. The criteria are the bar, exactly like a real review.
- 04
Get reviewed
Submit your fork URL and branch. A human reads the diff and sends back real feedback, usually within a day.
“10x isn't a personality type.
It's a rep count.”
Progression
Difficulty grows the way the job does.
Every project runs the same four rungs — fix a bug, ship a feature, make it fast, then make it clean. Start where you're comfortable and climb.
$git checkout -b fix/your-first-bug
Pick a ticket.
See how far you get.
Free while we're in early access. No sandbox to fight, no puzzle to reverse-engineer — a real codebase, a real ticket, and a human who reads your diff. Rep one starts here.
- 6 tickets across 1 projects
- Reviewed by a human, usually within a day
- Work locally, in your own editor
- No credit card, no trial timer