The Interview Gym: Why Practising Out Loud Beats Rehearsing in Your Head
You've read the questions. You know your answers. Then you open your mouth in the interview and it comes out as a shapeless three-minute ramble. Here's why — and the fix.
There's a specific kind of frustration that comes from being well prepared and interviewing badly. You'd read about the role. You knew your examples. And then the question landed and you produced four minutes of meandering context before arriving at a point you never quite made.
That's not a preparation failure. It's a rehearsal-format failure. Reading answers and speaking answers are different skills, and almost everyone practises only the first one.
Why thinking through an answer doesn't transfer
In your head, an answer is a compressed idea: "the migration project, how I handled the vendor, good outcome." That takes a second and a half to think and feels complete. Spoken, it's ninety seconds of sequencing decisions you've never made before — where to start, what to leave out, when to stop.
You're also missing everything that only exists in speech: pace, filler words, where your voice runs out of air, the moment you realise you've forgotten the point of the story and start circling. None of that shows up in silent rehearsal, and all of it shows up in the interview.
In your head
Instant, non-linear, forgiving. You skip the boring parts automatically and never notice you did. Feels like competence.
Out loud
Linear, timed, unforgiving. You have to choose an order, hold it, and land it — while a person watches. Reveals competence.
Musicians don't prepare by reading the score and imagining it. The interview is a performance, and the only rehearsal that counts is the one where sound comes out.
The four things that only break when you speak
- 1Length. Almost every unpractised answer is two to three times too long. Ninety seconds is the target for a behavioural question; most people's first spoken attempt runs four minutes.
- 2Opening. Strong answers state the situation in one sentence. Weak ones spend forty seconds on organisational background before anything happens.
- 3Ending. Unpractised answers don't end, they trail off — and the trail-off is where confidence visibly drains out of the room.
- 4Recovery. When you lose your thread, do you stop, breathe and restate, or do you keep talking hoping to find it? That's a trained reflex, not a personality trait.
The most common self-inflicted wound
Answering the question you prepared instead of the one you were asked. It happens when a memorised script fires on a keyword. Practising out loud with varied phrasings of the same question is what breaks the reflex.
How to actually run a practice session
Twenty minutes, three times, beats one two-hour session the night before. Deliberate practice means a specific target per round, immediate feedback, and repetition of the part that failed — not running through the whole list once.
Pick five questions, not fifty
Your walkthrough ("tell me about yourself"), a conflict story, a failure story, a why-this-company answer, and the hardest technical question in your field. These five cover most of what you'll be asked.
Record yourself answering cold
No notes, no second take. Your phone is enough. The first recording will be uncomfortable to listen to; that discomfort is the entire point and it's the last time it'll be this bad.
Listen with a stopwatch and one question
How long did it take to reach the point? Note the timestamp of the first sentence that actually answers the question. Getting that from 0:45 to 0:08 is the single biggest improvement available to you.
Redo only the opening
Don't run the whole answer again. Redo the first fifteen seconds five times until it lands cleanly. Openings are what you can most reliably train.
Change the phrasing and go again
"Tell me about a conflict" / "Describe a time you disagreed with a manager" / "When have you had to push back?" Same story, three prompts. This is what makes you robust rather than scripted.
Finish on a full clean run
End every session with one complete, unbroken answer. The last rep is the one your nerves will remember.
Our audio interview coach asks the questions out loud, records your answers and gives you feedback on structure, length and clarity — as many rounds as you want. It builds the questions from your CV, so start there.
Build my CV, then practiseA structure that survives being spoken
STAR is the standard framework and it works, but people memorise it as four boxes and produce answers that sound like form-filling. The spoken version is simpler: one sentence of setup, most of your time on what you did, and a hard stop on the result.
| Part | Time | Common mistake |
|---|---|---|
| Situation | ~10 seconds | Two minutes of org-chart context nobody needs |
| Task | ~10 seconds | Merging it with situation until neither is clear |
| Action | ~50 seconds | Saying "we" — the interviewer needs to know what you did |
| Result | ~15 seconds | Trailing off without ever stating the outcome |
The "we" problem
Listen back to a recording and count your "we"s. Team framing is admirable and it also makes you invisible. "We rebuilt the process" tells the interviewer nothing about you. "I mapped the current process and proposed the redesign; the team built it in six weeks" tells them everything, and is still generous.
Prepare the questions you'll actually be asked
Generic question lists are a starting point, not a preparation plan. The questions in your interview come from three sources, and you can predict most of them.
Your CV
Every gap, every short tenure, every unusual jump, every big claim. If it's on the page, prepare a calm two-minute version. Interviewers probe the interesting bits — and you chose which bits are interesting.
The job description
The core responsibilities become behavioural questions. "Manage stakeholder relationships" becomes "tell me about a difficult stakeholder". Read the ad as a question generator.
The company's situation
A recent funding round, merger, product launch, regulatory change or hiring spree tells you what problem they're hiring you to help with — and what they'll test.
Your own questions count as practice too
"Do you have any questions for us?" is a real evaluated question, and it's the one candidates most often improvise. Prepare three, out loud, like any other answer. Ask about the actual work: what would the first ninety days look like, what's the hardest part of this role, how does the team decide priorities.
The short version
- Silent rehearsal trains a different skill from the one the interview tests.
- Record yourself cold — the first uncomfortable playback is where all the improvement is.
- Target ninety seconds; measure how long it takes you to reach the point.
- Practise the same story against three phrasings so you're robust, not scripted.
- Predict your questions from your CV, the job ad and the company's current situation.
Get the CV right, then train the answers
Your interview questions come out of your CV — so build the document first, then practise the walkthrough out loud against the roles you're actually applying for. Both live in the same place.
Build my CV freeFree to build and preview. Pay only when you download.
Frequently asked questions
How long should an interview answer be?
Around 60–90 seconds for a behavioural question, and under 2 minutes for "tell me about yourself". Most unpractised answers run two to three times longer than that. The reliable fix is recording yourself with a stopwatch — the gap between how long an answer feels and how long it is surprises nearly everyone.
Is it worth doing mock interviews on my own?
Yes, provided you actually speak and record. Solo practice with a recorder captures the things silent rehearsal can't: pacing, filler words, how long you take to reach the point, and whether your answer has an ending. A partner adds pressure and unpredictable follow-ups, which is a useful second stage.
How many questions should I prepare?
Five, deeply, beats fifty superficially. A self-walkthrough, a conflict story, a failure story, a why-this-company answer and the hardest technical question in your field will cover the large majority of what you're asked — and the same underlying stories can be re-aimed at many different prompts.
What if I go blank in the interview?
Say so and buy time deliberately: "Good question — let me think for a second." A three-second pause reads as considered; thirty seconds of filler reads as panic. This is a trainable reflex, which is exactly why practising recovery in your rehearsals matters as much as practising the answers.
Should I memorise my answers word for word?
No. Memorised answers break the moment the question is phrased differently, and they sound recited. Memorise the *structure* and the key facts — the opening sentence and the result are worth locking down — then let the middle vary each time you tell it.