The task
You just walked out of an interview. The next one is in 4 days. You have 30 minutes and your messy notes. You need a debrief that tells you exactly what to fix — not a feel-good summary.
When this is the right job for AI
- You took at least 10 lines of notes during or right after the interview.
- You can name 1-2 questions you fumbled.
- You want structured feedback, not therapy.
If you didn’t take notes, the next 4 days will be more useful spent on prep than reconstruction.
What to feed the AI
- Company + role + round number (“3 of 5, system design”)
- Topics covered (5-10 bullets, exact wording where possible)
- Questions you felt strong on
- Questions you fumbled, with what you actually said
- Any specific feedback the interviewer dropped
- Your read on the interviewer’s engagement (asked follow-ups? checked phone?)
Copy-ready prompt
You are debriefing a job interview round to find the 2-3 things to fix before the next round.
Round: 3 of 5, system design, target role: Senior PM, Acme Cloud
Topics covered:
- Design a quota / billing system
- How to prioritize the first 3 features
- How to communicate trade-offs to engineering
- Behavioral: tell me about a time I disagreed with eng
Felt strong: trade-off communication, behavioral
Fumbled: prioritization (I jumped to features without framing user impact); the answer on "what would you ship first" went 4 min
Interviewer feedback dropped: "interesting framing on quota" + "let’s come back to the prioritization question" (which we didn’t)
Engagement: leaned in early, looked at notes during my long answer
Write:
1. The single biggest issue. One line. Direct.
2. Two fixable patterns (not "be more concise" — pattern level).
3. The exact thing to drill before round 4.
4. The story I should pre-build now in case it comes up again.
No "you did great" framing. Treat me like a peer who asked for honest feedback.Sample output structure
- Biggest issue: you bypassed framing on prioritization. The interviewer wanted to see your decision process; you gave them an answer.
- Patterns to fix:
- When the question is “how would you prioritize”, start with the framework you’re going to use (e.g. impact × effort × strategic fit). Do not skip to the conclusion.
- The 4-minute answer is a signal you didn’t check the interviewer’s eyes. After 90 seconds, pause and ask “want me to keep going or take a different angle?”
- Drill before round 4: practice 3 prioritization scenarios out loud with a 90-second cap and a forced framework step.
- Pre-build: “a time I changed my mind on a feature priority” — your prioritization answer needs a story to anchor the framework.
How to refine
- AI too soft → add: “this is honest feedback, not encouragement. Be willing to say
you missed a question.” - Output too generic → strict rule: “every fix must reference something specific the interviewer said or did.”
- Missing pattern level → add: “do not say
be more concise— name the conversational habit that produced the 4-minute answer.”
Common mistakes
- Debriefing only the things that went wrong. The strong moments tell you what to repeat.
- No timeline. “Fix this eventually” doesn’t survive the next 4 days.
- Skipping the interviewer signal column. Engagement cues are 50% of the data.
- Letting AI list 8 things. Two patterns is the realistic upper bound for what you can actually fix in 4 days.
Practical depth notes
For AI Interview Debrief: Pull Lessons Out of a Round Within 30 Minutes, the difference between a usable AI result and a generic one is the input packet. Give the model the audience, the current draft or raw material, the desired format, the decision you need to make, and two examples of what good and bad output look like. Ask it to preserve facts first, then improve structure or wording second.
After the first response, do a separate review pass. Look for missing constraints, invented details, weak calls to action, and language that sounds plausible but does not match the real situation. The best final output should be easy to use immediately: clear owner, clear next step, and no hidden assumption that someone else has to untangle. A stronger version of this workflow also defines the handoff. Decide who will use the output, what they should do next, and what information would make them reject it. If the deliverable is copy, test whether it has a single clear action. If it is analysis, test whether it separates observation from recommendation. If it is planning, test whether dates, owners, and tradeoffs are explicit enough for someone else to execute.
FAQ
- How long after the interview should I do this? Within 90 minutes — before your memory smooths the rough edges out.
- Should I share the debrief with the recruiter? No. The debrief is for you. The recruiter gets a thank-you note, not a self-assessment.
- Can I use this for the final-round debrief too? Yes — same template, swap “fix before next round” with “pre-decision reflection”.
Related
- AI behavioral interview prep
- AI mock interview
- AI tell-me-about-yourself practice
- AI thank-you email after interview
- Interview Debrief Prompts for Lessons From Every Round
Tags: #AI writing #Job search #Interview #Interview prep #Story bank