How to Practise Mock Interviews 2026 - Getting Real Value From Them

Key Takeaways

• Speaking answers aloud is a separate skill from knowing them, and only the first one is tested.
• Practice only works if it is uncomfortable — same-length, unpaused, with someone who will push back.
• Recording yourself is the highest-return practice available and the one people avoid.
• Six prepared stories cover most behavioural questions, so practise adapting rather than memorising.
• The review afterwards matters more than the session itself.

Most people prepare for interviews by reading their answers, thinking through their examples, and feeling reasonably ready. Then the actual interview happens and the answers come out disorganised, too long, and missing the point they had clearly in mind.

That gap is entirely predictable. Knowing an answer and delivering it under observation are different skills, and only the second one is being assessed.

This guide covers how to practise so the gap closes.

Before the interviews start, make sure your resume is getting you there — the free ATS score checker.

Why reading answers does not work

You skip the hard part silently. Reading through an example in your head, you glide over the section you have not actually worked out. Speaking it aloud, you stop.

Timing is invisible on paper. An answer that feels concise in your head frequently runs four minutes out loud.

Structure collapses under pressure. The organised version exists when you are calm; the interview version is what emerges when you are not.

There is no follow-up. Real interviews probe. Your own review does not ask "what would you do differently?"

The fix is not more preparation. It is different preparation — out loud, timed, observed.

What each method actually trains

The useful conclusion: recording yourself sits in the low-effort column and trains most of what actually fails. That is why it is the foundation, not the optional extra.

Recording yourself

The highest-return practice available, and the one people avoid because watching it back is unpleasant.

How: pick a question, record two to three minutes on your phone, then watch it.

What you will notice immediately — and could not have noticed otherwise:

• Filler words you had no idea you used
• Sentences that trail off unfinished
• The point arriving ninety seconds late
• Where you lost your own thread
• Whether you look at the camera or away

The discomfort is the mechanism. You cannot fix what you have never heard yourself do.

Do two a day for a week and the improvement is substantial. This works whether or not you can find a practice partner, which makes it the foundation.

What to watch for, and what to do about it

Practising with someone

A peer. Alternate roles — being the interviewer is unexpectedly instructive, because you hear what a weak answer sounds like from the other side.

Someone senior in your field. A former colleague or a senior who was hired where you are applying. They ask better follow-ups and their feedback is calibrated.

Someone outside your field. Useful specifically for checking whether you can explain your work to a non-expert, which is exactly what a non-technical interviewer or HR round requires.

Ask them to push back. The most common failure in peer practice is politeness — a partner who accepts every answer is not simulating anything.

Give your partner these exact follow-ups

Hand them this list. Most people do not know how to interrogate an answer, and without prompting they will nod and move on.

Three of these in a row on the same story is roughly what a real interviewer does, and it is where most prepared answers fall apart.

Running a session properly

Simulate, do not discuss.

• Same length as the real thing
• No pausing to restart an answer
• Video on if the real interview will be
• Dressed appropriately if it is a video round — it changes how you carry yourself
• Phone away
• Answers spoken in full, not summarised as "and then I'd talk about the migration"

Do not stop to discuss mid-session. Take notes and review at the end, because interruption removes exactly the pressure you are trying to practise under.

A 45-minute session that mirrors a real round

Run it at the time of day your real interview is scheduled if you can. A 9am interview and a 9pm practice session are not the same experience.

What to practise

Six behavioural stories covering conflict, failure, influence without authority, ambiguity, pressure, and technical depth. Most questions map onto these, so practise adapting them to different phrasings rather than memorising answers to specific questions — see the US behavioral interview STAR guide.

The six stories, and what each one covers

Six stories, adapted, cover the overwhelming majority of behavioural questions asked. Memorising twenty answers is a worse use of the same time.

Your introduction. "Tell me about yourself" opens most interviews and sets the direction of everything after it. Practise it until it runs sixty to ninety seconds naturally.

