How to Prepare for an Interview: A 7-Day Checklist and Timeline

Most people prepare for an interview the same way: skim the company website, reread their resume, and hope the questions are friendly. Then the interviewer asks for a specific example of handling a conflict, and the best story they have comes to mind on the drive home.

Knowing how to prepare for an interview is mostly a sequencing problem. If you do the right work in the right order, you walk in with a clear map of what the employer needs, five to eight stories that prove you can do it, and logistics that won't distract you.

This guide gives you a seven-day timeline you can compress into two days if needed, with the exact output for each day, a story-bank method, logistics checklists for in-person and video interviews, and a minute-by-minute plan for the morning of.

How to prepare for an interview: the 7-day plan at a glance#

Here's the full plan. Each day has one focus and one concrete output, so you always know when you're done. Most days take 45 to 90 minutes.

The time isn't spread evenly. Story building and rehearsal take the most effort because they change what you say in the room. Reading about the company feels productive, but it has a lower payoff per hour.

If you have less than a week#

Interviews often get scheduled for the next day. Compress the plan by keeping the steps that change your answers and dropping the rest.

Want this as a printable list? The free interview prep checklist walks through the week before, the day of, and the follow-up in order.

Step 1: Decode the job description (7 days out)#

Every interview question traces back to a need the employer wrote down, often badly, in the job description. Your first job is to translate the posting into a short list of competencies you'll be tested on.

Build a requirement map#

Print or paste the job description and mark it up. Highlight required skills, underline responsibilities, and circle anything repeated. Then group what you found into five to seven competencies, such as "stakeholder management," "SQL and reporting," or "handling escalations."

For each competency, write your strongest evidence next to it. If a line has no evidence, that's a gap you need to prepare to address honestly.

If you're not sure which terms matter most, the job description keyword finder pulls out the skills and qualifications a post emphasizes. The same method appears in the guide on how to find keywords in a job description.

Find the problem behind the posting#

Companies hire to solve a problem: a team that's overloaded, a new product launch, a process that keeps breaking, a key person who left. Look for clues in phrases like "fast-growing," "build out," "first hire," or "improve." If you can name the likely problem, you can frame every answer around solving it.

Step 2: Research the company, team, and interviewers (6 days out)#

Research has one purpose: to give you material you'll actually use in answers and questions. Set a 60-minute timer and capture findings in a one-page brief, not a pile of open tabs.

Where to look and what to note#

• The company's own site. Products, customers, mission, and the careers page, which often describes how teams work and grow.
• Recent news and announcements. Launches, funding, acquisitions, layoffs, new leadership. Note the date of anything you plan to mention.
• The team's public work. Engineering blogs, design case studies, conference talks, published reports, or social posts from team members.
• Interviewer profiles. Check LinkedIn for each interviewer's role and tenure. You're looking for common ground and their likely priorities, not personal details.
• Customer and employee reviews. Read them for patterns, and treat single angry reviews with skepticism.
• Competitors. Know two or three by name and one way this company differs.

A one-page research brief#

Keep your brief short enough to reread in five minutes the morning of the interview.

Turn research into better answers#

Research only pays off when it shows up in what you say. The test is simple: could another candidate say the same sentence about a different company? If so, it isn't specific enough yet.

The "after" version does three things: it names a real, dated fact, connects it to your experience, and points to a problem you can help with. Aim for two or three research details like this across the whole interview, not one in every answer.

What to research for each interview stage#

Your research should get deeper as you move through the process. A recruiter screen needs basics. A final round needs a point of view.

Step 3: Build your story bank (5 days out)#

This is the most valuable hour and a half in the whole plan. Most interviews today are at least partly structured: interviewers ask set questions about how you've handled real situations, then score your answers against the competencies the job requires.

Why stories matter more than polished answers#

Employers use structured interviews because they work. The U.S. Office of Personnel Management describes the structured interview as among the most valid assessment tools available for predicting job performance. A 2022 research review summarized by the Society for Industrial and Organizational Psychology ranked structured interviews highest among common selection methods.

For you, this means interviewers are listening for specific evidence: what you did, how you did it, and what happened. A generic answer scores low no matter how confident it sounds.

Choose six to eight stories that cover the most ground#

You don't need a different story for every question. You need a handful of strong, flexible stories that each prove several competencies. Employers consistently value teamwork, problem-solving, and communication; NACE's 2026 survey found those among the attributes employers most want to see, and noted that more than half of respondents cited 10 or more skills they look for.

Pick stories from this list of situations, aiming to cover each at least once:

• A result you're proud of, with a number attached
• A problem you solved that others had given up on
• A conflict or disagreement with a coworker, manager, or client
• A mistake or failure, and what you changed afterward
• A time you led without formal authority
• A time you had to learn something fast
• A deadline or priority clash you handled
• A time you influenced a decision with data or persuasion

Map stories to competencies#

Make a simple grid. Stories go down the side, competencies from your requirement map go across the top, and you mark which story proves what. Any competency with no mark needs a new story.

