Knowing what to do before an interview is less about a checklist and more about walking in with three things locked: a real read on the company, a handful of story-driven answers, and your own career narrative cold. Most candidates think they're prepared because they printed the resume, picked an outfit, and skimmed the homepage. Then a question lands ("Why this company?"), and the answer comes out as a generic shape instead of a specific story.
The candidates who land offers prepare for the conversation, not the questions. They rehearse stories, not bullet points, and study the company's last earnings call, not just its About page. When behavioral interview questions come up, they have specific situations ready. For broader frameworks, our interview tips guide covers the mindset side. Here's what to do in the days before you walk in.
What to do before an interview, in order of impact
The mistake most people make is treating prep as a checklist where every item carries equal weight. It doesn't. Research and story prep account for about 80% of how you come across in the room. Logistics like outfit, route, and water bottle are necessary, but they're not what wins. Spend your prep time accordingly.
Here's the order of impact, highest to lowest:
- Research the company beyond surface level (the single biggest differentiator)
- Build 5–7 story-driven answers to behavioral questions
- Know your own narrative cold: why this role, why now, why you
- Prepare specific questions that show you've done the work
- Handle logistics so they're invisible
Most things to do before an interview cluster around items 4 and 5, which is why most candidates sound the same. The first three are what separate you.
Research the company beyond surface level
"Visit their website" is the prep advice everyone gives. It's also the bare minimum. Hiring managers can tell within five minutes whether you actually understand the business or just memorized the homepage. The candidates who stand out go three layers deeper.
Layer 1: What the company says about itself.
Read the About page, the careers page, the company blog, and any recent press releases. Note the language they use. If they call themselves "operators" or "builders" or "scrappy," that's a culture signal you can mirror.
Layer 2: What outsiders say about it.
Check the most recent funding announcements on Crunchbase or PitchBook. Read the last two earnings calls if it's public. Skim Glassdoor reviews, but read them for patterns. Three people complaining about the same VP means something; one disgruntled ex-employee means less. Look at the company's competitors and have a quick opinion on how it's different.
Layer 3: Who's on your interview panel.
Look up every interviewer on LinkedIn. Note their tenure, their role before this one, and any content they've posted. If someone's been there eight years, they care about the long-term mission. If someone joined three months ago, they're still proving themselves and probably want to hire someone who'll make them look smart.
When you walk in able to reference the company's recent product launch, the strategic shift they announced last quarter, or a piece of content the hiring manager wrote, you've already separated yourself from 90% of candidates. That's what to do before a job interview that actually moves the needle.
Build 5–7 story-driven answers using a real framework
Behavioral questions sound like "Tell me about a time you…" and they're the part of the interview where most candidates lose ground. Not because they don't have stories, but because their stories ramble, lack a clear outcome, or sound made up.
The fix is to build a small inventory of stories in advance. Five to seven is the right number. Each story should be ready to deploy against multiple question types. Use the STAR framework (Situation, Task, Action, Result) as scaffolding:
- Situation: The context in two sentences. Where, when, who.
- Task: What you were specifically responsible for.
- Action: What you did. Not the team. You.
- Result: The outcome, with a number if possible.
The Action step is where most stories collapse into "we" instead of "I." Interviewers want to know what you did, not what your team accomplished. Force yourself to name the specific decisions you made and the specific moves you owned.
Map your stories to common buckets:
- A time you led without authority
- A time you handled conflict with a coworker or manager
- A time you owned a mistake
- A time you turned around a failing project
- A time you persuaded someone to change their mind
- A time you delivered under a tight deadline
- A time you took initiative on something not in your job description
Most behavioral questions can be answered by adapting one of these seven. Rehearse them out loud (not in your head, out loud) until each one runs about 90 seconds and lands a clean result.
Know your narrative cold
Your career narrative is the through-line that connects your last job, your current job search, and this specific role. It's the answer to three questions you will get asked in some form: "Why are you looking?" "Why this company?" "Why this role?"
If those three answers don't fit together cleanly, you sound either confused or opportunistic. If they do fit, you sound like a candidate with intent. The narrative doesn't have to be dramatic. It just has to be specific and consistent.
Write your narrative out in three paragraphs the night before:
- Where you've been. Two or three lines on the arc of your career so far. Skip the chronology; lead with the theme.
- Why you're looking now. Be honest but framed forward. "I've taken that role as far as it goes for me; I want to build something at earlier stage" reads better than "my manager was difficult."
- Why this role at this company. Name something specific. A product, a market position, a hire they made recently. Generic enthusiasm reads as generic.
Practice the whole thing out loud once. Then practice the 30-second version. Then the 10-second version. You should be able to deliver any length on demand.
Prepare questions that prove you did the work
The interviewer will ask if you have questions. "No, I think you've covered everything" is the wrong answer. So is "What's the company culture like?" That's the question everyone asks and it doesn't show you've thought about anything specific.
Good questions reference something you learned in your research. Three categories to prepare from:
- About the role: "What does success look like in this role at the six-month mark versus the eighteen-month mark?"
- About the team: "You mentioned the team grew from four to twelve in the last year. How has the way decisions get made changed?"
- About the company: "I saw the recent pivot toward enterprise. How is that shaping what you're hiring for now?"
Prepare at least five so you have a few left if they get answered earlier in the conversation. The right questions can flip the dynamic. Instead of being evaluated, you're being treated as a peer.
What to do right before an interview
The last 60 minutes have one job: get you into the room calm, alert, and present. This is not the time for last-minute research or trying to memorize new answers. The work is already done.
- 90 minutes before: Eat something light. Low-blood-sugar interviews are how good candidates blank on easy questions.
- 60 minutes before: Re-read your STAR stories one time. Don't drill them. Just refresh.
- 30 minutes before: Arrive on-site (or set up your video space). Do not arrive early into the building. Wait outside or in a coffee shop. Walking in 25 minutes early reads as anxious; 10 minutes early reads as prepared.
- 5 minutes before: Two slow breaths. Adopt an expansive posture for 60 seconds. Glance at your career narrative summary. That's it.
What to do right before an interview is mostly what not to do: don't cram, don't check email, don't psych yourself out by re-reading the job description for the fifteenth time.
Handle logistics so they're invisible
These are the items every prep guide leads with. They matter, but they're the floor, not the ceiling. Get them done two days out so they're not eating prep time the morning of:
- Print three copies of your resume on decent paper.
- Confirm the address, the floor, the front desk procedure. For video, test the camera, the mic, the lighting, and the background.
- Lay out the outfit the night before. Aim one notch more formal than the company's daily dress code.
- Charge your phone, your laptop, and a backup if you have one.
- Have the recruiter's number saved in case anything goes wrong.
The point of locking logistics down early is so the morning of the interview, you have nothing left to think about except the conversation you're about to have.
What to leave at home
Some prep habits feel productive but quietly work against you on the day. They eat hours that would be better spent elsewhere, and worse, they often show up as stiffness or over-rehearsal the moment the conversation starts. Skip these:
- Memorizing answers word-for-word. You'll sound rehearsed and you'll panic the second a question lands slightly different from what you practiced.
- Trying to be impressive. Be specific instead. "Impressive" is generic; specific is memorable.
- Bringing up salary first. Let them open that conversation. The exception is if a recruiter has asked you for a range up front. Give a range, don't anchor on a single number.
- Apologizing for any gap in your experience. If they ask about something you haven't done, say what you have done that's adjacent and how you'd close the gap.
The pattern across all four: trust your judgment in the moment instead of trying to control it in advance. That's what preparation is supposed to buy you.
How Cook'd AI takes prep from scattered to sharp
Most candidates prepare by cobbling together tabs from Indeed, LinkedIn, a friend's advice, and three Glassdoor pages. The result is generic prep that produces generic answers. Cook'd AI was built to fix that.
Drop in the job description and your resume, and Cook'd generates a tailored interview prep plan: the specific behavioral questions this role is likely to surface, the company-research moves that matter for this stage and industry, and personalized STAR-story prompts pulled from your own experience. You walk in with answers that fit the actual role, not advice copy-pasted from a template. That's the difference between hoping you're prepared and knowing you are.
Ace your interview and prep with Cook'd AI today.
Cook'd AI builds your interview prep around the actual role, the company, and your own experience. No generic checklists.
Cook'd AI builds your interview prep around the actual role, the company, and your own experience. No generic checklists.
Frequently Asked Questions
How many days before an interview should I start preparing?
Three to five days is the sweet spot for most roles. That's enough time to do real company research, draft your STAR stories, rehearse them out loud, and refine your narrative without overcooking it. For senior roles or panel interviews, push to a full week. Less than two days and you'll be running on adrenaline; more than ten days and you'll forget what you prepared.
What are the most important things to do before an interview if I only have an hour?
If you have 60 minutes total, spend 25 on company research (their last big announcement, their main competitors, who's on your panel), 25 on drafting three quick STAR stories you can adapt to most questions, and 10 on writing your "why this role, why now" narrative in two paragraphs. Skip the rest. The first three are what carry you through the conversation.
Should I memorize my answers before the interview?
No. Memorize the structure of your stories and the key facts and numbers, but not the exact wording. Memorized answers sound rehearsed and they fall apart when the question is phrased even slightly differently than you expected. Rehearse out loud until the stories flow naturally; that's different from memorization.
What should you do before an interview the night before?
Lock logistics, not content. Lay out your outfit, print resumes, confirm the address or test the video setup, and go to bed at a normal hour. Read your STAR stories and narrative once, then put them down. Cramming the night before backfires; sleep helps recall more than re-reading does.
What if I don't have any impressive accomplishments to talk about?
You probably do; you're just defining "impressive" wrong. Interviewers want specific examples of judgment, ownership, and outcomes, not awards. A time you fixed a broken process, taught yourself something the team needed, or held a difficult conversation all count. The story matters more than the scale.
Answer
