Home · Blog · Interview prep
How to prepare for an interview in one day
One day is enough to prepare well if you spend it on the things interviewers actually test. This plan fits into about five focused hours, in five blocks, and tells you what to leave out.

In short
- Spend the day in five blocks, about five hours in total, and stop in the evening.
- Start with the job description: list the 5 or 6 things it asks for, because that’s what the questions will test.
- Prepare five stories in STAR form and a one-minute introduction, then say them out loud.
- Research the company for 45 minutes, not three hours, and write three questions to ask.
- Do one full practice run out loud; it finds more problems than any amount of reading.
Practise this free: a mock interview for Behavioural round (STAR), scored, with a stronger answer. 3 a month, no card.
Start a mock interviewThe invitation came today and the interview is tomorrow. That’s less time than you’d like, but more than you think. Interviews mostly test what you’ve already done, and a day is enough to organise it so it comes out clearly.
What a day isn’t enough for is everything. So the plan below is about choosing: five blocks, about five hours, in the order that matters most. If you have a week, use the full interview preparation checklist instead.
Block 1: the job description (45 minutes)
Everything else depends on this, so do it first.
- Print or copy the job description and highlight every requirement and responsibility.
- Group them into 5 or 6 themes, for example “leading projects”, “working with customers”, “SQL and reporting”.
- Next to each theme, write one thing you’ve done that shows it. A project, a result, a situation.
- Mark the gaps: themes where you have nothing. You’ll decide how to talk about them in block 3.
This list is your map for the day. The interviewers will build their questions from the same document.
Block 2: your introduction (30 minutes)
The first question is almost always some version of “tell me about yourself”. Prepare a one-minute answer in three parts:
- Now: what you do and the area you work in.
- Proof: one or two things you’ve done that match the themes from block 1.
- Why this job: what draws you to this role at this company.
Write it, then say it out loud three times with a timer. Cut whatever pushes it past 90 seconds. Our guide to tell me about yourself has examples for different levels.
Block 3: five stories (90 minutes)
Most questions after the introduction ask for examples: a challenge, a conflict, a mistake, a success, a time you led. Five well-prepared stories cover most of them, because one story can answer several questions.
Pick five from your block 1 list and write each in the STAR format: the situation, your task, the actions you took and the result, with a number where you can.
| Story | Answers questions about |
|---|---|
| A project you led to a result | Leadership, ownership, success |
| A disagreement you resolved | Conflict, teamwork, communication |
| A mistake and what you changed | Failure, learning, honesty |
| A tight deadline | Pressure, prioritising |
| Something you improved | Initiative, problem solving |
For the gaps from block 1, prepare an honest answer: what you have that’s close, and how you’d learn the rest.
Interviewer: This role uses Tableau. Have you worked with it?
You: Not Tableau itself, but I built our team’s weekly reporting in Power BI: twelve dashboards used by about forty people. The ideas carry over, data models, filters, keeping it simple for the reader. I’ve started Tableau’s free training and I’d expect to be productive in it within a few weeks.
Say each story out loud once. Two minutes is the target; more than three and the interviewer will drift.
Block 4: the company and your questions (45 minutes)
Research has a point of diminishing returns, and it comes quickly. In 45 minutes, find:
- What the company does, in one sentence you could say to a friend.
- Something recent: a product launch, an expansion, a news story, from their own news page or LinkedIn.
- The team or product you’d join, if the job description says.
- The interviewers, if you have their names: their role and how long they’ve been there.
- How the company interviews, if it’s well known. Our company interview guides cover Google, Amazon, Microsoft, McKinsey, PwC, SAP, Spotify and others.
Then write three questions to ask at the end. Good ones ask about the work, not the perks: what success looks like in the first six months, what the team is working on now, what the biggest challenge is. Our guide on how to research a company before an interview goes deeper if you have more time.
Block 5: one practice run out loud (60 minutes)
This is the block people skip, and it’s the one that makes the most difference. Answers that sound fine in your head come out longer, vaguer and with more “um” when you say them.
- Ask someone to interview you, by video or in person, with five questions from your block 1 themes. If no one is free, record yourself on your phone.
- Answer exactly as you would tomorrow, including the introduction and your questions at the end.
- Play it back or ask for feedback, and fix the two biggest problems. Usually it’s answers that run long and stories without a result.
You can also run a mock interview for your role, which asks the questions, follows up on vague answers and scores each one.
A practice run tonight, free. Ghostpilot’s mock interviews ask questions for your role, follow up like a real interviewer and score every answer with what to improve and a stronger version built from your CV.
3 mock interviews a month are free, with no card needed.
Start freeWhat to skip
With one day, these don’t pay back the time:
- Memorising answers word for word. It sounds rehearsed and falls apart with a follow-up. Know the points, not the script.
- Reading every page of the company website. You need five facts, not fifty.
- Learning a new technical skill overnight. Review what you know; explain honestly what you don’t.
- Preparing for every possible question. Five good stories cover most of them.
The evening
Stop by early evening. Pack what you need, check the route or the video link, lay out your clothes and get a normal night’s sleep. Our guide on how to prepare for an interview the night before has the evening checklist, and how early to arrive for an interview covers the morning.
Career offices recommend the same order of work: understand the role, prepare examples, research, practise. MIT’s career advising resources are a good reference if you want more.
If your mind goes blank tomorrow despite all this, it happens to everyone; what to do when your mind goes blank in an interview explains how to recover in a few seconds.
Questions
Can you prepare for an interview in one day?
Yes. Most of what interviewers test is your experience, which you already have. A day is enough to match it to the job, prepare five stories, learn the essentials about the company and practise once out loud. What a day can't do is teach you new technical skills, so don't try.
What should I prioritise if I only have a few hours?
In order: the job description, your one-minute introduction, three to five stories with results, and two questions to ask. If there's time left, research the company and do a practice run out loud.
Should I stay up late preparing?
No. Stop in the early evening. A tired candidate answers worse than a slightly less prepared one, and late-night cramming makes answers sound memorised.
How do I prepare for technical questions in one day?
Review the fundamentals listed in the job description rather than learning new topics. Practise explaining two projects in depth, and solve two or three problems out loud, talking through your thinking as you would in the interview.
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.
Keep reading



