How to debrief a tech rejection in 10 minutes (checklist)

Most engineers don't debrief rejections. They ruminate.

Rumination feels like work. It isn't. A debrief is short, structured, and ends with one action.

Here's a 10-minute checklist you can run after every tech rejection—whether the email said "we went with other candidates" or you simply got ghosted after the final round.

Before you start (30 seconds)

• Open a note titled: Rejection — [Company] — [Role] — [Date]
• Paste the rejection email if you have it
• Set a 10-minute timer. Stop when it rings.

Minute 1–2: Capture facts only

No emotion. No storytelling. Fill these blanks:

• Company / role / level applied
• Source: referral / cold apply / recruiter outbound
• Last stage reached: OA / phone / onsite / HM / offer stage
• Dates of rounds
• Rejection channel: email / portal / ghost
• Exact wording (if any)

If you can't name the last stage, your tracker is broken. Fix that after the timer—not during.

Minute 3–5: Round-by-round memory dump

For each round, write one line max:

• Round — what was tested — where I felt weak — interviewer signal
• Example: DSA screen — graphs/BFS — slow to pick DS — had to hint twice
• Example: System design — chat system — no capacity math — asked "how many servers?"
• Example: Behavioral — conflict story — vague "we" — follow-up: "what did YOU do?"

Prompts if memory is fuzzy:

• Where did I go silent?
• What question did I hope they wouldn't ask?
• What would I redo if I had 10 more minutes in that room?

Minute 6–7: Force a diagnosis (one sentence)

Complete this template:

I most likely lost at [stage] because of [specific skill/signal]. Evidence: [1 concrete moment].

Good examples:

• I most likely lost at system design because I never estimated QPS. Evidence: interviewer asked twice about scale; I waved hands.
• I most likely lost at HM because leveling was unclear. Evidence: my stories were task execution, not scope ownership.

Bad examples:

• "They had a better candidate." (Unfalsifiable. Useless.)
• "I'm bad at interviews." (Too broad to drill.)
• "Bias / unlucky." (Maybe true sometimes—still need a controllable next step.)

Minute 8–9: Pick ONE drill for the next 48 hours

Only one. Circle it:

• 2 timed DSA problems out loud on my weak pattern
• 1 full system design with numbers on paper
• Rewrite 3 behavioral stories for ownership + metrics
• Rewrite top resume bullets (kill ticket language)
• Mock focused only on the weak round
• Study target company's actual round shape before applying again

Write the drill as a calendar block. If it's not scheduled, it's a wish.

Minute 10: Close the loop

Answer three yes/no questions:

1. Is this diagnosis written down somewhere I'll see it next week?
2. Is the drill scheduled in the next 48 hours?
3. Am I applying to the next company with a different prep focus than last time?

If any answer is no, use 2 more minutes. Then stop. Do not reopen the wound tonight.

Copy-paste checklist (save this)

REJECTION DEBRIEF (10 min)

• Company:
• Role / level:
• Last stage:
• Rejection note:
• Round notes: 1) 2) 3)
• Diagnosis (1 sentence): I most likely lost at ___ because ___. Evidence: ___.
• One drill (48h): __________________ @ date/time ____
• Tracker updated: Y/N
• Next application only after drill starts: Y/N

Weekly pattern review (extra 10 minutes on Sundays)

Once you have 3+ debriefs:

• Which stage appears most often as the kill shot?
• Is the same skill showing up across companies?
• Are you over-indexing on DSA when design/behavior is the real leak?

Patterns beat feelings. Your third rejection is more honest than your first.

Common debrief mistakes

• Writing a novel. If it takes an hour, you won't do it next time.
• Blaming only the company. Keep a controllable lever even when process is messy.
• Five drills. One deep fix beats a chaotic self-improvement binge.
• Skipping happy paths. Also note what went well—so you don't "fix" strengths in panic.

When you want the debrief done for you

If opening a doc after every rejection still feels heavy, that's the job of PortLume's Rejection Autopsy Agent: when a rejection hits your inbox, it already knows the company, role, and stage from your tracker—and sends back a round-by-round diagnosis without you pasting context twice.

Agentic, to us, isn't "faster when you ask." It's "done before you had to ask."

Try it on your last rejection: Run a free interview debrief.

Related:

• What "we went with other candidates" means
• 5 non-coding reasons engineers fail loops