Outline each story with STAR#

Write each story as four short lines using the STAR method: situation, task, action, result. Outline only; scripts sound robotic. Most of your words should go to the action and the result.

If you have a story but can't get the structure right, the STAR method answer generator turns a rough description into a structured outline you can edit. For more practice prompts, see the full list of behavioral interview questions.

Step 4: Prepare for the questions you're most likely to get (4 days out)#

Beyond behavioral questions, a short list of standard questions shows up in most interviews. Prepare notes, not scripts, for each.

Each of these has a detailed guide: tell me about yourself, why do you want to work here, why are you leaving your job, your greatest weakness, where you see yourself in 5 years, and salary expectations.

Predict the role-specific questions#

Standard questions are only half the interview. The rest come from the job itself. Go back to your requirement map and write one likely question per competency, such as "Walk me through how you'd handle a vendor who misses a delivery date." The interview question generator can suggest likely questions from the job title and description if you want a starting list.

Know your resume line by line#

Interviewers often walk through your resume in order and ask about whatever catches their eye. Before the interview, read every line as if you were a skeptical stranger. For each role, prepare one sentence on why you joined, one on your biggest result, and one on why you left. For any gap longer than a few months, prepare a brief, matter-of-fact explanation; the guide to explaining an employment gap shows how to keep it short. If a bullet makes a claim you can't expand on for two minutes, either prepare the story or soften the bullet.

Prepare for the gaps#

Look at the gaps on your requirement map. For each one, prepare a short, honest answer with three parts: what you have that's close, how you'd close the gap, and evidence that you learn fast. Interviewers rarely reject people for one gap. They reject people who get defensive about it.

Step 5: Rehearse out loud and run a mock interview (3 days out)#

Reading your notes is not the same as practicing. The problems that hurt candidates, such as rambling, filler words, burying the result, and losing the thread, only show up when you speak.

How to run a useful mock interview#

1. Pick eight questions: three standard, four behavioral from your story bank, and one curveball you haven't prepared.
2. Find an interviewer: a friend, a mentor, a career center adviser, or an AI practice tool. Give them the questions and the job description.
3. Record the session on your phone or computer, video if the real interview is on video.
4. Answer at full length without pausing to restart. Recovering from a stumble is part of the skill.
5. Ask for two pieces of feedback: what was strongest, and what was least clear.
6. Watch the recording once and write down your top three fixes.
7. Repeat only the weakest two answers the next day.

If you don't have a practice partner, the mock interview practice tool asks realistic questions with follow-ups and gives structured feedback. There's more on how to get the most from it in the guide to AI mock interview practice.

Fix the most common delivery problems#

Your recording will show you which of these you need to work on. Most people have two or three.

Step 6: Prepare your questions and your close (2 days out)#

Interviews end with "Do you have any questions for us?" Having none is a common way to lose a close decision, because it suggests low interest or weak preparation.

Choose questions that help you decide#

Prepare five questions and expect to ask two or three. Good questions are ones you actually need answered. Strong categories include:

• Success: "What would make someone in this role a clear success after six months?"
• Challenges: "What's the hardest part of this job that the description doesn't mention?"
• Team: "How does the team decide what to work on each quarter?"
• Growth: "How have people in this role grown over the past few years?"
• Process: "What are the next steps, and when should I expect to hear back?"

Avoid questions the website answers, and save detailed salary and benefits questions for the recruiter or a later stage unless they raise it. The guide on questions to ask in an interview has options for every interviewer type.

Write a 20-second close#

At the end, take a moment to summarize your fit. It's your last chance to connect your strengths to their needs.

Step 7: Handle logistics the day before (1 day out)#

Logistics problems cause disproportionate stress. A late train, a dead laptop battery, or a wrong conference room can wreck your first five minutes, and the first five minutes shape how the rest is heard.

The day-before checklist#

• Confirm the date, time, time zone, and interviewer names
• Save the address, entrance, parking, and building security instructions, or the video link and meeting ID
• Choose and try on your outfit, matched to the company's dress norms
• Print three to five copies of your resume and your list of questions
• Pack ID, notebook, pen, water, and any portfolio or work samples
• Test camera, microphone, lighting, and internet for video interviews
• Charge your phone and laptop, and plan a backup connection
• Reread your research brief and story bank once, then stop

What to wear#

Dress norms vary more than they used to, so base your choice on evidence rather than habit. Look at photos on the company's careers page or social accounts, or simply ask the recruiter what people usually wear to interviews.

• When in doubt, go one step more formal than what employees wear day to day.
• Choose clothes you've worn before so nothing pinches, gapes, or needs adjusting.
• For video, pick solid colors and check them on camera; busy patterns can flicker on screen.
• Keep accessories and fragrance minimal so nothing distracts from what you're saying.

Logistics by interview format#

The details change with the format. Use this comparison to make sure nothing gets missed.

For format-specific advice, see the guides to video interview tips and phone interview tips.