Your project explanation, in a two-minute and a ten-minute version. Different interviewers want different depth — see campus placement technical interview questions.

Technical problems out loud. Narrating while solving is a genuinely separate skill from solving — see the US tech interview process guide.

Your questions for them, which are part of the assessment.

The review

Where the improvement actually happens.

For each answer, check:

• Length — was it under three minutes?
• Structure — was there a clear beginning, middle and result?
• "I" or "we" — did you describe your own contribution?
• A number — was there a quantified outcome?
• The point — did it arrive in the first thirty seconds?

Fix one thing at a time. Trying to correct five habits simultaneously fixes none. Pick the worst, work on it until it improves, then move to the next.

Keep the stories that work. Once an answer runs cleanly, stop rewriting it and practise delivery instead.

A four-week schedule that works around a full day

By week four you should be practising delivery, not rewriting content. If you are still changing what your stories say in the final week, you prepared too few stories too late.

Common Mistakes

Reading answers instead of speaking them. Only the spoken version is tested, and it is markedly harder than the version in your head.

Never recording yourself. It is the only way to hear the filler words, trailing sentences and late-arriving points that you cannot detect from the inside.

Practising with someone too polite to push back. A partner who accepts every answer is not simulating an interview.

Stopping mid-answer to restart. Real interviews do not allow it, and practising with restarts trains the wrong habit.

Memorising answers to specific questions. You cannot anticipate exact wording — practise adapting six stories instead.

Discussing during the session rather than after. Interruption removes the pressure you are practising under.

Trying to fix everything at once. Correcting one habit at a time works; correcting five works on none.

Practising only technical questions. Behavioural rounds eliminate technically strong candidates routinely.

Still rewriting your stories the night before. By then you should be practising delivery, not content.

Never practising your questions for them. It is part of the assessment and it is the easiest part to prepare.

Frequently Asked Questions

How many mock interviews should I do?

Enough that speaking your core answers feels routine — commonly one or two full sessions a week during an active search, plus daily short recorded practice.

Is recording myself really necessary?

It is the single highest-return practice available. Filler words, trailing sentences and late-arriving points are invisible from the inside and obvious on playback.

Who should I practise with?

A peer for volume, someone senior in your field for calibrated feedback, and someone outside your field to check you can explain your work to a non-expert.

What if I have nobody to practise with?

Recording yourself covers most of the value. It requires no partner and addresses the delivery problems that matter most.

Should I memorise my answers?

No. Prepare six stories and practise adapting them, because memorised answers sound recited and collapse when the question is phrased unexpectedly.

How long should answers be?

Two to three minutes for behavioural questions, sixty to ninety seconds for your introduction. Anything over four minutes is losing the room.

How do I stop saying "um" so much?

Replace it with silence. A two-second pause feels enormous to you and reads as composure to the interviewer, which is the opposite of how it feels.

I only have one week. What do I do?

Record two answers a day and run one full session. Prioritise your introduction and three behavioural stories over technical breadth.

How do I stop saying "we" instead of "I"?

Rewrite each story explicitly: "the team did X, I did Y". Then practise saying the Y part out loud until it stops feeling like boasting.

What should I review afterwards?

Length, structure, whether you said "I" rather than "we", whether there was a number in the result, and whether the point arrived in the first thirty seconds.

Practice matters only if your resume gets you the interview. Check your ATS score free.

Make This Practical

Record yourself answering one question a day for a week, and watch each one back. It is uncomfortable, it requires no partner, and it is the fastest way to discover the filler words, unfinished sentences and late-arriving points that you cannot hear from inside your own head.

Then run full sessions properly rather than comfortably. Same length, no pausing, video on if the real round is, answers spoken in full, and no discussion until the end — and hand your partner the follow-up questions above, because most people will not interrogate an answer unless you ask them to.

Finally, review against five specific checks — length, structure, "I" versus "we", a number in the result, and whether the point arrived in the first thirty seconds — then fix one habit at a time rather than all of them at once.