How to Prepare for a Job Interview: A 7 Day Plan (2026)

Most people prepare for interviews by reading. They open a list of common questions, nod at the sample answers, feel briefly reassured, and then discover on the call that reading an answer and saying one out loud are completely different skills. The gap between those two is where good candidates lose offers.

This is the plan I give people who have a week. It is built around one rule: every day ends with something you said out loud, not something you highlighted. If your interview is in two days, compress it by doing Days 1 and 2 in one sitting and skipping Day 5.

Day 1: Read the job description like a rubric

The job description is not marketing copy. It is the scoring sheet the panel will use, written in advance and in public. Copy it into a document and split it into three columns: hard requirements, soft requirements, and the words that repeat.

• Hard requirements are the things you either have or you do not. Years, tools, domains, certifications.
• Soft requirements are the coded ones: 'comfortable with ambiguity' means the team is reorganising, 'cross functional' means you will spend half your time in other people's meetings.
• Repeated words are the ones the hiring manager wrote themselves rather than pasted from a template. Those are the ones your answers should echo.

For every hard requirement, write one line naming the project where you did that thing. If a requirement has no line, that is a gap, and gaps are handled by acknowledging them early rather than hoping nobody asks. The same vocabulary exercise should already have shaped your resume before you applied.

End of day output: a one page requirement map with a project name next to each row.

Day 2: Research the company past the homepage

Anyone can quote the about page, which is exactly why quoting it signals nothing. Spend 45 minutes in four places instead: the latest funding or earnings note, the engineering or product blog, recent Glassdoor and Blind posts about the team, and the LinkedIn profiles of the people interviewing you.

You are looking for three specific things: what changed for them in the last six months, what problem the role exists to solve, and one thing you can credibly say you find interesting. That last one is the raw material for the question they will ask about motivation.

Write it down as three sentences. If you cannot compress your research into three sentences you have not understood it, you have only collected it.

Day 3: Build the six story bank

Almost every behavioral question in existence is a request for one of six stories. Write these six once and you can answer forty questions without inventing anything under pressure.

1. A project you led end to end, with a number attached to the outcome.
2. A conflict with a colleague or stakeholder that you resolved without escalating.
3. A failure that was genuinely yours, and what you changed afterwards.
4. A time you influenced a decision without having authority over it.
5. A time you worked under a deadline or constraint that forced a tradeoff.
6. A time you learned something unfamiliar fast because the work required it.

Each story gets the same shape: situation in one sentence, your specific task, the actions you personally took, and a result with a number. That last part is not optional. 'It went well' is not a result. 'Cut onboarding time from nine days to four' is a result. This is the STAR structure and it holds up because interviewers are taking notes in that order.

Keep each story to 90 seconds spoken. Time it. Most people write two minutes of material and deliver four.

Day 4: Drill the five questions you will definitely get

There are five questions that show up in nearly every loop regardless of role or seniority. Prepare these five properly and the rest is improvisation on top of your story bank.

• Tell me about yourself, which sets the frame for everything after it.
• Why do you want to work here, which tests whether you researched or applied in bulk.
• Why should we hire you, which is really asking what the team gets that it does not have now.
• What are your strengths and weaknesses, where the weakness half is the only half being scored.
• Do you have any questions for us, which is the one candidates treat as a formality and interviewers treat as a signal.

The opener deserves the most rehearsal because it is the only answer you fully control the timing of. A present, past, future structure in under 90 seconds beats a chronological life story every time.

For the weakness question, pick something real that has a cost and a fix attached, not a strength wearing a costume.

And write your closing questions in advance, one per interviewer type, because the recruiter, the hiring manager and the peer all need a different question.

Day 5: Run a spoken mock round

This is the day people skip, and skipping it is why prepared candidates still ramble. Reading your notes creates the feeling of readiness without the skill. You need at least one round where questions arrive in an order you did not choose, with follow ups you did not script.

Two workable options. Get a friend to run 30 minutes off your requirement map, or run an AI mock interview that asks the follow up questions a real hiring manager would ask and gives you a transcript afterwards. The transcript matters more than the score, because the fix is almost always visible in your own words: filler at the start of every answer, three sentences of context before the point, no number at the end.

Score yourself on three things only. Did the answer start with the point. Did it stay under 90 seconds. Did it end with a result. Fix in that order.

Day 6: Logistics, numbers and the setup

Boring day, cheapest wins. Handle everything that could go wrong before it can go wrong on the call.

• Test the meeting link, camera, microphone and headphones on the actual platform, not a different one.
• Check the interviewer names and pronunciations, and have the panel list open during the call.
• Fix your background and lighting, with the light in front of you rather than behind.
• Decide your salary range with a reason attached, because compensation often comes up in the first call.
• Print or open your requirement map, your six stories in bullet form, and your questions.

On the number, have a researched range and a sentence explaining how you arrived at it. Candidates who answer with a flat figure and no reasoning leave money on the table before the loop even starts.

If it is a recruiter phone screen rather than a video round, the rules change slightly: shorter answers, more energy in the voice, and no visual cues to lean on.

Day 7: The last 60 minutes

Do not cram. Nothing you learn in the last hour will be retrievable under pressure, and reading new material right before a call actively crowds out the stories you already rehearsed.

1. Sixty minutes out: read your three research sentences and your six story headlines, once.
2. Thirty minutes out: say your opener out loud twice, standing up.
3. Fifteen minutes out: close every tab you do not need, silence notifications, get water.
4. Five minutes out: join the call early and sit in silence rather than rehearsing.

If nerves are the problem rather than preparation, the fix is physical, not mental. Slow the exhale, drop the shoulders, and speak the first sentence slightly slower than feels natural. Pace is the single most controllable variable in how prepared you sound.

If the round is technical

Everything above still applies, but add two things. Narrate while you work, because silence reads as being stuck even when you are thinking clearly. And restate the problem in your own words before writing anything, which catches the misread requirement that sinks otherwise correct solutions.

For coding rounds specifically, pattern coverage beats problem volume. Knowing the handful of recurring shapes gets you further than grinding hundreds of problems at random.

For system design, the same logic holds with a smaller set of repeatable structures.

After the interview

Write down every question you were asked within ten minutes of hanging up, while it is still accurate. That list is the single best prep material for your next loop, and if there is a second round with this company it is close to the exact syllabus.

Then send a short follow up the same day that references one specific thing from the conversation. It rarely wins the offer on its own, but it keeps you in the debrief conversation.

Common questions

How long should preparing for an interview take? Around six to eight hours spread across a week beats the same hours crammed into one evening, because spacing is what makes the stories retrievable under pressure.

How do you mentally prepare for a job interview? By removing uncertainty rather than by building confidence. Confidence follows from having said your answers out loud, knowing the panel names, and having tested the link.

What if you get a question you did not prepare? Buy three seconds honestly, with 'let me think about that for a second', then map it to the closest story in your bank. Almost every unexpected question is a familiar one in different clothing. If you want your own examples surfaced while you talk rather than recalled from memory, that is exactly what a live interview assistant is for.