How to get feedback from an interview transcript

Memory edits the story. Transcripts keep the awkward pauses, the second probe, and the answer that never landed the result.

If you only remember “it felt okay,” you will prep randomly. If you can see the probe, you know exactly which story to rewrite tonight.

Read the interviewer’s lines first, on their own. Skip your answers entirely on the first pass and read only what they said. Their questions and follow-ups are a compressed record of what they were assessing and where they didn’t get it — and reading them separately stops you from getting absorbed in defending your own answers.

Find where you started talking. In a weak answer, the first sentence is usually throat-clearing: restating the question, setting up context, or hedging. Note how many seconds pass before you say anything the interviewer could evaluate.

Mark every question you answered with a category instead of an instance. “I’m collaborative” is a category; “I disagreed with the staff engineer about the retry policy and here’s what I did” is an instance. Interviewers ask for instances, and categories are the most common way a fluent answer fails.

Check who the verbs belong to. Count how often you say “I decided,” “I chose,” or “I pushed for” against how often you say “we.” The ratio is usually more lopsided than it felt at the time.

A tagged transcript is not yet feedback — it becomes feedback when it produces something you will rehearse tonight. Convert each weak tag into one concrete change: a missing result to add, a “we” to replace, an opening to cut.

Rank by what will recur, not by what stung most. An answer about a competency central to the role will almost certainly come up again in the next round; one about a niche technical detail probably won’t. Rewrite the recurring one first.

Cap the plan at two rewrites. This is the step where most people over-commit, and a plan of eight rewrites reliably becomes a plan of zero.

Delivery isn’t on the page. A transcript records what you said, not the pace you said it at, and an answer that reads well can still have landed flat. Treat the text as evidence about content and structure, and get a second opinion on delivery from a mock round or a recording you listen back to.

Neither is the bar. A transcript shows how your answer compares to a good answer; it can’t show how it compared to the other four candidates that week. That’s why “this was a solid answer” and “this was the strongest answer they heard” are different claims, and only the first one is knowable from your own text.

It also won’t show what was decided before you spoke. Interviewers arrive with a hypothesis from your CV, and some questions are there to confirm it rather than to explore. If a whole section of the conversation feels oddly narrow, that’s usually why — and no amount of rewriting that answer changes it.

See how to get an interview transcript from Otter, Granola, Zoom/Meet exports, or same-day notes. Once you have it, the debrief checklist turns that feedback into a short, specific practice plan.