How to Practice for a Job Interview (Out Loud, Not in Your Head)

There's a specific failure mode in interview preparation: you read a list of common questions, think through roughly what you'd say for each, feel prepared, and then perform badly in the actual interview.

The reason is that you never practised the thing you're being tested on. You practised knowing the answer. The interview tests saying it — under time pressure, without editing, to someone whose reaction you're reading in real time.

Those are close to unrelated skills.

Why silent rehearsal fails

When you think through an answer, you skip. Your brain marks the middle section as "and then I'd explain the architecture" and moves on, because you know what you mean. Out loud, that shortcut has to become forty seconds of actual sentences, and you discover you don't have them.

You also can't hear the problems. Silent rehearsal has no length — you can't tell that your answer runs four minutes when it should run ninety seconds. You can't hear yourself say "basically" eleven times, or trail off without a conclusion.

A structure that survives pressure

Most behavioral questions are asking the same thing: tell me about a time you did something hard, and what happened. The widely-taught STAR format (Situation, Task, Action, Result) works, with one adjustment most people miss — the weighting.

A good answer is roughly:

• Situation + Task: 20%. Enough context to make the rest legible. Two sentences, usually. This is where people over-invest.
• Action: 60%. What you specifically did. Not the team. This is the part being evaluated and the part most commonly rushed.
• Result: 20%. What happened, ideally with a number. Include it even when the result was mixed — especially then.

For the "tell me about a failure" genre, add one more beat at the end: what you changed afterward. An answer without it reads as a story about bad luck. With it, it reads as someone who learns.

Practising properly

Say it out loud, standing up. It feels ridiculous alone in a room. Do it anyway — the physical act of speaking is the thing being trained.

Time yourself. Most answers should land between 90 seconds and 2 minutes. Record the length of your first attempt; it's usually double what you'd guess.

Record and listen back once. Once is enough — the point is to hear your filler words and your pacing, not to critique yourself into paralysis.

Practise the follow-up, not just the question. Real interviews drill down. After each answer, ask yourself: what's the obvious next question? Then answer that too. This is where unprepared candidates come apart.

Vary the order. If you always practise the same list in the same sequence, you're memorizing a performance rather than building the ability to answer cold.

The questions worth preparing

You cannot prepare for every question, but the distribution is narrow. Prepare these and you'll have raw material for most of what you get asked:

1. Walk me through your background.
2. Tell me about a project you're proud of.
3. Tell me about something that failed.
4. Tell me about a disagreement with a colleague.
5. Why this role, and why now?
6. What's a technical decision you'd make differently in hindsight?
7. Describe something you had to learn quickly.
8. What questions do you have for us?

That last one is not filler. Having three specific questions ready — about the team, the work, the trajectory — is one of the cheapest ways to separate yourself.

Getting feedback that's worth anything

Self-assessment plateaus fast. You'll catch your filler words and your worst tangents, and then you'll stop noticing anything.

What helps is an outside read on specifics: whether your answer was actually responsive to the question asked, whether the result was clear, whether you spent your time on the right part. A friend in the industry is ideal. A mock interview that scores you question by question is the scalable version of the same thing — the value is in the written record of which answers were weak and why, which is precisely what you can't see from the inside.

Whatever the source, the loop is: answer out loud, get told specifically what was weak, do that answer again. Two or three rounds of that will change your performance more than a week of reading question lists.