Why it matters
A loop is designed to sample different abilities, and candidates who prepare one way for all of them underperform in the rounds that do not match their habit. A strong system design answer does not help in a debugging round where the interviewer wants a hypothesis and a measurement. Knowing the format tells you what to optimise: structure for design, narration for coding, evidence for behavioural, and a written artefact for take-homes.
Mental model
A loop is a portfolio of measurements, each with its own instrument. The metaphor breaks because the instruments are people forming impressions, so the same answer can score differently depending on whether the reasoning was visible to the person holding the instrument.
How it works
Each branch names the stage and the behaviour it scores; a prepared answer does not transfer between rounds.
Step 1 of 6
Ask for the stage list
Write the stage list, duration and tools down before preparing. The format decides what to optimise: structure, narration, evidence or an artefact.
start
Which stage are you preparing for?
Ask the recruiter for the stage list, the duration and the tools allowed, and write them down before preparing. Each stage samples a different behaviour.
Path walked
- Which stage are you preparing for?
Figure. Each stage samples a different ability: narration for coding, structure for design, a hypothesis for applied debugging, evidence for behavioural, and a written artefact for take-homes. The branch names what to optimise, not what to know.
What to notice. The mapping is the page's, not a scorecard; stage lists differ by company and the recruiter's list wins. No duration or weight is drawn because the page names none; “often weighted less” is the page's description, not a measured ratio. The figure does not claim a take-home can be skipped — it claims one stage's preparation does not cover another.
Text version
A decision map from the stage list to what each stage scores. The question asks which stage you are preparing for. The coding branch asks for narration: narrate the decision, not the syntax, because the fundamentals still decide. The design branch asks for requirements, request path, failure and cost, in that order. The applied debugging branch asks for a hypothesis and a measurement before touching the code, because design preparation does not transfer. The behavioural branch asks for three stories with decisions and evidence rather than a list of achievements. The take-home branch is conditional: a written artefact, one signal among several and often weighted below the onsite rounds. Six steps walk the branches, starting with the stage list.
- Ask the recruiter for the stage list, the duration and the tools allowed, and write it down before preparing.
- Map each stage to the skill it samples, then check which of those skills you have never demonstrated aloud.
- For applied rounds, practise reading a broken system and stating a hypothesis before touching code.
- For design rounds, practise requirements, a request path, a failure mode and a cost, in that order.
- For behavioural rounds, prepare three stories with decisions and evidence rather than a list of achievements.
- After each real interview, write the questions you were asked and the answer you gave while it is fresh.
Trade-offs
| Choice | Good for | Cost | Fails when |
|---|---|---|---|
| Broad preparation | Covers every stage | No stage gets deep practice | The loop weights one stage heavily |
| Depth in one area | Strong signal where you are best | A weak stage can veto the loop | The role requires breadth |
| Practice with peers | Realistic pressure and feedback | Scheduling and mismatched levels | Feedback is polite rather than specific |
| Solo rehearsal | Cheap and repeatable | No interruption practice | The round is interactive and you have never been interrupted |
Good for
Covers every stage
Cost
No stage gets deep practice
Fails when
The loop weights one stage heavily
- The loop weights one stage heavily
- The role requires breadth
- Feedback is polite rather than specific
- The round is interactive and you have never been interrupted
Figure. Each choice with what it buys, what it costs, and the case where it loses.
What to notice. The fourth column is the decision: if the losing case describes your situation, the choice is wrong.
Text version
Four trade-offs: Broad preparation is good for Covers every stage, costs No stage gets deep practice, and fails when The loop weights one stage heavily. Depth in one area is good for Strong signal where you are best, costs A weak stage can veto the loop, and fails when The role requires breadth. Practice with peers is good for Realistic pressure and feedback, costs Scheduling and mismatched levels, and fails when Feedback is polite rather than specific. Solo rehearsal is good for Cheap and repeatable, costs No interruption practice, and fails when The round is interactive and you have never been interrupted
Failure modes
- Preparing content only. You know the material and freeze on the format. Debug: time one answer per format and check whether it fits the stated duration.
- Ignoring the applied round. Design preparation does not transfer to debugging a failing system. Debug: rehearse one broken-system scenario end to end and note where you started.
- No record of the loop. The same mistake repeats across companies because nothing was written down. Debug: check whether you can list the last five questions you were asked.
In production
Keep a running log of questions, formats and your answers, and review it before the next loop. Rehearse under time pressure at least once per format.
Common misconceptions
People think: AI interviews are all about model knowledge.
Actually: Loops still weight coding, design and collaboration; domain knowledge is one input among several.
People think: The take-home is the deciding round.
Actually: It is one signal, often weighted less than the onsite rounds, and a strong take-home cannot compensate for a weak debrief.
Interview angle
Asked how you prepare for a loop, the strong candidate names each stage, the skill it samples and the evidence they will bring to it, then says what they would change after a weak round. Weak answers treat every round as a knowledge quiz and never mention the format's mechanics.
Sources
- interviewing.io blog — how real technical loops are structured and scored.
- Will Larson, Staff Engineer guides — the scope signal senior loops are looking for.
- levels.fyi — public data on how level maps to role scope.