In eight years of coaching professionals through job searches, the most common thing I hear after a missed interview is some version of: 'I knew what I wanted to say, I just froze.' Sometimes that is true -- nerves do strange things in high-pressure moments. But more often, when I ask what they prepared, the answer is something like 'I read through the job description the night before' or 'I looked at their website for a few minutes.' The freeze is usually not a nerve problem. It is a preparation problem that looks like a nerve problem once you are sitting in the chair.
Why most people show up under-prepared
Job seekers spend hours tailoring their resume and worrying about the ATS -- and then treat the interview as improvisation. Part of this is understandable: interviews feel personal and harder to script than a document. But the candidates who consistently get offers are not better performers under pressure. They are more prepared, and preparation is almost entirely separable from talent. A 2014 study published in the Journal of Applied Psychology found that candidates who engaged in deliberate behavioral preparation -- specifically rehearsing stories from their work history -- performed measurably better on competency-based interview questions regardless of prior interviewing experience.
Step 1: Research the company and role (45 minutes)
Forty-five minutes of real research before an interview puts you ahead of a large share of candidates. You are not looking for encyclopedic knowledge. You are looking for two or three specific things you can reference naturally in the conversation to show you thought about the role before you walked in.
- ▸Read the company's 'About' page and any recent news or press releases. Look for a product launch, a partnership announcement, or a mission statement that connects to why you are applying.
- ▸Find the team or department page on LinkedIn. If you can identify your potential manager, spend five minutes reading their recent posts or articles.
- ▸Look at Glassdoor reviews, not to find drama, but to understand what employees consistently mention about the culture, pace, and challenges.
- ▸Read the job description three more times. Highlight the verbs: 'manage,' 'build,' 'grow,' 'optimize.' These are the outcomes the employer cares about most.
- ▸If the company is publicly traded, skim the most recent earnings summary or investor letter for ten minutes. The business priorities will surface clearly.
The question research helps you answer
Every interview eventually includes some version of 'Why us?' Candidates who have done thirty minutes of real research answer this specifically -- a product decision they found interesting, a problem the company is publicly trying to solve, something they noticed about the team's work. Candidates who haven't answer it vaguely. The difference is immediately audible to someone who has been hiring for any length of time.
Step 2: Build your STAR stories (60 minutes)
The STAR format -- Situation, Task, Action, Result -- is the structure behind almost every strong behavioral interview answer. You do not need to memorize scripts. You need three to five real stories from your work history that you know well enough to tell naturally, in about two to three minutes each, and that map to what the job description is asking for.
STAR format
Situation: Set the scene in one or two sentences. Task: What were you responsible for in that situation? Action: What did you specifically do? This is the longest part -- be concrete. Result: What changed because of what you did? Use a number wherever you can find one.
STAR story example
S: 'Our team was midway through a platform migration when a key vendor pulled their contract with two weeks' notice.' T: 'I was the project lead, responsible for finding a path forward without losing the launch date.' A: 'I ran an emergency vendor assessment over 48 hours, negotiated a short-term extension with the original vendor for continuity, and onboarded a new vendor in three weeks by running the integration in parallel with other workstreams.' R: 'We launched on schedule. Budget impact was 4% over the original estimate, and we ended the year with a stronger vendor relationship than we had started with.'
Build your five stories by reading the job description and identifying the competencies it rewards: leadership, problem-solving, stakeholder management, technical judgment, whatever the role emphasizes. Then match each one to a real story from your history. If a story has no number in the result, try harder to find one. Numbers make stories both memorable and credible -- and the same principle that makes resume bullets stronger applies to interview answers.
Step 3: Prepare your questions (15 minutes)
Interviews are two-way conversations, and candidates who ask strong questions leave a better impression than those who say 'I think you covered everything.' The questions you ask also help you evaluate whether the role is actually right for you -- which matters more than most candidates let themselves consider during a search.
- ▸'What does success look like in this role at six months and at one year?'
- ▸'What are the two or three things the team is most focused on solving right now?'
- ▸'How would you describe the decision-making culture on this team?'
- ▸'What brought you to this company, and what has kept you here?'
- ▸'Is there anything about my background that gives you hesitation about this role that I could address?'
The last question is the most useful
Asking whether your background raises any hesitations is uncomfortable, but it is the most useful question in the room. It gives you the chance to address a concern the interviewer might carry silently into their evaluation rather than raising it with you. In eight years of coaching, I have never seen a candidate lose a role by asking it. Most candidates who do ask it say the tone of the conversation shifted noticeably after they did.
Step 4: Practice out loud
Rehearsing interview answers silently is nearly useless. The gap between 'I know what I want to say' and actually saying it coherently in two minutes -- while someone watches -- is enormous, and the only way to close it is to practice out loud. This does not mean memorizing scripts. It means running through your STAR stories at least twice each, out loud, before the day arrives.
- ▸Time yourself. A two-to-three minute answer that covers all four STAR parts is the right length for most behavioral questions. Past four minutes, cut.
- ▸Record yourself once if you can tolerate it. You will hear filler words, pacing problems, and places where the story loses energy in a way that mental rehearsal never surfaces.
- ▸Practice with another person if possible -- a friend, a partner, anyone willing to sit across from you for twenty minutes and ask 'tell me about a time when.'
- ▸Prepare a crisp two-minute answer for 'tell me about yourself.' This is almost always the first question, and the one candidates are least ready for despite knowing it is coming.
'Tell me about yourself' -- the structure that works
Current role and relevant context (one sentence), background most relevant to this specific job (two sentences focused on what the role requires), and what brings you to this role specifically (one sentence). Not your life story, not a resume walkthrough. A four-sentence pitch aimed at this job, delivered as if you have thought carefully about why it is the right next move -- because you have.
The day-before checklist
- ▸Confirm the interview time, format (video, phone, or in-person), and who you will be speaking with.
- ▸Save the job description and your resume somewhere you can reference them immediately before you log in or walk in.
- ▸If it is a video interview, test your camera, microphone, and background. Log in with the exact link five minutes early.
- ▸If it is in-person, confirm the location, how long the commute takes, and plan to arrive ten minutes early.
- ▸Get seven to eight hours of sleep. Interviews require full cognitive function, and the research on performance under sleep deprivation is unambiguous.
What to do when you blank in the interview
Almost every candidate blanks at some point -- a question arrives that they didn't prepare for, or a story falls apart mid-sentence. The way to handle it is simpler than it feels in the moment.
- ▸Pause and say: 'That's a good question -- let me think about that for a second.' Silence for three to five seconds reads as thoughtful, not lost.
- ▸If you can't recall a strong example, be honest: 'I don't have a perfect match for that exact situation, but a related one was...' and use your nearest STAR story. Honest redirection reads better than a fumbled improvisation.
- ▸If you lose your thread mid-answer, stop and reset: 'Let me back up -- what I want to make sure I convey is...' Interviewers do not penalize a clean restart.
- ▸If a question is genuinely unclear, ask: 'Could you say a little more about what you are looking for there?' This is a completely normal thing to say.
Key takeaway
Interview preparation is not about predicting every question. It is about knowing your own stories well enough to adapt them to any question, having done enough research to sound like someone who thought about this role before the day arrived, and having practiced out loud enough that your answers come out as a conversation rather than a performance. Two to three hours of focused preparation is enough to change how an interview feels -- and how it goes. See also: how to tailor your resume to the job description and what recruiters actually look for for the full picture of what gets you to the interview in the first place.