What Is a Mock Interview, and Is It Worth Your Time?

What actually happens in a mock interview

Most sessions run somewhere between 30 and 60 minutes. You are given a role, sometimes a job description, and the interviewer works through a realistic mix: an opener like "tell me about yourself", a handful of behavioral questions, and for technical roles a coding or design problem. Then comes the debrief.

The debrief is where most of the value sits. Answering a question badly in private teaches you nothing. Being told that your answer to "why do you want this job" ran ninety seconds and never actually said why is something you can fix by Thursday.

Who can run one

There are four common setups, and they suit different people.

A sensible plan for many people is to mix them: use an AI or a friend for volume early on, then book one session with someone who interviews for a living once your answers are in decent shape.

The types of mock interview

"Mock interview" is a wide label. Pick the one that matches the round you are actually facing.

Behavioral interviews ask about things you have done: a conflict, a missed deadline, a project you led. Your answers need real stories, not adjectives. Technical or coding rounds have you solve a problem while explaining your thinking (there is more in our guide to technical mock interviews), and system design rounds give engineers an open-ended prompt, such as designing a notification service, judged on how you reason about trade-offs.

Case interviews, common in consulting and product roles, hand you a business problem to structure live. Screening or HR rounds are shorter and more conversational: salary expectations, notice period, why you are leaving. Panel and video interviews are their own thing, since you are speaking to several people at once, or to a camera with nobody reacting.

Are mock interviews worth it?

Yes, if you do them properly, and mainly for a reason people do not expect. Interviewing is its own skill, separate from doing the job. Plenty of capable people have knowledge they cannot express clearly in ninety seconds while nervous. A mock interview shows you the gap between what you know and what you say.

It also lowers the temperature. The first time you answer "walk me through your resume" out loud, it tends to come out messy. By the fourth time it is smooth, and your real interview is not the first time.

How to get more out of one

1. Choose one target role and paste in the job description. Generic practice gives generic feedback.
2. Keep it real: camera on, timer running, and no pausing to restart an answer you botched.
3. Ask a sharper question than "how did I do?" Try "which answer was weakest, and what would you change in it?"
4. Record it if you can, and watch it once. It is uncomfortable, and it is also the fastest way to notice filler words and where your eyes go.
5. Repeat the weak questions within a few days. Feedback you do not act on is just information.

Where people go wrong

The most common mistake is practicing what you are already good at. It feels productive, and it is comfortable. Spend most of the session on the two or three questions you would rather skip.

The second is memorizing scripts. A rehearsed answer delivered word for word sounds like a recitation, and interviewers notice. Know your stories and your key points, then let the sentences come out differently each time.

The third is doing a dozen sessions in a week and changing nothing between them. Two well-reviewed mock interviews beat ten you shrugged off.

You can try one right now: our free mock interview takes a few minutes to start. Prefer to practice on your own first? Here is how to do a mock interview at home.