A One-Week Interview Preparation Plan That Works
A seven-day interview preparation plan where each day produces something the next day uses: a research sheet, an answer bank, three stories and one full spoken mock.
If you have an interview in a week, spend it in a fixed order: research the role, write an answer bank, rehearse three stories, then practise out loud and finish with one full mock. Each day produces something the next day uses, so nothing is wasted and nothing gets crammed into the night before. Below is a one week interview preparation plan with a 45 to 60 minute focus for each day, the output it should leave behind, and a compressed version for when you have less notice.
What a good week of preparation produces
By the end of the week you should have four things in hand:
- A one-page research sheet on the role and the company.
- An answer bank of 8 to 10 questions written in your own words.
- Three rehearsed stories you can tell in about 90 seconds each.
- One full spoken mock interview, reviewed.
The order matters. Research comes before writing because you cannot choose which of your experiences to lead with until you know what the role needs. Writing comes before speaking because talking points on paper keep you from rambling while you find the shape of an answer. Speaking comes before polishing because the sound of your answer tells you what to fix; polishing wording first is work on the wrong thing.
The full schedule:
| Day | Focus (45–60 minutes) | Output |
|---|---|---|
| 1 | Read the job description and the company | Research sheet started |
| 2 | Turn requirements into questions | One-page sheet, five lines |
| 3 | Write the answer bank | 8–10 bullet answers |
| 4 | Build three stories | Three 90-second stories |
| 5 | Practise out loud alone | 20-minute routine, recorded once |
| 6 | Full mock and review | Reviewed mock, one answer rewritten |
| 7 | Light rehearsal and logistics | Calm, prepared, stopped |
Days 1–2: What do you need to know about the role before you write a single answer?
Start with the job description and read it for repeated verbs. If it says "own", "coordinate" or "debug" three times, those are the behaviours the interviewer will test. Underline them rather than reading the whole advert as a wish list.
Then make one page with five lines:
- The role in your own words, one sentence.
- Three requirements that appear more than once.
- Two things about the company you can say out loud without flattery, such as a product decision you find interesting or a market they have entered.
- One question you genuinely have about the job.
- The name and role of whoever you are meeting, if you know it.
Now turn every requirement into a question. "Works across teams" becomes "tell me about a time you had to get another team to do something they did not want to do". This list is the raw material for tomorrow's answer bank, and it is why research comes first: the questions you write are only as good as the requirements you noticed.
Day 3: How do you build an answer bank you can actually say out loud?
Write talking points, not scripts. A script collapses the moment the interviewer asks a follow-up; a few bullets let you rebuild the answer in the room. Aim for 8 to 10 questions covering four families:
- Tell me about yourself.
- A strength, with evidence.
- A failure or a conflict.
- Why this role, and why now.
Take the "tell me about yourself" question, where a draft usually goes wrong by reciting a CV. A weak version:
"I've been in operations for six years, I started as an analyst, then moved into team lead, and now I'm looking for a new challenge in a bigger company."
It is accurate and it tells the interviewer nothing they can use. The same facts, rebuilt as bullets:
"Six years in operations, mostly fixing delivery problems. Two things I'd point to: I ran the scheduling change that cut missed deadlines on my team, and I now train new analysts on it. I'm applying here because this role is the same problem at a larger scale, and that's the part of the work I'm best at."
The second version works because it leads with a summary, gives two pieces of evidence, and connects to the role. The facts did not change; the order did. If talking points feel stiff when you say them, the guide on how to sound natural with talking points in a job interview goes further.
Day 4: Which three stories will carry most of the interview?
Most behavioural questions can be answered from three well-chosen situations. Pick real ones you can re-angle:
- A delivery under pressure.
- A disagreement you worked through.
- A mistake you found and fixed.
Each story gets four beats, and each beat gets one or two lines:
- Situation: where you were, what was at stake, in one sentence.
- Decision: what you chose to do and why, including what you ruled out.
- Action: the two or three concrete things you did.
- Result: what changed, stated plainly. If you have no number, describe the change instead.
Keep each story to about 90 seconds spoken. That length gives the interviewer enough to probe without taking over the conversation. Write a skeleton with blanks and fill it from your own history:
"At ______, we had ______ coming up and ______ was at risk. I decided to ______ rather than ______, because ______. So I ______ and then ______. In the end, ______ changed, and I learned ______."
No invented details. If a story is thin, choose a smaller, real one; an honest small story beats an inflated large one under questioning. The greatest achievement interview answer page shows the same discipline applied to one question, and ownership interview questions helps when your story is about taking responsibility.
Day 5: How do you practise out loud without an audience?
Use a 20-minute routine, once or twice if you have the time:
- Five minutes: say your three stories aloud, one after another, without notes.
- Ten minutes: answer random questions from your bank, out loud, in full sentences.
- Five minutes: note what you stumbled on and why.
Record yourself once and listen back for three things: filler words, pace, and whether your point landed in the first sentence. Most people discover their answer only arrives at the end. That is fixable, and it is cheaper to fix today than in the room.
Mark the two questions that felt worst. They go into Day 6. Speaking is the part people skip, and it is the only part that changes how you perform; reading your notes feels like preparation because you recognise the material, but recognition is not recall under pressure.
Day 6: What does a full mock interview look like, and how do you review it?
Run 30 minutes end to end: the introduction, four questions from your bank, and your questions for them. Do it in one sitting, out loud, without stopping to fix anything. Treat the mock as the week's deliverable rather than an optional extra.
Then review each answer against three checks:
- Did it start with the point, or did it warm up first?
- Did the story have a result you could name?
- Did you answer the question that was asked, not a nearby one you preferred?
Pick the answer that failed the most checks and rewrite it. Say the new version immediately, while the old one is still in your ear. The before-and-after is the point of the day. If your answers tend to wander, the frameworks in communication interview questions give you a shape to fall back on.
Day 7: What should you do the day before, and what should you not do?
Light rehearsal only. One pass of your three stories and your introduction, then stop. Rest is part of the plan, and a tired voice and a full head help no one.
Check the logistics instead:
- Time, format and who you are meeting.
- How you will join the call or reach the building, tested once.
- The two or three questions you will ask them.
- What you will wear and what you need in front of you.
Skip the rest. No new topics, no rewriting the answer bank, no memorising full scripts. Last-minute additions push out the material you have already rehearsed.
What if you only have two days, not seven?
Compress to the three highest-value blocks and accept that the polish will be missing:
| Day | Focus | Output |
|---|---|---|
| 1 morning | Research sheet and three requirements | Five-line sheet |
| 1 afternoon | Three stories in four beats | Three stories, spoken once |
| 2 | One full spoken mock, reviewed | One rewritten answer |
If something has to go, drop the wording polish first. Never drop saying the answers out loud: a rough answer you have spoken is worth more than a polished one you have only read.
The three mistakes that waste a week of preparation
- Reading answers instead of speaking them. Recognition feels like preparation but is not. Fix: say every answer aloud at least once.
- Preparing topics instead of questions. The interviewer asks questions, not topics. Fix: write your bank as questions and answer those.
- Memorising scripts word for word. A single follow-up breaks the script and your confidence with it. Fix: bullets, not paragraphs.
Before you walk in
The week works because each day hands the next day something finished, and the mock is the product, not the afterthought. If you do only one thing from this plan, make it the spoken mock. Next step: open your calendar and block the seven slots now, starting with Day 1.
Frequently asked questions
How many hours a day does this one week interview preparation plan need?
About 45 to 60 minutes on most days, with Day 6 taking closer to an hour because it includes the mock and the review. The days are short on purpose: focused practice beats a long unfocused session, and the plan assumes you still have a job or other commitments during the week.
Should I prepare differently for a panel interview than a one-to-one?
Yes, in one respect. With a panel, expect each person to probe a different area, so make sure your three stories cover different ground rather than repeating one theme. Practise holding eye contact across the panel when you answer, and direct your question for them to a named person rather than the room.
What if the job description is vague and I can't tell what they will ask?
Work from the role title and the team's likely priorities instead. Ask what problem the hire is meant to solve, write three questions around that, and prepare your stories for the most common behavioural ground: pressure, disagreement and mistakes. Vague adverts usually mean the interview will lean on your past behaviour.
Is it worth preparing questions to ask the interviewer, and how many?
Yes, and two or three is enough. One should be about the work itself, one about how the team measures success, and one about what the first few months look like. Write them down and take them in; a written question reads as preparation, not as a test.
How do I prepare for a role I'm changing into without direct experience?
Build your stories from adjacent experience and name the transfer explicitly. If you have not done the exact job, show the closest real situation and say what carried over: a process you ran, a stakeholder you managed, a problem you solved. Honest bridging beats pretending, and interviewers usually probe for exactly that.