01
Capture the raw conversation
Transcript, Otter/Granola export, or detailed notes. Include questions, your answers, and follow-ups.
Guide
A debrief is not “how do I feel?” It’s “what did the conversation show, and what do I practise next?” Use this checklist after every round while the details are still fresh.
By Saadan NaqviLast updated: 13 August 2026
Write down the conversation, mark where the interviewer probed, label answers as strong/mixed/weak, then leave with a tiny action list: 1–2 rewrites and a next-round checklist. That is a real debrief.
01
Transcript, Otter/Granola export, or detailed notes. Include questions, your answers, and follow-ups.
02
Any time the interviewer asked twice, interrupted, or pushed for an example — highlight it. Probes are signal.
03
Strong / mixed / weak is enough. Weak usually means vague ownership, missing result, or no trade-off.
04
Two rewrites to practise, one story to prepare, two questions to ask them. Keep the list short enough to finish tonight.
A probe is any moment the interviewer worked to get something out of you: a repeated question, a “can you give me a specific example,” an interruption, or a follow-up that narrowed the scope. Probes are the most reliable signal in a transcript because they are the interviewer telling you, in real time, that the answer wasn’t finished.
Read what the probe asked for, not just that it happened. “Can you be more specific?” means the answer was abstract. “What did you do?” means you narrated a team. “And what happened?” means you stopped before the result. Each of those points at a different repair, and the probe names which one.
Two probes on the same competency matter more than two probes spread across the interview. If ownership got questioned in both the conflict story and the project story, that’s a pattern in how you tell stories, not a problem with one story.
Strong means the interviewer got a decision, a result, and enough specifics to ask a good follow-up — and their follow-up built on your answer instead of repairing it. Mixed means the content was there but arrived late or needed one prompt. Weak means it stalled, stayed abstract, or ended without an outcome.
Score against what the answer gave the interviewer, not against how articulate you sounded. Fluency is the trap here: the smoothest answers are often the vaguest, because it’s easy to speak confidently about generalities and harder to be precise about a specific decision you made.
Expect most answers to be mixed. A debrief where everything is weak means you’re rating your mood; a debrief where everything is strong means you’re not reading closely. Two or three mixed answers and one weak one is what a normal round looks like.
Close the debrief with a list short enough to finish the same evening: two rewrites, one story to prepare, two questions to ask next time. If the list is longer than that, it won’t get done, and an unfinished debrief is worth about as much as no debrief.
Keep the debriefs. Four rounds in, the pattern across them is more useful than any single one — the same competency going soft three times is the thing to actually fix, and you can only see it by comparing.
No transcript to work from yet? See how to get an interview transcript first. Once you’ve scored each answer, rewrite the weak ones with a clear decision, trade-off, and result so the next round actually changes.
Iteration turns a transcript or detailed notes into a private Interview Review: signal read, weak-answer rewrites, practice drills, and next-round prep. Start with a free preview — no account required.
20–40 minutes is enough if you stay concrete. Longer usually means rumination, not analysis.
Evidence from the conversation, specific rewrites, and a short practice plan. Not vibes and not fake offer odds.
Start alone with notes so you don’t lose the details. A peer can help later — after you’ve named the soft answers.
Yes, and it takes ten minutes. A good round still usually contains one probe worth reading. It’s also the only way to learn what your strong answers have in common, which is harder to see when you only ever review the bad ones.
Write the competency instead of the wording — “asked about a conflict with a senior engineer” is enough to work from. Reconstruct in the order the conversation went, since sequence tends to jog the parts you’ve lost.
It turns your transcript or notes into a private Interview Review with signal read, rewrites, drills, and next-round prep.
More guides