How to Read Mock Interview Feedback (and Actually Improve)

Doing a mock interview and reading the score is about a third of the value. The other two thirds are in what you do with the feedback, and most people do the same two things with it: feel briefly bad about the number, and book another session. That loop can run for twenty sessions without producing much improvement.

The score is the least useful part

A single number compresses forty-five minutes into one dimension, which means it can tell you that something went wrong but never what. Two candidates can score identically because one could not find the algorithm and the other found it in four minutes and then never explained it. Those require opposite interventions.

Read the score once, then ignore it. Everything actionable is in the transcript.

The four-pass review

This takes about twenty minutes and is the highest-return time in the whole practice loop. Each pass looks for one thing only, because looking for everything at once means finding nothing.

Notice that three of the four are habits rather than knowledge. Habits change quickly once you can see them, which is why this review typically produces a visible improvement within two or three sessions while more problems produce none.

"It is not the strongest of the species that survives, but the most adaptable to change."
- Leon C. Megginson, paraphrasing Darwin (1963), often misattributed to Darwin himself

Change one thing per session

The temptation after a bad session is to fix everything at once: talk more, clarify better, test properly, manage time. Attempting four changes under pressure reliably produces four partial changes and one worse session, and then the sense that practice is not working.

Pick one. Carry it into the next session as a single sentence you can hold in your head, like "narrate before typing". When it happens without effort, pick the next one. Four sessions, four habits, all of them permanent.

Read across sessions, not within them

A single session tells you about a single question. Five sessions tell you about you. Keep a two-line note after each one and the repeated word will be obvious by the fifth: always clarifying too little, always going quiet at the same point, always running out of time in the last ten minutes.

When to dismiss feedback

Not all of it is right, and treating every piece as gospel is its own failure mode. Feedback that names a moment in the transcript is usually worth acting on. Feedback that is generic advice which could apply to any candidate on any question is worth noting and no more.

The useful test is whether you can point at the line it refers to. "You should communicate more" fails that test. "At minute nineteen you switched approaches without saying why" passes, and you can do something about it tomorrow.

The improvement is not in the sessions

Sessions generate evidence. Review turns evidence into a change. Doing the first without the second is how people arrive at their thirtieth mock interview with the same three habits they had at their first, and conclude that practice does not work for them.

Twenty minutes of reading, one habit carried forward. That is the whole method, and it is worth more than doubling the number of sessions.