Guides › Interview prep

How to prepare for a job interview in 3 days

By the MyPrepGuru team · Updated 2026-11-02 · 6 min read

Sometimes an interview arrives with a few days' notice. Maybe a recruiter called and asked if Thursday works, or a role you applied for weeks ago suddenly moved. Three days is not a lot, but it is enough to get meaningfully better prepared if you spend the time on the right things.

This guide is a practical plan. It is also honest about limits. Three days will not turn you into a different candidate, and no plan can promise a particular outcome. What it can do is make sure you walk in knowing the role, with your stories ready, and with a few rounds of out-loud practice behind you.

What three days can and cannot do

It can:

• Help you understand what the role is asking for and match your experience to it.
• Get your core stories and your opening answer into shape.
• Give you speaking practice so your answers come out clearly.
• Reduce avoidable surprises, such as not knowing what the company does.

It cannot:

• Create experience or skills you do not have.
• Make you an expert in a technology you have never touched.
• Replace the weeks of preparation that a very senior or highly technical role might need.

If the interview involves a coding test, case study, or portfolio review, put extra time into that format, because this plan focuses on the conversational part. Be realistic about which parts of the interview you can improve and which you cannot.

Before day one: a ten-minute setup

Gather these in one place:

• The job description (save a copy; postings get taken down).
• Your current resume.
• Any details from the recruiter: interview format, length, names of the interviewers, and the number of rounds.
• A way to record your voice, such as a phone.

Note down the format first. A short phone screen, a panel, and a technical deep dive all call for different emphasis.

Day 1: understand the role and your story

The goal of day one is to know what they want and what you will say about yourself. Plan about two to three hours, split across the day if needed.

1. Read the job description closely. Highlight repeated words and the top responsibilities. Postings sometimes list requirements in rough priority order, though not always.
2. Sort requirements into three buckets: strong match, partial match, and gap. Be honest. The gap list tells you what questions to expect and what you need an answer for.
3. Skim the company. Look at their website, product, and recent public announcements. You are looking for two or three specific things you can mention, not a research project.
4. Draft your "tell me about yourself" answer. Use a present, past, future structure and keep it near a minute and a half.
5. Check your resume against the posting. If you have a resume feedback tool, a keyword-overlap check can help you notice terms from the posting that your resume leaves out. MyPrepGuru's Resume Feedback gives a keyword and skill-overlap estimate with matched and missing terms. It is our own estimate and does not predict any real applicant tracking system's result, so use it as a prompt for editing, not a verdict. For more, see how ATS keyword matching works and tailoring your resume to a job description.

Day 1 output: a bucketed list of requirements, a drafted opening answer, and two or three company details.

Day 2: stories, questions, and your first mock

The goal of day two is to prepare real examples and practice them aloud. Plan three to four hours.

Morning: build your story bank

Choose four to six stories from your work that you can reuse. Cover a spread: a success, a mistake, a conflict, a time you led or influenced, and a time you learned something quickly. For each story, write only a few bullet points: situation, what you did, result. Do not write scripts. The STAR method gives a structure, and 25 behavioral interview questions shows which questions each story can serve.

Midday: predict the questions

Take your requirements list from day one. For each partial match or gap, write the question an interviewer might ask. For instance, if the posting asks for experience managing a budget and you have only managed a small one, expect "Tell me about your experience with budgets" and prepare an honest, specific answer. Predicting questions from a job posting walks through this more fully.

Afternoon: first spoken run

Answer your opening question and four or five others out loud, recording as you go. Listen back once. Note the problems: no result, too long, filler words, an unclear opening. Fix one or two, then redo them. If you want a full mock sitting, a tool like MyPrepGuru runs a screening round followed by a second round built from your pasted job description, then gives a scored report per dimension with quotes from your transcript. A mock is practice only, and it is not for use during a real interview. See how to use an AI mock interviewer for tips on getting value from one.

Day 2 output: a story bank, a list of predicted questions, and one recorded practice session with notes.

Day 3: polish, logistics, and rest

The goal of day three is to sharpen, not cram. Plan two to three hours and stop earlier than you think you should.

1. Second spoken run. Repeat the questions that went worst on day two. Ideally, do a full mock sitting and read the report, focusing on the one or two lowest-scoring areas rather than everything.
2. Prepare your questions for them. Write three to five thoughtful questions about the team, how success is measured, and what the first months look like. Avoid anything easily answered on their website.
3. Handle likely tricky topics. Think through your answer to "Why are you leaving?" and any gaps in your history. Keep answers honest, short, and forward-looking. If pay may come up, read salary expectations in interviews so you have a plan.
4. Sort the logistics. Confirm the time and time zone, the video link or address, who you are meeting, and how long it takes to get there. Test your camera, microphone, and internet if it is remote. Pick your clothes and have your resume and a notepad ready.
5. Stop early. The night before, do a light review of your bullet points, not a new practice marathon. Sleep matters more than another rehearsal.

Day 3 output: a final recorded run, questions for the interviewer, and logistics confirmed.

If you have only one day left

Compress it: read the posting and bucket requirements (one hour), draft your opening answer and three stories (one hour), then spend the rest answering questions aloud and fixing the worst one. Skip the nice-to-haves.

Common mistakes in short-notice prep

• Only reading, never speaking. Reading your notes feels like preparation but does not train the spoken skill. See practice out loud.
• Trying to memorize scripts. Memorize the outline instead.
• Researching the company for hours and neglecting your own stories.
• Ignoring the gaps. Interviewers may probe where your experience is thinnest, so have an honest answer ready.
• Practicing late into the night before. Tired is worse than slightly under-rehearsed.

Practice this

Today, do the one thing that makes the other steps easier: paste or print the job description and sort its requirements into strong match, partial match, and gap. Then answer your opening question out loud, once, with a timer. If you want a structured run, a MyPrepGuru mock interview can build its role-specific round from that same posting and give you a report with quotes from your own transcript.