Updated 2026-09-04

How to Debrief After an Interview (Candidate Side)

How to debrief after an interview, on your side of the table, is a twenty-minute note written the same day. Write down the questions and the story you used for each. Mark the claims that had no number under them. Pick two things you'll say differently next time.

Hiring panels also call their private sit-down a debrief. You won't be in that room. Send the thank-you if you want — it just doesn't belong on this page.

What to write down

Fill a table while you still remember the wording. The "how it felt" paragraph writes itself later. Next Thursday you need the wording.

DimensionWrite thisMost people write this
The questionAs close to verbatim as you canThe topic ("leadership")
Your first sentenceThe line that actually came outThe story you meant to tell
The exampleWhich one, in a few words"I talked about the rewrite"
The result you statedA number, a decision, a thing that shipped — or a blankThe activity ("I led it")
Their follow-upThe next question they askedNothing. People forget this was the interview
What you asked themWhat left your mouthThe list still sitting in your notes app
FixesOne content, one structureA verdict on how it went

The follow-up column is the one that pays. If they asked again, your first answer didn't land. Faces are a lousy source for that.

Stay on stuff you can check. "I said we cut churn 12%" has a fact under it. "They seemed unimpressed" is you narrating a face, and you can't rewrite a face.

What vanishes by evening

By 10pm you still remember the bit where you sounded sharp. The ninety seconds of setup in front of it has usually gone. The rows below are the ones that actually change the next loop, and they're the first to fade.

Easy to loseWhy it is worth writing down
The exact questionYou remember the topic. They asked a narrower thing.
Your opening lineThat is what they heard while deciding whether to keep listening.
Their follow-upThey asked it because the first answer was not enough.
A claim with no number"We improved retention" sounds finished. There's no number under it.
The question you never askedYou ran out of time on the only part you control.
Names, team, timeline they mentionedRound two will assume you still have these.
The example you swallowedUsually the one you should've used.
How long you talked before the pointMemory keeps the sharp bit and drops the setup.

If you can't recall the questions an hour later, stop there. That's already the finding, and it'll still be true next Thursday.

Twenty minutes, same day

Open a note before you reopen the careers page and dump the table first. The two fixes come after, once you've got the wording down.

Skip the neat write-up for a minute. In the lobby, or walking to the car, talk the questions out loud into your phone or your Watch for sixty seconds. Don't polish it. You're still close enough to the wording that a messy sixty seconds will hold.

If the next loop is tomorrow, two fixes are enough. If you've got a week, rewrite the weak story into a tight paragraph and say it twice.

Two fixes

If you write down twelve things you did badly, you'll just feel worse. Pick one content fix and one structure fix, then say the new version out loud once, badly.

Content: swap one vague story for one with a situation, an action, and a result you can state as a number.

Structure: land the result in 60 to 90 seconds and stop. Or get your questions out before the call starts winding down.

Otherwise you walk in next time and tell the same mushy story again.

The standing instruction

Your memory plays favorites. A mock transcript still has the throat-clearing, which is why you capture a practice round. A real interview only if they said yes.

Run the mock with a friend or a coach. Start with one tap on the Watch so nobody's got a laptop open between you. Phone's fine if that's what's in your hand. Nothing starts on its own. Afterwards read the words that came out. The version in your head is always cleaner. You'll see whether you opened with the result or buried it, whether you named the number, whether you asked about team priorities or just… didn't.

Don't re-read the whole transcript every time. Write the extract once as a Skill, in ordinary language, and run it after each mock. Add your planned-question list when you run it if you want that check; a transcript can't recover a list you never said out loud. Output is Markdown or a PDF.

After each mock interview, use only the transcript and any "Planned questions" list in my message. List every question I was asked, as close to verbatim as the transcript allows. For each one, note the example I used, whether I stated a number, a decision, or a thing that shipped, and the first sentence of my answer. Flag where I answered a different question, used more than about 200 words before the result, or made a claim with no number. Report the word count; do not claim an exact speaking duration. If I included a "Planned questions" list, compare it with the transcript and list any I did not ask. If I did not include one, write "Planned-question check unavailable." Two fixes only — one content, one structure. Markdown. Do not grade my tone, my confidence, or whether I got the job.

If you haven't made a Skill yet, the same questions work as a one-off in Chat:

List every question I was asked and the example I used for each.

Where did I claim a result without a number?

Planned questions: [paste the list]. Which of these did I never ask?

Read the sheet once for structure before you start judging. In a mock, "tell me about a time you disagreed with your manager" often spends ninety seconds on background before the disagreement. Easy to miss if you're going on vibe. The full transcript is on app.pastok.com, which is where you check a line before you treat it as yours.

Speaker labels can be wrong in a two-person mock. Read the line.

What this will not tell you

Nobody can tell you if you got the job from a recording, including this. It also can't grade your tone. Don't record a real interview unless they agreed — ask first; how to ask permission to record a meeting is the practical version. A voice memo is plenty if you only needed two questions from a screen.

Practice the debrief on a mock

Run one mock, capture it, and leave with two written fixes before your next real loop.

Try Pastok

Related

Practice the debrief on a mock

Run one mock, capture it, and leave with two written fixes before your next real loop.

Try Pastok