- The highest-leverage prep step is rehearsing how you'll defend each claim on your resume out loud, because that's what the interview actually tests.
- A tight "tell me about yourself" answer, kept under 90 seconds, prevents the single most common mistake I see candidates make.
- Company research matters, but it hits diminishing returns fast, and most people spend their prep time in the wrong place.
To prepare for an interview, research the company and the role, map your resume bullets to the job's requirements, and rehearse three to five stories that prove you've done the work before. Most candidates over-prepare on company trivia and under-prepare on defending their own resume, which is where interviews are won or lost. Build your prep around the document you already submitted.
What should you actually do to prepare for an interview?
Interview prep tends to expand to fill whatever time you give it, which is a problem, because the highest-value work takes a couple of focused hours and the rest is mostly reassurance. The list below is in rough priority order, so if you only get through the first four items, you've covered most of what matters.
- Re-read your own resume. Read the exact version you submitted for this role, because that's the document the interviewer is holding, and any gap between what it says and what you say out loud is what they'll probe.
- Map every claim to a story. For each bullet, especially the quantified ones, know the backstory well enough to explain it in two or three sentences without scrambling.
- Read the job description twice. Pull out the three or four requirements they repeat or lead with, because those are the themes your answers should keep circling back to.
- Prepare your "tell me about yourself" answer. Rehearse it out loud, time it, and keep it under 90 seconds. More on why below.
- Pick five or six flexible stories. Choose examples broad enough to answer most behavioral questions, since interviewers ask the same underlying things in different words.
- Research the company, then stop. Know the mission, what they do, recent news, and who you'd be working with. You don't need their full funding history.
- Prepare three or four questions to ask them. Make them specific to the role and the team, not generic questions you could ask any employer.
- Sort the logistics. Confirm the time zone, the location or video link, who you're meeting, and what you're wearing, so none of it is a variable on the day.
If your resume itself needs work before any of this, fix that first, because no amount of rehearsal saves a document that misrepresents what you did. Tightening it is faster than people expect, and you can tailor your resume to the specific posting in about 20 to 30 minutes.
How far in advance should you start, and what fits in each window?
You don't need a week, but you do need more than the morning of. The useful prep splits cleanly into three windows. About a week out, do the slow work: re-read your resume, build your stories, and research the company while it can still sink in rather than sitting in short-term memory. The day before, do one timed run of your "tell me about yourself" answer and a couple of behavioral questions out loud, ideally to another person or at least to a voice recorder, because rehearsing in your head feels productive and isn't. The morning of, do almost nothing except confirm logistics, re-skim your resume and the job description, and arrive early enough that you're not regulating your heart rate in the lobby. Cramming the night before tends to make people more anxious, not more prepared, so the goal in the final window is to stay loose, not to learn anything new.
How do you use your own resume as your interview script?
This is the part almost nobody does, and it's the part that decides interviews. Your resume is not just the thing that got you in the room. It's the agenda for the conversation, because the interviewer will use it to drive their questions, and every line on it is a claim you're implicitly agreeing to defend.
I've written resumes for over 1,200 people, and the pattern is consistent: the bullets that look strongest on paper are often the ones candidates fumble hardest in the room. Take a real example, lightly anonymized, of a bullet I see some version of constantly:
Increased sales by 200% in 3 months, generating $500K in new revenue.
On paper that's excellent. In an interview, it's a trap if you haven't prepared for it, because a good interviewer's instinct is to pull the thread. They'll ask what the baseline was, since 200% of a small number is a different story than 200% of a large one. They'll ask whether the $500K was your number or the team's, and what you specifically did versus what the market or a pricing change did. They'll ask how you'd repeat it. If you can answer all of that crisply, the bullet does exactly what it's supposed to and you look credible. If you stall, the impressive number flips into a liability, and the interviewer quietly downgrades everything else on the page along with it.
So the method is simple, if tedious: go bullet by bullet, and for every quantified claim write down the baseline, your specific contribution, the mechanism that produced the result, the timeframe, and what you'd do differently next time. Do that for your top five or six bullets and you've prepared for most of the interview without ever looking at a list of "common interview questions," because the questions were always going to come from your resume anyway. The document you built, whether you wrote it yourself or used a tool like Resumatic to build an ATS-ready draft, is your script. Treat it that way.
What questions should you prepare answers for, and how do you structure them?
You can't predict every question, but you can prepare for the categories, because most interview questions are variations on a handful of underlying ones. There's the opener ("tell me about yourself"), the motivation question ("why this role, why us"), the behavioral questions ("tell me about a time you..."), the weakness or failure question, and the closer ("do you have any questions for us"). If you have solid material for each category, you can adapt on the fly.
For the behavioral questions specifically, structure your answer around the situation, what you actually did, and the result, kept tight. The common failure isn't picking the wrong framework, it's over-stuffing the answer, so resist the urge to narrate every detail. Say what the situation was in a sentence, spend most of your time on the specific actions you took, land the result, and stop. The interviewer will ask a follow-up if they want more, and a follow-up is a good sign, not a gap you need to pre-empt. If you want a fuller bank to practice against, work through a list of common interview questions and how to answer them, but treat them as practice reps for the categories, not scripts to memorize word for word.
What do most people get wrong when preparing?
After moderating r/resumes (1.2M members) and reading a steady stream of "how did my interview go this badly" posts, the same few mistakes come up over and over, and they're rarely about knowledge. They're about delivery and self-awareness.
The first one is the big one. "Tell me about yourself" is the most predictable question in the entire process, and it's the one people prepare for least, which is backwards. A long, meandering answer to the opener sets a tone you spend the rest of the interview climbing out of. The third one is newer and worth flagging directly: live AI assistance during video interviews is rising fast, and it doesn't work the way people hope. Interviewers can tell, the same way teachers can tell, and the cost of getting caught is far higher than the cost of a slightly rough answer you came up with yourself.
How do you prepare for a virtual or phone interview?
The content of your prep doesn't change for a video interview, but the failure points do, so handle them in advance. Test your camera, mic, and connection on the actual platform you'll be using, not a different one, ideally a day ahead so you have time to fix anything. Set your camera at eye level and look at the lens, not the screen, when you're speaking, because that's what reads as eye contact to the person on the other end. Frame yourself with a plain or uncluttered background and decent front lighting. You're allowed to have your resume and a few notes off to the side, which is one of the real advantages of a remote interview, but keep them as bullet points you glance at, not a script you read, since reading is as obvious on camera as live AI is. For a phone interview, stand or sit upright, because your posture genuinely changes how your voice carries, and keep your resume in front of you for the same reason it helps on video. If you want a plain external checklist to cross-reference, the U.S. Department of Labor's interview tips are solid and unfussy.
What should you do in the 24 hours before?
Keep the final day boring on purpose. Confirm the time, the time zone if it's remote, the location or link, and who you're meeting, so nothing about the logistics is still open. Do one out-loud run of your "tell me about yourself" answer and one behavioral story, then stop practicing, because more reps past that point tend to add anxiety rather than polish. Have your resume printed or open on screen, along with the job description. Lay out what you're wearing the night before. Sleep, since being rested does more for your performance than one extra hour of cramming ever will. The work that matters was the resume mapping and the rehearsal you did earlier in the week, and the day-before job is just to protect it.
Frequently asked questions
A: For most roles, two to four focused hours is enough, spread across the week before rather than crammed the night before. The bulk of that should go to mapping your resume claims to stories and rehearsing your opener out loud. Senior or highly technical roles may need more, but past about five hours you're usually buying reassurance, not better answers.
A: Keep it under 90 seconds and structure it as a short arc: where you are now professionally, one or two highlights that connect to this specific role, and why you're interested in this job. Skip your full work history and anything personal. Rehearse it out loud and time it, because this is the most predictable question and the one people botch most often.
A: Yes, a small set of notes is fine and often looks prepared rather than unsure, especially the questions you want to ask them. In a remote interview you can keep brief notes off-screen too. The key is that they're glanceable prompts, not a script you read from, since reading your answers is obvious in person and on camera.
A: Lean on transferable examples from school, internships, volunteer work, or projects, and prepare them the same way you'd prepare paid work: situation, what you did, result. Interviewers for entry-level roles expect this and care more about how you think and communicate than about a long history. Researching the role and asking good questions also signals more than years of experience does.
A: Usually, yes. Experienced interviewers notice the tells: unnatural pauses before answers, eyes tracking across a screen, and phrasing that's suddenly more polished than your conversational speech. It reads as dishonest and the downside of getting caught is far worse than giving a slightly imperfect answer. Prepare beforehand so you're not tempted to rely on it live. Resumatic · Interview Prep Frequently asked questions For most roles, two to four focused hours is enough, spread across the week before rather than crammed the night before. The bulk of that should go to mapping your resume claims to stories and rehearsing your opener out loud. Senior or highly technical roles may need more, but past about five hours you’re usually buying reassurance, not better answers. Keep it under 90 seconds and structure it as a short arc: where you are now professionally, one or two highlights that connect to this specific role, and why you’re interested in this job. Skip your full work history and anything personal. Rehearse it out loud and time it, because this is the most predictable question and the one people botch most often. Yes, a small set of notes is fine and often looks prepared rather than unsure, especially the questions you want to ask them. In a remote interview you can keep brief notes off-screen too. The key is that they’re glanceable prompts, not a script you read from, since reading your answers is obvious in person and on camera. Lean on transferable examples from school, internships, volunteer work, or projects, and prepare them the same way you’d prepare paid work: situation, what you did, result. Interviewers for entry-level roles expect this and care more about how you think and communicate than about a long history. Researching the role and asking good questions also signals more than years of experience does. Usually, yes. Experienced interviewers notice the tells: unnatural pauses before answers, eyes tracking across a screen, and phrasing that’s suddenly more polished than your conversational speech. It reads as dishonest, and the downside of getting caught is far worse than giving a slightly imperfect answer. Prepare beforehand so you’re not tempted to rely on it live.
Alex Khamis, CPRW, is the cofounder of Resumatic and the founder of Final Draft Resumes. He moderates r/resumes (1.2M+ members) and has personally written resumes for over 1,200 professionals across executive, technical, and career-transition roles since 2019, which is where the patterns in this piece come from. LinkedIn | About Resumatic If you want the resume you'll be defending in that room to be clean, current, and ATS-ready before you start prepping, Resumatic is free to start. Most people have a solid first draft in about 20 minutes, and the bullet rewriter is on the free tier. Then do the harder work that this article is actually about: rehearse how you'll back up every line of it, out loud, until you can defend the impressive numbers as easily as you wrote them.
