Why these rounds exist
An algorithm interview tests whether you can solve a well-defined problem in a fixed amount of time. It says less about whether you can work inside code you did not write, which is most of what the job actually involves.
A real-world round hands you something closer to the job itself: an existing project, a scoped task, and a limited amount of time to make a defensible change.
The three formats
- Bug fix: you get a codebase with a failing test and a description of what is wrong. You reproduce the error, trace it, and fix it while explaining your reasoning.
- Add a feature: you get a working app and a small, scoped request, like adding pagination to a list component. You read the existing patterns in the code before you add your own.
- Take-home plus review: you build something over a few hours on your own time, then defend the choices you made in a live conversation. The finished code matters less than your answers about why you wrote it that way.
How to prepare
Get comfortable reading code you did not write. Open an unfamiliar repository, pick a function, and explain out loud what it does before you run it. Know your way around your editor's debugger and Git well enough that neither one interrupts your train of thought.
CodeSparring's debugging rounds put you in a real codebase with a failing test that a verified pack runs against your fix, and its case labs cover forward-deployed engineering work like a 911 dispatch system, an ontology build, and a Stripe billing webhook. See what a full round looks like before you start one.