5 Interview Mistakes You Only Notice When You Review the Recap

Most of us prepare for interviews the same way: read a list of common questions, write a few answers, and hope they come out right on the day.

The problem is that you never find out how they actually came out. The call ends, you feel "okay-ish", and a week later you get a rejection with no feedback.

A simple habit fixes this. After every interview and mock interview, write down three things:

What was I asked?
What did I actually say?
What should I have said?

Do this a few times and the same mistakes start showing up. Here are the five most common ones, plus fixes that work.

1. Giving the result last

Behavioral questions like "Tell me about a time you missed a deadline" have a natural story order: situation, what I did, what happened. The trouble is that interviewers stop listening halfway through the setup.

Fix: say the result first, in one line. "We shipped two days late, but the client renewed, and here's how." Then tell the story. The interviewer now knows where you're going and listens for the how.

2. Drawing boxes before saying numbers

In system design rounds ("Design a URL shortener"), many candidates jump straight to drawing a load balancer, app servers and a database.

Interviewers want to hear the scale first: how many reads, how many writes, how much storage per year. Without numbers, every box looks like a guess.

Fix: spend the first two minutes on scale and say the numbers out loud. Reads per second, writes per second, storage. Then design.

3. Answering the question you prepared, not the one asked

When a question sounds like one you've practiced, it's tempting to play back the prepared answer, even when the follow-up is slightly different. "Why do you want to leave your job?" is not the same as "What would make you stay?"

Fix: repeat the question back in your own words before answering. It buys you three seconds and forces you to listen.

4. A "Tell me about yourself" that runs for three minutes

More detail feels more impressive. In reality the interviewer wants a 60-second map: who you are now, the one or two things you're best at, and why this role.

Fix: write it, time it, cut it to under a minute. Present, past highlight, why this job.

5. No good question at the end

"Do you have any questions for us?" Answering "No, I think you covered everything" is a missed chance.

Fix: keep two real questions ready. "What does the first 90 days look like for this role?" and "How does the team handle on-call / deadlines?" both work.

How to build this habit without a lot of effort

Writing these notes by hand after every call is tiring, and you forget half of what was said within an hour. A few ways to make it easier:

Record your mock interviews (with permission) and listen back at 1.5x speed.
Use a simple template: three columns, asked / said / should have said.
Use a tool that does the recap for you. Disclosure: I work on ClapAssist, a desktop app for Mac and Windows built for exactly this. It has a practice mode, and after each session it gives a recap: what you were asked, how you answered, and what to fix before the next round. It also works for regular work meetings and client calls, which is handy when you want notes without typing during the call.

Whatever method you pick, the important part is closing the loop. An interview you don't review is practice you threw away.