Mock Interviews That Are Worth the Hour

Why most practice runs teach you nothing

The typical mock interview is a friend reading questions from a list while you answer, followed by them saying it went well.

That exercise is comfortable and almost useless, for a specific reason. It rehearses the part you can already do, which is answering a question you saw coming, and skips the part that actually decides interviews, which is the follow-up.

Real interviewers probe. What would you do differently, who disagreed, how did you know it worked, what was the hardest part. A prepared answer survives the first telling and falls apart under three follow-ups. A mock interview that never probes cannot show you that.

Choose the partner for the right reason

Who runs it matters more than how it is structured.

Someone who has hired for the role is the best option by a distance. They know what the real questions are, they probe instinctively, and their assessment is calibrated against actual candidates.

Someone in your field who has not hired is a reasonable second. They can tell whether your technical content holds up even if their questioning is softer.

Someone outside your field is more useful than people assume, for one thing in particular: whether your answers are comprehensible without shared context. If a non-specialist cannot follow your explanation, a recruiter will not either.

A close friend or partner is the worst option and the most common. They will not push, they will not tell you it was bad, and you will both find the whole thing awkward enough to cut short.

If nobody is available, our interview prep tool generates role-specific questions, which handles the question side even if it cannot replicate a probing human.

Setting it up so it produces information

Brief the interviewer properly. Send them the job description and your resume, and tell them explicitly to ask follow-up questions rather than moving on when an answer finishes.

Give them permission to be harsh. People default to encouragement, and encouragement is not what you are there for. Saying "I need you to tell me what was weak, not what was fine" changes the session materially.

Ask for one specific thing to be hard about. Interrupting, pushing on vague claims, asking for numbers. A single instruction produces better pressure than a general request to be tough.

Run it in the format of the real interview. If the interview is on video, do the mock on video. The mechanics of a video call, where to look, when to speak, how the delay affects turn-taking, are part of what you are practising.

Record it, and watch it

This is the part everyone skips and it is where most of the value sits.

Watching yourself is unpleasant and it is the fastest way to notice things nobody will tell you. That you say "kind of" eleven times. That your answers run four minutes. That you look away when uncertain. That you begin every answer with forty seconds of context nobody needed.

None of these come through in verbal feedback because the person giving it is being polite and, more often, has genuinely stopped noticing.

Watch it once, at normal speed, with a notepad. Write down three things to change. Do not watch it repeatedly; the return drops sharply and the discomfort does not.

One clear takeaway: a recording tells you what a polite friend never will.

Time your answers

Length is the single most common problem and the easiest to fix once measured.

Two minutes is the target for a behavioural answer. Most people run to four or five on their first attempt, almost always because the setup is too long. The situation and task should take twenty seconds; what you did should take most of the time.

Have your mock interviewer time three answers and tell you the numbers. Being told you talk too long is easy to dismiss. Being told an answer took four minutes forty is not.

Do it before you feel ready

The instinct is to prepare thoroughly and then practise. That order wastes the exercise.

The point of a mock interview is to find out what you cannot yet do, and doing it early means the rest of your preparation is aimed at real gaps rather than imagined ones. Practising when you are already polished mostly confirms what you knew.

A useful sequence: rough out your examples, run a mock immediately, then spend your remaining preparation on whatever fell apart. One early session and one closer to the interview beats two sessions the night before.

What to actually ask for afterwards

General feedback produces general answers. Ask narrow questions instead.

• Which answer was weakest, and what specifically was missing from it?
• Where did you stop believing me?
• Which answer would you have pushed harder on if this were real?
• Did I answer the question you asked, or a nearby one?
• What would you write in your notes about me?

That last one is the most useful question available. It forces the person out of politeness and into the framing an actual interviewer uses.

Practising alone, which mostly works

Nobody available is a common situation and it is not a reason to skip practice.

Say your answers out loud to an empty room, timed and recorded. It feels absurd and it captures most of the benefit, because the gap between knowing a story and telling it is what you are training against.

Then supply your own follow-ups. After each answer, ask yourself the three questions a good interviewer would: what would you do differently, who disagreed, how did you know it worked. Answering those aloud is the closest solo approximation of a probing interviewer.

Our career guides set out what each role's interviews concentrate on, which helps you choose which examples deserve the practice.

When mock interviews stop helping

There is a point of diminishing returns and people past it are usually avoiding applying.

Two or three sessions for a role you care about is plenty. Beyond that you are rehearsing rather than improving, and over-rehearsed answers develop the same problem as memorised ones: they arrive at the wrong speed and stop sounding like a person.

If your answers are landing at roughly two minutes, you can handle three follow-ups, and you are not saying anything you would regret, you are ready. The remaining uncertainty is not fixable by more practice.

Practise the parts that are not questions

Mock interviews concentrate on the middle of the conversation and leave the edges untouched, which is where more of them go wrong than people expect.

The first ninety seconds set the tone. Whatever you say to "tell me about yourself" gets read as a signal of how organised you are, and it is the answer most people have never said out loud before the day. Run it three times in the mock, not once.

The salary question deserves the same treatment. It usually arrives early, often from a recruiter rather than the hiring manager, and the difference between a rehearsed reply and an improvised one is large. Have your mock interviewer ask it at an awkward moment and watch what you do.

The questions you ask at the end are also part of the assessment. Practise saying them aloud, because a question that reads well in your notes can sound accusatory when spoken, and you will only find that out by hearing it. Our post on questions to ask an interviewer covers which ones are worth the slot.

Then there is what happens when you do not know something. Ask your interviewer to include one question you cannot answer. Most candidates have never practised saying "I have not done that, here is the closest thing I have," and it comes out either defensive or apologetic the first time. It is a two-sentence skill and it is worth owning before it matters.

None of these take long. Ten minutes at the edges of a session covers all four.

Questions people ask

How many mock interviews should I do?

Two or three for a role you care about. One early to find the gaps, one closer to the day. Beyond that you are rehearsing rather than improving.

Who should run a mock interview?

Ideally someone who has hired for the role. A close friend is the most common choice and the least useful, because they will not push.

Should I record my practice interview?

Yes. It reveals filler words, answer length and delivery problems that no polite observer will mention and that you will not notice live.

How long should my answers be?

About two minutes. Most people run to four before measuring, usually because the setup takes too long relative to what they actually did.

Can I practise without a partner?

Yes. Answer out loud, timed and recorded, then ask yourself the follow-ups a real interviewer would. It captures most of the benefit.

Related reading

• Tech Resume Keywords: What Recruiters Actually Search For
• Healthcare Resume Keywords: Licences, Settings and Systems