Home · Blog · Interview prep
Interview preparation checklist, from one week out to the last hour
Most interview mistakes aren't about skill. They're a forgotten name, a dead laptop battery, a question you knew was coming and never said out loud. A checklist takes care of those, so your attention can go to the conversation.

In short
- A week out, read the job post line by line and match each requirement to one example from your work.
- Two or three days out, say your answers out loud; reading them in your head is not practice.
- The day before, check the time, the place or the link, and the names of everyone you’ll meet.
- In the last hour, stop preparing content. Check the setup, then calm your breathing.
Practise this free: a mock interview for Behavioural round (STAR), scored, with a stronger answer. 3 a month, no card.
Start a mock interviewA good interview looks relaxed, but that’s because the preparation happened earlier. This checklist is organised by when to do each thing, so nothing is left for the morning of the interview. Copy it into your notes, tick things off, and skip whatever doesn’t apply to your role.
For the reasoning behind each step, our longer guide on how to prepare for an interview goes deeper. This page is the list.
One week before
The week before is for understanding the role and collecting your material.
- Read the job post line by line. Highlight every requirement and every verb (“own”, “lead”, “build”, “support”). Those are the things they’ll ask about.
- Match each requirement to an example. For every highlighted line, write one sentence about a time you did it. Gaps are fine; knowing them in advance is the point.
- Research the company. What it sells, who buys it, how it makes money, and one recent piece of news. Our guide on how to research a company before an interview has a 30-minute method.
- Look up your interviewers if you have their names: their role, how long they’ve been there, anything they’ve written or presented.
- Confirm the format. Phone, video or in person? How long? One interviewer or a panel? Is there a test or presentation? It is normal to ask the recruiter.
- Reread your own CV. They will ask about anything on it, including the line you added three years ago.
| Format | Extra preparation |
|---|---|
| Phone screen | 60-second introduction, salary range, notice period. See our phone screen tips. |
| Video call | Camera, light, sound and a test call. See our Zoom interview guide. |
| In person | Route, travel time, where to go when you arrive, what to wear. |
| Technical | The language, tools and problem types named in the post; practise under time pressure. |
| Panel | Who does what on the panel, and an answer that speaks to each of them. |
Three to five days before
This is when preparation turns into practice.
- Write five or six stories in the STAR format: situation, task, action, result. Pick ones with a clear result, ideally with a number. One good story can answer several questions: a difficult project can be about conflict, deadlines or leadership depending on how you tell it.
- Prepare the questions that come up almost every time:
- Look at questions for your role. Our interview questions by role pages list the ones specific to engineers, analysts, managers, nurses, teachers and more.
- Say every answer out loud. Twice. Time the introduction; it should be about a minute.
- Prepare three questions to ask them. Our page on questions to ask at the end has ones that interviewers remember.
- Research the salary range for the role, level and city, in case it comes up. See salary expectation questions.
Here’s what one prepared story looks like once it’s tightened. Notice it fits in about 45 seconds.
Question: Tell me about a time you had to deliver under a tight deadline.
Answer: Last spring our biggest client moved their launch forward by two weeks, and our part of the integration wasn’t finished. I was the lead on it, so I split the remaining work into what was needed for launch and what could follow a week later, and got the client to agree to that. I paired with a colleague on the riskiest piece and we ran daily ten-minute check-ins with their team. We shipped the launch scope two days early, and the rest went out the following week without issues. Since then I always agree a “must-have for launch” list at the start of a project.
The day before
The day before is for logistics, not new material.
- Check the time and time zone in the invite. Put it in your calendar with two reminders.
- Check the place or the link. For an office: the address, the floor, who to ask for. For video: open the link, check you have the right app, and test your camera and microphone in it.
- Write down the names of everyone you’ll meet, and how to pronounce them if you’re unsure.
- Prepare what to bring: printed CV copies, a notebook and pen, ID if the building needs it, the job post with your notes.
- Choose your clothes and check they’re clean and fit.
- Run through your stories once, out loud, then stop. Cramming late adds stress and not much else.
- Sleep. It does more for your answers than another hour of practice.
On the day
- Eat something and drink water.
- Plan to be ready early: 10 to 15 minutes early for an office, 5 minutes for a video call with everything already open.
- Charge everything: phone, laptop, earphones.
- Silence notifications on every device in the room.
- Have water and your notes within reach.
The last hour
In the last hour, stop preparing content. It’s too late to learn new things, and trying makes you more anxious.
- Read your one-page notes once: your introduction, the five stories as headings, your three questions.
- Breathe slowly for two minutes. The NHS breathing exercise takes five minutes and works well before an interview.
- Have your first sentence ready. A simple hello, and a thank-you for their time.
- Know what you’ll do if you go blank. Our guide on what to do when your mind goes blank gives three sentences that buy you time.
Practise before the real thing. Ghostpilot’s mock interviews ask the questions for your role, listen to your spoken answer and score it, with notes on what to tighten.
Free to start: 3 mock interviews and 2 live calls a month, no card needed.
Start freeAfter the interview
The interview isn’t quite over when the call ends.
- Write down the questions they asked while you remember them. They’re useful for the next round and the next company.
- Note anything you’d answer differently and practise that answer once.
- Send a thank-you email within 24 hours. Our thank-you email templates cover the hiring manager, a panel and a recruiter.
- Put the date they gave you for an answer in your calendar, and follow up politely if it passes.
For more guides and worksheets, Harvard’s career services office publishes interview resources that apply well beyond students.
Questions
How many days before an interview should I start preparing?
About a week is comfortable for most roles: enough time to research, write examples and practise twice. If you only have a day, focus on the job post, three examples and your questions for them.
What should be on an interview preparation checklist?
Research on the company and role, five or six prepared examples, answers to the common questions said out loud, questions to ask, logistics (time, place or link, names), what to bring, and a plan for the follow-up email.
How many examples should I prepare for an interview?
Five or six well-practised stories cover most behavioural questions, because one story can answer several questions. Pick ones with a clear result, ideally with a number.
Should I practise interview answers out loud?
Yes. Answers you have only thought through tend to come out longer and vaguer than you expect. Saying them out loud two or three times, or doing a mock interview, is the fastest way to tighten them.
Get live help in your next interview
Ghostpilot hears each question and shows an answer from your CV, in a small window above your call. Free to start: 2 live interviews and 3 mock interviews a month, no card needed.