Interview day: a timeline from wake-up to walk-in#

The morning of the interview is for warming up, not preparing. Here's a sample schedule for a 10:00 a.m. interview. Adjust the times to your commute.

1. 7:00 a.m. Wake at your normal time and eat a familiar breakfast.
2. 8:00 a.m. Reread your research brief and the top three stories. Ten minutes, no more.
3. 8:15 a.m. Say your introduction and one story out loud once.
4. 8:45 a.m. Get dressed and check your bag against your packing list.
5. 9:15 a.m. Leave with a 20 to 30 minute buffer for traffic or transit delays.
6. 9:40 a.m. Arrive nearby. Use the restroom, silence your phone, take a few slow breaths.
7. 9:50 a.m. Check in at reception. Be polite to everyone you meet, since you can't know who will be asked for an impression.
8. 10:00 a.m. Greet your interviewer by name, and start with a steady first answer.

For a video interview, replace the commute with a final tech check at 9:30, then close every app that could pop up a notification, and join three to five minutes early.

The first five minutes#

Interviewers form impressions quickly, and your first answer is usually "tell me about yourself" or a variation. Know your opening two sentences cold. Everything after that can be more conversational.

How to adapt your preparation to the interview format#

The seven-day plan covers most interviews, but some formats need extra preparation. Plan for the specific format as soon as you know it.

Technical interviews need a longer runway than a week. If you're facing coding or system design rounds, use the technical interview prep guide for a multi-week study plan.

Managing nerves without overpreparing#

Some nerves help. They sharpen your attention. The goal isn't to feel calm; it's to perform well while feeling a bit nervous.

What helps#

• Rehearse your opening. Nerves peak in the first minute, so a well-practiced start buys you time to settle.
• Slow your breathing. Breathe in for four counts and out for six, a few times, right before you walk in or join the call.
• Reframe the interview as a two-way conversation. You're also evaluating them, which shifts your focus from being judged to gathering information.
• Bring notes. Knowing your key stories are on paper reduces the fear of going blank.
• Accept pauses. Saying "Let me think about that for a second" sounds thoughtful, not unprepared.

What doesn't#

• Rehearsing until midnight the night before
• Memorizing answers word for word
• Comparing yourself with imagined other candidates
• Replaying one weak answer during the rest of the interview

After the interview: the first 24 hours#

Preparation doesn't stop when the interview ends. What you do in the next day sets you up for the next round and the next interview.

Debrief within an hour#

Right after the interview, spend 10 minutes writing down the questions you were asked, the stories you used, what landed, and anything you'd change. Note interviewer names and anything personal they mentioned that you could reference in a thank-you. The interview tracker keeps rounds, interviewers, and follow-ups in one place.

Send a specific thank-you note#

Send a short thank-you email within 24 hours to each interviewer if you have their addresses, or ask the recruiter to forward it. Mention one specific topic from your conversation and restate your interest in one sentence. The guide on thank-you emails after an interview has templates, and the thank-you email generator drafts one from your notes.

Plan your follow-up#

If the interviewer gave you a decision date, wait until a business day after it passes before checking in. If they didn't, a polite note after about a week is reasonable. The guide on how to follow up after an interview covers timing and wording.

Preparation mistakes that cost candidates offers#

Most interview prep goes wrong in predictable ways. Check your plan against these before the week starts.

• Researching instead of rehearsing. Hours on the company website feel productive, but they don't change how clearly you answer. Cap research at an hour for most rounds.
• Preparing answers but not stories. Polished answers to "What's your greatest strength?" fall apart when the follow-up is "Give me an example." Prepare the example first.
• Using the same stories for every company. Your story bank is reusable, but which stories you lead with should change with each requirement map.
• Ignoring the gaps. Hoping they won't ask about the skill you lack is not a plan. Prepare a calm, honest answer.
• Practicing only in your head. Silent review hides rambling, filler, and weak endings.
• Skipping the questions you'll ask. "No, I think you covered everything" is a missed chance to show interest and judgment.
• Leaving logistics to the morning. A broken link or wrong building is avoidable stress at the worst possible moment.
• Treating each round as the first. Later rounds expect deeper knowledge of the team and a view on how you'd approach the work. Update your brief between rounds.

Next steps: put your plan on the calendar#

The difference between candidates who prepare well and those who don't is rarely talent. It's whether the work happens in a planned sequence or in a panic the night before.

Today, do three things:

• Block the seven prep sessions on your calendar, working backward from your interview date.
• Start your requirement map from the job description, since every later step builds on it.
• Write down the first three stories that come to mind for the competencies you found.

If your resume needs a refresh before the interview, make sure every story you plan to tell is reflected in your bullet points; interviewers often ask about whatever is on the page. Resume Maker's AI assistant can revise bullets directly in your resume, so your resume and your interview answers tell the same story.

Each round you complete makes the next one easier, because your story bank, research brief, and question list carry over. Keep them in one document and update them after every interview.