If you've got an interview coming up, there's a decent chance your practice so far looks something like this: you found a list of common questions, read through them, and thought about what you'd say to each one. Maybe you jotted a few notes. It feels like preparation, and it is, sort of. But it leaves out the part the interview tests, which is saying the answer out loud to a person who can ask you a harder question right after.
Below is how we'd tell a friend to practice. Six steps, in order. Work out what this particular interview is going to ask, pull together a handful of stories you can tell well, say them out loud until they hold together, get someone to ask you follow-ups, do a couple of full mock interviews, and then fix the two things the feedback keeps pointing at. If you only have a couple of days, there's a compressed version further down.
Why reading questions doesn't count as interview practice
There's nothing wrong with reading question lists. You should. The problem is stopping there, because reading and thinking happen in your head, and interviews happen out loud, in front of someone, with no pause button.
Practice that carries over to the interview tends to have a few things going for it. You're speaking in full sentences, so your pacing and your endings get exercised. You don't know exactly what's coming, so you're pulling stories from memory under a bit of pressure rather than reading them off a page. And afterward, somebody or something tells you how it went, so you're not relying on your own sense of whether it was fine.
Sitting at the kitchen table with a list gets you none of that. Each step below adds at least one of those things back.
Step 1: Work out what this interview is going to test
A lot of wasted prep comes from trying to cover every question anyone has ever been asked. You don't need to. You need the eight or ten questions this interviewer is likely to ask, and you can get surprisingly close.
Start by asking the recruiter what the format is. Phone screen, behavioral round, technical round, case, panel? They'll usually just tell you, and it changes how you should spend your time.
Then go through the job description slowly and turn each requirement into the question someone would ask to check for it. If it says stakeholder management, expect something like "tell me about a time you had to get buy-in from someone who disagreed with you." If it says ownership, expect "tell me about a problem you fixed that wasn't really your job."
Last, be honest with yourself about the two or three things a hiring manager might worry about when they look at your background. A gap, a jump in level, a switch of industry. Those questions are coming whether or not anyone asks them directly, so you want stories ready that answer them.
When you're done you should have a short list of likely questions and a short list of doubts to address. That's what you're practicing for.
Step 2: Put together six to eight stories you can tell well
You can't practice telling stories you haven't picked yet. So before you say anything out loud, choose a small set of experiences that can stretch across a lot of different questions. Six to eight is plenty. Any more and you won't know any of them well.
Try to cover the usual ground:
| Story type | What it shows | Questions it answers |
|---|---|---|
| Achievement | You get measurable results | Biggest win, why should we hire you |
| Conflict | You can disagree without it getting ugly | Difficult coworker, pushing back on a manager |
| Failure | You can own a mistake | Tell me about a mistake, what would you do differently |
| Ambiguity | You can work without clear instructions | A time you had little direction |
| Leadership | You can move things without formal authority | Leading a project, convincing a team |
| Learning | You pick things up fast | New tools, new industry, new responsibilities |
For each one, write down a few bullet points rather than a paragraph. What the situation was, what you specifically did, and how it turned out, ideally with a number attached. If that sounds like the STAR method, it is, but treat it as a checklist rather than a script. Spend most of your words on what you did, and say "I" rather than "we". If you can't say what your own part was, that's a sign to pick a different story.
Go for the stories with something at stake. "I resolved a conflict by having a conversation" won't land. "I had to tell the VP that the thing we'd spent six months building wasn't going to meet the requirement, three weeks before launch" will. Most people have stories like that and skip them because they're uncomfortable to tell. Those are usually the best ones.
Step 3: Say each answer out loud, with a timer running
This is the step everyone skips, and it's the one that makes the difference between sounding prepared and being prepared.
Set a timer for 90 seconds, which is about as long as a behavioral answer should run. Pick a question from your list and answer it out loud, in full sentences, as though someone were sitting across from you. Then do the next one, but record it, and listen back.
Listening to yourself is uncomfortable, so make it easier by only listening for three things. Does the answer have a point an interviewer could repeat in one sentence? Is the example specific, with names and numbers and decisions you made, rather than "we worked together to address the issue"? And does it end, with a result, instead of trailing off?
Ignore everything else for now. If you try to fix every filler word and awkward pause at once you'll get self-conscious and worse. Fix those three and you'll already sound better than most people who walk in.
Go through each story in your bank at least twice. When you can hit the main points inside 90 seconds without looking at your notes, you're ready for the harder part.
Step 4: Practice the follow-ups, because that's where answers fall apart
Interviews rarely go answer, next question, answer, next question. You finish a story and the interviewer asks what you'd do differently, or how you measured the result, or how the other person reacted. That's not them being difficult. Follow-ups are how a good interviewer checks that you lived the story you just told, and they're where a memorized answer collapses.
For each of your stories, write down three follow-ups you'd expect and answer them out loud, briefly. You don't need a polished answer to every possible angle. You need to be able to talk about the story from a few directions without stalling.
It helps a lot to have someone else ask the follow-ups, so you can't see them coming. A friend who does interviews for a living is great if you have one. An AI interviewer built for this works too. When you do a session on Roundpass, the AI interviewer listens to the answer you gave and asks a follow-up based on it, so if you were vague, it pushes, the same way a person would.
Step 5: Do at least two full mock interviews
Practicing on your own gets you fluency. What it can't give you is the feeling of a full interview, with questions you haven't seen, one after another, and no stopping to check your notes. For that you need a mock interview, and you need the whole thing rather than a few questions here and there.
The whole thing matters because interviews wear you down in ways single questions don't. By the sixth answer your energy dips, your stories start to blur into each other, and the transitions get clumsy. You won't know that about yourself until you've sat through one.
A few ways to get one:
- Ask someone who hires people, or who interviewed for a similar role recently, to run 30 minutes with you. Their questions don't have to be great. The point is answering on the spot while someone watches.
- Book a human coach. Worth it for senior and executive roles where how you carry yourself matters as much as the content, though it's expensive and you'll need to plan ahead.
- Use an AI mock interview, which you can do at 11pm on a Tuesday without asking anyone a favor. On Roundpass the first interview session is free and doesn't need a credit card. It's 15 minutes, three or four behavioral questions tailored to the role you enter, and a full feedback report at the end. You can be answering your first question about a minute after signing up.
If you're weighing up tools, we wrote a comparison of AI interview prep tools that goes through what each one does well and where it falls short, including the cases where Roundpass isn't the best pick.
Try to do the first mock at least five days before the real interview so you have time to act on what you learn. Do the second one two or three days out, after you've fixed things.
Step 6: Fix two things, then go again
A mock interview with no feedback is just an interview. The information that comes out of it is the point, so make sure you get some.
Good feedback is about the answers rather than about you. It tells you which stories never got to a result, where you slipped into "we" when the interviewer needed to hear "I", which answers ran long, and where you leaned on filler. A friend can catch some of that. A written report that goes through every answer catches all of it, which is what Roundpass's feedback report is for. It looks at the STAR structure of each answer, lists the competencies you showed and the ones you didn't, and ties each suggestion to something you said in the session.
Whatever the feedback says, don't try to fix all of it. Pick the two biggest problems, rework the stories behind them, say those answers out loud again against the timer, and then do another mock. Two focused rounds will get you further than one where you try to change everything.
How much interview practice is enough, and when to do it
For a job you care about, plan on somewhere between six and ten hours spread across a week or two. More than that and you hit diminishing returns fairly quickly. Keep the last day light. Cramming the night before tends to make people worse, not better.
If you have two weeks
- Days 1 and 2: ask about the format, build the question list, draft the story bank.
- Days 3 and 4: say every story out loud against the timer and record a few. Write three follow-ups per story.
- Day 5: first full mock interview.
- Days 6 to 8: fix the two biggest issues from the feedback. Replace any story that isn't working.
- Day 9 or 10: second mock interview.
- Days 11 to 13: light practice on whatever's still shaky.
- Day 14: rest. Reread your three strongest stories and the job's main requirements, and leave it there.
If you have one week
Same arc, squeezed: question list and stories on day one, out-loud practice on day two, first mock on day three, fixes on day four, second mock on day five, a light look-through on day six.
If you have 48 hours
Skip building a full bank. Pick your four strongest stories, say each one twice against the timer, and do one 15-minute mock so you've heard yourself under a bit of pressure. Spend whatever's left reading about the team and coming up with two questions worth asking at the end.
Adjusting for the kind of interview you've got
Everything above is built around behavioral interviews, which nearly every process includes somewhere. Some tweaks for other formats:
- Technical and coding rounds. Practice talking through your reasoning while you solve the problem, because interviewers are grading the thinking as much as the result. And don't let the behavioral round become an afterthought. At a lot of tech companies it counts for as much as the technical one.
- Case interviews. Practice laying out your structure aloud before you dig in, and give each part a time budget. The framework and the trade-offs are what's being judged, not how clever the idea is.
- Phone and video interviews. Rehearse in the exact setup you'll use, same mic, same camera, same lighting. Record one and check that your eye line and audio are doing you favors.
- Panel interviews. Practice answering to the person who asked while still bringing the others in.
- Career changers. Your stories stay the same and the framing changes. A story about pushing back on a product requirement because it wasn't technically feasible is a solid product management story, as long as you tell it as product judgment rather than engineering.
Frequently asked questions
How long should you practice for a job interview?
Six to ten hours over a week or two is enough for most roles. Roughly, that's a couple of hours building your question list and story bank, two or three hours of timed out-loud practice, and two full mock interviews with time in between to act on the feedback. Past that the returns fall off quickly, and heavy practice the night before usually does more harm than good.
How do you practice for an interview by yourself?
The first three steps here work fine alone: map the likely questions, pick your stories, and answer each question out loud against a 90-second timer while recording yourself. What's hard to do alone is handle follow-ups you didn't see coming, and get an honest read on how you sounded. For those two, you want a friend who interviews people or an AI interviewer that responds to what you said.
Is it better to practice interview answers out loud or in your head?
Out loud. Rehearsing silently trains your memory of the story, not your delivery of it, and those are different things. Plenty of people feel completely ready right up until they hear themselves ramble for three minutes on a recording. You only catch that by saying it and listening back.
Can you practice a job interview for free?
Yes. A friend who hires, a university career center, and the voice recorder on your phone all cost nothing. If you want an interviewer that asks follow-ups and a written feedback report afterward, Roundpass's first 15-minute interview session is free, no credit card needed, and the report comes with it.
Start with one answer, today
The hardest part of interview practice is the first answer you say out loud to an empty room. After that it's repetition. So pick one question from your list, set a 90-second timer, and answer it now, before you close this tab.
When you want someone to ask the follow-ups, run your first mock interview free on Roundpass. It takes about a minute to start, and 15 minutes later you'll have a clear picture of where you stand.