People want a number — "do five and you're ready." But the real answer isn't a count; it's a state you're aiming for, and the reps are just how you reach it. Still, "it depends" is a useless answer on its own, so below you'll get both: the principle, and rough ranges for different situations.
The principle: practise until it's boring
You're ready when the interview stops feeling novel — when "tell me about yourself" triggers a calm, rehearsed response instead of a jolt of adrenaline. Nerves are highest on first exposure and fall with repetition, so you're doing reps until the situation feels familiar, not until you hit an arbitrary milestone. If you regularly go blank under pressure, that familiarity is exactly what buys you the headroom to think.
Rough ranges by situation
The right number depends on how rusty you are and what's at stake. These are ranges, not promises — treat them as a starting point and adjust to how the reps actually feel.
- Rusty (haven't interviewed in years): ~4–6 full mocks. The rust is real and it's mostly nerves, not knowledge. The first two reps just knock off the shock of hearing yourself; the useful practice starts after that.
- Actively interviewing already: ~1–2 tune-ups per role. You've got the reflexes; you're sharpening role-specific stories and shaking off the particular nerves of a company you want. Quick, targeted, not a full course.
- Senior / leadership role: ~3–5, focused on narrative. Not about knowing the material — it's about telling a coherent story about impact, judgement and trade-offs out loud. Seniors often under-practise here because they assume experience carries them. It doesn't carry the delivery.
- Technical loop: 2–4 per round type. Practise each format separately — coding, system design, behavioural — because they fail differently. The skill that trips people isn't the answer; it's narrating your reasoning while your brain is busy solving.
- Final round: ~2–3, close to the real thing. You already cleared the earlier gates, so this is polish and stamina — full-length reps that rehearse the specific panel and the fatigue of a long day, not fresh preparation.
For most people this lands in the small handful — not one, not thirty. If a range feels too low, it's usually because the reps weren't realistic enough to count.
A senior engineer, five years since her last interview, targeting a staff role: she's both rusty and senior. She does two reps to knock off the shock, then three more aimed squarely at telling crisp impact stories out loud — around five total, weighted toward narrative rather than trivia. The count is just the by-product of practising until it stopped feeling strange.
Quality beats count — by a lot
Three focused, out-loud, feedback-driven mocks beat ten you half-attended. A rep only counts if it's realistic enough to trigger real nerves and you actually act on the feedback. Ten passive run-throughs where you never review what went wrong aren't ten reps — they're ten rehearsals of your mistakes.
Counting silent, in-your-head run-throughs as reps. Thinking through an answer while lying in bed rehearses nothing that matters — the whole difficulty lives in speaking it aloud under pressure. If your mouth didn't move and your heart rate didn't tick up, it wasn't a rep.
Space them out — don't binge
Five mocks in one panicked evening are worth far less than five spread across a week. Cramming stacks the reps while you're tired and defensive, so the feedback bounces off; spacing lets each lesson settle before the next one, and it gives your nerves time to actually recalibrate between sessions. Skill and calm both consolidate in the gaps, not in the grind.
Practically: a rep every day or two in the run-up beats a marathon the night before. And it's fine — good, even — to stop when you're clearly landing your answers. There's a point of diminishing returns where another mock adds anxiety instead of skill. The goal was never a high score on the counter; it was walking in with the thing already feeling routine.
Do one full out-loud mock today — record it and watch it back before you plan any more. That single honest rep tells you more about how many you need than any guide can. If you're smooth and calm, you're closer than you think. If you wince, you just found your real starting point.
How to know you're ready
Forget the count and check for two signs. First, your core answers come out smoothly without scripting — you can hit the beats in any order without groping for them. Second, the thought of the interview produces mild anticipation rather than dread. That second shift is real interview confidence — earned through reps, not affirmations. When you hit both, you've done enough, whatever the number turned out to be.
Then stop. There's a point of diminishing returns where more mocks add anxiety instead of skill, and cramming the night before does more harm than a good night's sleep. Pair your reps with a sensible prep week and trust that you've done the work.
Make every rep count
Run realistic voice mock interviews that trigger real nerves, then get a scored report and a model answer for every question. A handful of these beats ten passive run-throughs. Free to start.
Start freeFrequently asked questions
How many mock interviews should I do before a real interview?
There's no magic number, but a rough guide: 4-6 if you're rusty, 1-2 tune-ups if you interview regularly, 3-5 for senior roles focused on narrative, 2-4 per round type for technical loops, and 2-3 for a final round. The real target is doing enough realistic, out-loud reps that the interview stops feeling novel.
How do I know if I'm ready for an interview?
Two signs: your key answers come out smoothly without a script, and thinking about the interview brings mild anticipation rather than dread. If you're there, you've done enough reps regardless of the count.
Do mock interviews in my head count?
No. The difficulty of an interview lives in speaking out loud under pressure, so silent run-throughs rehearse the wrong thing. A rep only counts if you actually voice your answers, ideally recorded or with feedback, and act on what you find.