The interview is a tree: resolve the upstream decision before the ones that depend on it, and each branch is worked through until it’s marked “decided” or flagged with an owner.
Trail map
Detailed content
🎤 Anatomy of a relentless interview
How the method works: sequentially, with a recommended answer, dependency tree, exploration before asking, flags with owners, checkpoint, backstop, and final reconciliation.
The interviewer asks one question per turn and waits for the answer before continuing—they never fire off five at once.
Serial keeps the focus on resolving one decision at a time and doesn't overwhelm you.
1 per turn · focus · conversation pace.
For each question, the interviewer already suggests the best answer it can infer from the context, so you only have to confirm, correct, or redirect.
Reduces the effort of answering from scratch and speeds up the entire session.
Suggested answer · low friction · best guess.
Resolve the upstream decision before the ones that depend on it, and follow each branch all the way through without skipping.
Making downstream decisions before upstream ones creates rework — order matters.
Dependency order · branch by branch · upstream first.
If the answer is in the code, a file, or a doc you provided, the interviewer reads it instead of asking—and only brings up what's new.
Asking about what's already written down wastes your attention on what matters.
Don’t ask the obvious · read first · only ask what’s new.
When you don’t know the answer, the question becomes a flag with the right owner ("cost table → finance"), and the session continues.
Not knowing can’t stall the interview—record it and move on.
Flag · owner · avoid stagnation.
After each answer, before the next question, append the entry to the capture file; fix the past if something changes; never in batches.
It’s what ensures nothing gets lost when the context fills up.
Immediate append · correct the past · loss-proof.
Near the end, the interviewer offers a safety net: "Is there any aspect we haven't covered?".
Capture what the decision tree didn't reach—the last gap.
Safety net · coverage · intentional ending.
In the end, the entire capture is reread to look for contradictions and gaps, reconcile them, and give a recap: what was captured, what was flagged, and the next step.
Make sure the final document is coherent, not a patchwork.
Review · reconcile · final recap.