How to Prepare for an Interview: A 7-Day Plan

By Peter Miller · Published October 21, 2026 · Last updated: October 21, 2026

13 min read

Most people prepare for an interview the night before. They skim the company website, read a list of common questions, panic a little, and go to bed late. Then they walk in and give answers that are fine but forgettable.

I don't blame them. Nobody teaches this. But after years of interviewing candidates and coaching people through their own interviews, I've noticed the ones who get offers rarely prepared harder. They prepared earlier and in a better order. They knew the job, they had stories ready, and they'd said those stories out loud before.

So here's how to prepare for an interview with a plan you can actually follow. It's laid out as seven days, but you can squeeze it into three if the interview's sooner. Each day takes 30 to 60 minutes. You'll get worksheets you can copy, examples of answers before and after preparation, and a checklist for the last 24 hours.

If your interview's tomorrow, skip to the "compressed plan" section near the end.

What good interview preparation covers

Preparation isn't memorizing answers. It's reducing the number of surprises. When you walk in, you want to know:

• What the job really involves and what problem they're hiring to solve.
• Who you're meeting and what each person probably cares about.
• Which of your experiences prove you can do the work.
• How you'll answer the questions almost every interviewer asks.
• What you want to ask them.
• The practical details: where, when, how long, what to bring, what you'd accept for pay.

If you've covered those six areas, you're prepared. Everything else is polish.

How to prepare for an interview: the 7-day plan

Day 1: Decode the job posting

Print the posting or paste it into a document. Go line by line and highlight every requirement, responsibility, and skill. Then rewrite each one as a question an interviewer could ask.

• "Manage multiple projects simultaneously" becomes "Tell me about a time you juggled competing deadlines."
• "Experience with stakeholder communication" becomes "How do you keep senior people informed?"
• "Proficiency in Excel" becomes "Walk me through a spreadsheet you built."

You'll end up with 10 to 20 likely questions. That list is your study guide for the week. Also note anything in the posting you don't fully understand. Those become questions you ask them.

Day 2: Research the company and the people

Give it 45 minutes, focused. You want:

• What they sell, to whom, and how they make money.
• One or two recent developments: a launch, an expansion, a new leader, a funding round, layoffs.
• Who you're meeting. Look up each interviewer's public professional profile. Note how long they've been there and what they work on.
• How the team you'd join fits into the company.

Write down one thing you find interesting or have a genuine question about. You'll use it when they ask "Why do you want to work here?"

Day 3: Build your story bank

Take your list of likely questions from day one and match each to an experience from your past. You'll notice the same few stories can answer many questions. Aim for five to seven stories that cover:

• A significant achievement relevant to this role.
• A mistake or failure and what you learned.
• A disagreement or conflict you worked through.
• A time you led or influenced without formal authority.
• A time you handled something new or unclear.
• A time you went beyond what was asked.

Write each in STAR form (situation, task, action, result), keeping situation and task to one sentence each. Our STAR method examples show what good ones look like.

| Story name | Posting requirement it proves | Result | Questions it answers |
|------------|------------------------------|--------|----------------------|
| [e.g. Vendor switch] | [Cost control] | [Saved X / cut Y] | [Conflict, budget, initiative] |
| | | | |
| | | | |
| | | | |
| | | | |
              

Day 4: Prepare the questions everyone asks

Some questions come up in nearly every interview. Prepare short, honest versions of each:

• Tell me about yourself. 60 to 90 seconds: what you do now, one or two relevant highlights, why this role. See how to answer tell me about yourself .
• Why do you want this job? Tie your skills to their problem and add the detail you found on day two.
• Why are you leaving your current job? Forward-looking, no complaints.
• What are your strengths? One or two, each with a quick example.
• What's a weakness? A real one with what you're doing about it. More in how to answer what are your weaknesses .
• Why should we hire you? A short summary of your best match to the posting.
• What are your salary expectations? A researched range.
• Do you have any questions for us? Always yes.

Before: Why do you want this job? "It seems like a great company and I think I'd learn a lot."
After: "Your team is moving support from email to in-app chat this year, and I ran that exact switch at my last job. I'd like to do it again with a bigger customer base and fix what I'd do differently the second time."

Day 5: Practice out loud

This is the day most people skip, and it's the one that matters most. Answers you've only thought about come out long, wandering, and full of "um." Answers you've said out loud three times come out clean.

• Record yourself answering five questions on your phone. Watch it once.
• Note filler words, answers over two minutes, and stories with no result.
• Do it again. You'll be noticeably better on the second round.
• If you can, do a mock interview with a friend. Give them your question list and ask them to throw in one surprise.

Before: "So basically, um, we had this, like, project that was kind of behind, and there was a lot going on, and I sort of stepped in..."
After: "Our product launch was three weeks behind. I rebuilt the schedule, got the client to agree to drop two features, and we shipped four days late instead of three weeks."

Day 6: Prepare your questions and your numbers

Write four or five questions for them. You'll use two or three. Good ones are specific to the role:

