Interview Round Debrief
When To Use
You walked out, wrote nothing down, and gave the same weak answer in the next loop. Use this within a day of any round, while you still remember the wording of the questions. It answers: what did I learn in that room, and what changes before the next one?
When Not To Use
This holds what you learned; the status of the process and its next step live in Job Search Tracker. For practice before a round, run Mock Interview. If the round was more than a few days ago, a shorter pass is still worth it, marked as partial.
Inputs
- Your memory of the round: the questions, your answers, the follow-ups, typed or spoken as rough notes
- The row for this round from your Interview Loop Map, and your Interview Story Bank so changes land on named story IDs
If you have none of this, I start from the three questions you remember best and mark the output as a first draft.
Approach
The What, So what, Now what reflective model, as set out in the University of Hull Library guide to reflective writing, keeps a debrief from becoming a mood report: first what happened, then what it means, then what you will do. The judgment is that "So what" is your view and stays your view. I do not guess what the interviewer thought and I give no verdict on how it went. The failure this prevents is three loops in which the same story about the same launch gets the same puzzled follow-up, because nobody wrote the follow-up down.
Workflow
- Ask at most three questions, then go one prompt at a time: which round this was and with whom, by name and role; which questions you remember, in order; and whether you promised to send anything.
- What: for each question, the story or answer you gave, the follow-ups, and anything the interviewer said about the role or the process. Their words go in only as you remember them; a gap is written "not recalled".
- So what: per answer, whether it landed or did not, in your own view, with the reason you think so (a follow-up that showed interest, a question you could not close, time running out). No number, no overall verdict.
- Now what: changes to named story IDs, a gap to fill in your Career Evidence Inventory, one thing to practise aloud, new questions for the next round, and the updates for the loop map and the tracker.
- Promises: every item you said you would send (a link, a reference, a date) with a due date.
- Thank-you points, two or three, for a message sent within a day or two: thanks that names the conversation, one specific thing you discussed and what you took from it, and any promised item. No second ask and no re-arguing an answer. You write it and send it.
Output Format
# Interview Round Debrief
**Process:** [role] · **Round:** [round name] · **Date:** [date] · **Interviewer:** [name, role] · **Written:** [date, from memory]
## What was asked
| # | Question as you remember it | Story or answer you gave | Follow-ups | What they said about the role or process | Landed, in your view | Why you think so |
|---|---|---|---|---|---|---|
| 1 | [question] | [story ID or answer] | [follow-up] | [their words, or not recalled] | [landed / did not land / unsure] | [what you saw or heard] |
## What to change
| Change | Where | By when |
|---|---|---|
| [Edit to story [ID]] | Interview Story Bank | [date] |
| [Evidence gap, one thing to practise aloud, a new question for the next round, loop map and tracker updates] | [where] | [date] |
## Promises made
| What you said you would send | To whom | Due |
|---|---|---|
| [item] | [name, role] | [date] |
## Thank-you points
1. [Thanks, naming the conversation and the day]
2. [One specific thing you discussed and what you took from it]
3. [The promised item, if any]
## Decision
You decide which story changes to make before the next round and send the thank-you yourself, by [date].
Done When
- Every remembered question has the answer you gave beside it
- "Landed" holds your view and a reason, with no guess at the interviewer's opinion, and each change names a story ID or a place with a date
- Every promise has a due date, and the thank-you points name one real thing from the conversation
Quality Bar
- Written within a day where possible and dated as written from memory; recording an interview raises consent and legal questions, so check with a qualified adviser
- Interviewers appear by name and role only, with no judgement of them as people
- Nothing rates you or the round, and the thank-you is points with no second ask, not a finished message
- The debrief records what really happened in your words; you write the thank-you yourself, and nothing is put in the interviewer's mouth.
Next
Run pmjob-search-tracker (Job Search Tracker) to update the process and pick the next action.
About the makers
This pack is made by 90n (90n.ai): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).
1---2name: pmjob-round-debrief3description: Captures an Interview Round Debrief within a day of a round, with what was asked and what you answered, what landed and what did not in your own view, the promises you made, the changes to your stories, and points for a short thank-you that names one thing from the conversation. Use for "run pmjob-round-debrief", "debrief my interview", "notes after the interview", "what did they ask me", "thank-you after an interview", "what to change before the next round", "I just finished a round", "interview follow-up points", part of the Claude Guide for Product Interviews Pack by 90n.4metadata:5 source: https://skillmd.com/skills/polar-bear-org/pmjob-round-debrief6---78# Interview Round Debrief910## When To Use11You walked out, wrote nothing down, and gave the same weak answer in the next loop. Use this within a day of any round, while you still remember the wording of the questions. It answers: what did I learn in that room, and what changes before the next one?1213## When Not To Use14This holds what you learned; the status of the process and its next step live in Job Search Tracker. For practice before a round, run Mock Interview. If the round was more than a few days ago, a shorter pass is still worth it, marked as partial.1516## Inputs17- Your memory of the round: the questions, your answers, the follow-ups, typed or spoken as rough notes18- The row for this round from your Interview Loop Map, and your Interview Story Bank so changes land on named story IDs19If you have none of this, I start from the three questions you remember best and mark the output as a first draft.2021## Approach22The What, So what, Now what reflective model, as set out in the University of Hull Library guide to reflective writing, keeps a debrief from becoming a mood report: first what happened, then what it means, then what you will do. The judgment is that "So what" is your view and stays your view. I do not guess what the interviewer thought and I give no verdict on how it went. The failure this prevents is three loops in which the same story about the same launch gets the same puzzled follow-up, because nobody wrote the follow-up down.2324## Workflow251. Ask at most three questions, then go one prompt at a time: which round this was and with whom, by name and role; which questions you remember, in order; and whether you promised to send anything.262. What: for each question, the story or answer you gave, the follow-ups, and anything the interviewer said about the role or the process. Their words go in only as you remember them; a gap is written "not recalled".273. So what: per answer, whether it landed or did not, in your own view, with the reason you think so (a follow-up that showed interest, a question you could not close, time running out). No number, no overall verdict.284. Now what: changes to named story IDs, a gap to fill in your Career Evidence Inventory, one thing to practise aloud, new questions for the next round, and the updates for the loop map and the tracker.295. Promises: every item you said you would send (a link, a reference, a date) with a due date.306. Thank-you points, two or three, for a message sent within a day or two: thanks that names the conversation, one specific thing you discussed and what you took from it, and any promised item. No second ask and no re-arguing an answer. You write it and send it.3132## Output Format33```markdown34# Interview Round Debrief35**Process:** [role] · **Round:** [round name] · **Date:** [date] · **Interviewer:** [name, role] · **Written:** [date, from memory]36## What was asked37| # | Question as you remember it | Story or answer you gave | Follow-ups | What they said about the role or process | Landed, in your view | Why you think so |38|---|---|---|---|---|---|---|39| 1 | [question] | [story ID or answer] | [follow-up] | [their words, or not recalled] | [landed / did not land / unsure] | [what you saw or heard] |40## What to change41| Change | Where | By when |42|---|---|---|43| [Edit to story [ID]] | Interview Story Bank | [date] |44| [Evidence gap, one thing to practise aloud, a new question for the next round, loop map and tracker updates] | [where] | [date] |45## Promises made46| What you said you would send | To whom | Due |47|---|---|---|48| [item] | [name, role] | [date] |49## Thank-you points501. [Thanks, naming the conversation and the day]512. [One specific thing you discussed and what you took from it]523. [The promised item, if any]53## Decision54You decide which story changes to make before the next round and send the thank-you yourself, by [date].55```5657## Done When58- Every remembered question has the answer you gave beside it59- "Landed" holds your view and a reason, with no guess at the interviewer's opinion, and each change names a story ID or a place with a date60- Every promise has a due date, and the thank-you points name one real thing from the conversation6162## Quality Bar63- Written within a day where possible and dated as written from memory; recording an interview raises consent and legal questions, so check with a qualified adviser64- Interviewers appear by name and role only, with no judgement of them as people65- Nothing rates you or the round, and the thank-you is points with no second ask, not a finished message66- The debrief records what really happened in your words; you write the thank-you yourself, and nothing is put in the interviewer's mouth.6768## Next69Run pmjob-search-tracker (Job Search Tracker) to update the process and pick the next action.7071## About the makers7273This pack is made by 90n ([90n.ai](https://90n.ai)): AI-native ways of working and tools for Product, Marketing and HR teams, built by ex-McKinsey founders. We map where time and money leak, redesign the work around AI and stay until your people run it themselves, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).