• "What would you want this person to have done in the first 90 days?"
• "What's the hardest part of this job that the posting doesn't mention?"
• "How does this team measure success?"
• "What made the last person in this role successful, or not?"

Then sort out the numbers. Research a salary range for the title and location using public data like the US Bureau of Labor Statistics occupational pages or salary ranges published in job postings (many states now require them). Know your minimum, your target, and your notice period. Here's a longer list of questions to ask at the end of an interview .

Day 7: Logistics and a light review

The day before, don't cram. Do the practical things:

• Confirm the time, time zone, address or video link, and the names of the interviewers.
• For in-person: plan the route and parking, and leave time for traffic.
• For video: test the link, camera, mic, lighting and internet on the device you'll use.
• Lay out your clothes. Print two copies of your resume. Charge your phone.
• Reread the job posting, your story bank, and your resume once. Then stop.
• Sleep.

The morning of the interview

You've done the work. The morning is about protecting it. Here's the routine I suggest.

Eat something. It sounds obvious, but a lot of people skip breakfast from nerves and run out of focus by the third interviewer. Something light is fine.

Do one warm-up out loud. Say your 60-second introduction once, in the shower or the car. Then say the result line of your best story. That's all. You're warming up your voice, not rehearsing everything again.

Reread three things, once. The job posting, your story bank, and your resume. Pay attention to dates and titles on the resume. If an interviewer asks why you left a job in 2022, you don't want to hesitate on which job that was.

Leave a buffer. For in-person interviews, plan to arrive in the area 20 minutes early and walk in five to ten minutes before your time. For video, sit down at your desk 15 minutes early, close every app you don't need, put your phone on silent and out of reach, and have a glass of water nearby.

Have a fallback. Save the recruiter's phone number. If the video link fails or you're stuck in traffic, call or email right away. A quick heads-up is forgiven. Silence isn't.

Reset your posture. Right before you go in, take a slow breath and drop your shoulders. You're not there to perform. You're there to have a focused conversation about work you've already done.

If you notice your mind racing, look at your story bank one last time and pick the one story you most want them to hear. Decide you'll find a way to tell it. Having one clear goal for the conversation does more for nerves than any breathing trick I know.

How preparation changes by interview type

Phone screen

Usually 20 to 30 minutes with a recruiter. Focus on your intro, why you're interested, your salary range, and availability. Keep your notes open. Our phone interview guide has a full checklist.

Video interview

Prepare the same content as in-person, plus the setup: eye-level camera, front lighting, quiet room, closed notifications. Do a test call with a friend on the same platform.

Panel interview

Find out who's on the panel and what each person does. Expect questions from different angles: the manager on results, a peer on collaboration, HR on culture fit. Read our panel interview tips .

Technical or skills test

Ask the recruiter what format to expect: live problem, take-home, presentation. Practice in that format. For coding or case interviews, practice thinking out loud.

Final round

Expect bigger-picture questions about judgment and priorities, and possibly a "first 90 days" question. Prepare a short plan for your first three months.

If your interview is tomorrow

No time for seven days? Here's the two-hour version, in order of impact:

• 30 minutes: Highlight the posting and write ten likely questions.
• 30 minutes: Match three or four stories to those questions, in STAR form, bullet points only.
• 30 minutes: Say your intro and three stories out loud. Record at least one.
• 15 minutes: Quick company research: what they do, one recent piece of news, who you're meeting.
• 15 minutes: Write three questions to ask, confirm logistics, lay out your clothes.

That's enough to walk in prepared. Go to bed.

Preparation mistakes I see constantly

• Researching the company for hours, the job for minutes. Interviewers care more that you understand the role than that you know the founding year.
• Memorizing word-for-word answers. They sound stiff and fall apart when the question is phrased differently. Memorize points, not sentences.
• Preparing stories with no results. Every story needs an ending. What changed because of what you did?
• Forgetting your own resume. Interviewers ask about anything on it. Reread it and be ready to talk about every line for two minutes.
• Skipping the practice. Thinking about answers isn't the same as saying them.
• Ignoring logistics. A dead laptop battery or a wrong time zone has ended more interviews than bad answers.

I have interviewed candidates who were clearly brilliant and still lost to someone less experienced, because the other person had prepared specific stories and they hadn't.

Prepare your resume as part of interview prep

Your interviewer's questions usually start from your resume. If a bullet says "managed vendor relationships," expect "Tell me more about that." If you can't back up a line with a story, consider rewording it before you send any updated version.

It's also worth checking how well your resume matches the posting. Run it through the free ATS resume checker with the job description. The gaps it shows are the requirements you'll need to prove most clearly out loud. If the employer wants a cover letter at a later stage, the cover letter generator can draft one from your resume and the posting. For a professional rewrite before a big final round, see HireFlow resume writing .

Start your prep today, not tomorrow night

Knowing how to prepare for an interview is mostly about starting early and practicing out loud.

• Day 1: turn the posting into questions.
• Day 3: build five stories with results.
• Day 5: practice out loud and record yourself.
• Day 7: logistics, light review, sleep.

Before day one, check your resume against the job posting so you know exactly which strengths to lead with and which gaps you'll need to explain.