Your last-minute interview doesn’t have to be a disaster. Here’s what to research, what to practice and what to leave out when time is tight.
More...
In the grand scheme of things, what a great problem to have.
But still a problem, nevertheless.
A company has come back quickly and can't wait to see you. Fantastic news but you assumed there'd be more notice before you had to turn up and perform.
Then the panic arrives, because you're now counting hours, opening seventeen browser tabs, and trying to remember every achievement you've ever had while a small voice in your head doubts you're going to pull this off.
If you are facing this situation, here are 7 steps for a quick (but thorough) interview prep.
Key Takeaways
Jake rang me in a panic. He'd been applying for weeks and hearing nothing back, then a company called out of the blue. They'd just won an earthworks project at an airport, very similar to something he has been working on for the last 3 years.
He also knew what it probably meant.
His current project was coming to an end, so half his team had likely applied for the same job. This was his one chance, and he was terrified of blowing it.
The problem was that they told him at 3pm and it was taking place at 10 am the next morning.
We worked together on this for an hour and next day he was offered on the spot.
Did he deliver a perfect interview? No, not at all.
But did he do enough to convince them he was a perfect fit? Yes, absolutely.
This is what worked for him, and what can work for you too.
Now, of course, it would be lovely to have a fortnight to prepare but interviews don't work like that when you're the one being chased.
If you've got one evening, you've got one evening, but there's still plenty you can do with it.
Don't waste this golden opportunity.
Let’s dive in.
1. Address your fear head on
Your nervous about the interview because you are nervous about the clock. That is totally understandable because it puts extra pressure on you.
You’re just being human. But here's something to think about.
In a survey of professional orchestra musicians, 96% admitted to anxiety before their most outstanding performances.
Even superstars aren’t immune. British singer songwriter Adele has admitted she gets really scared before performing. Once she panicked and escaped out a fire door before a show and another time she projectile-vomited on a person in Brussels. This is someone who has sold over 120 million records.
So, that anxiety you are feeling right now might very well help you perform better on the day than you would without it.
Interviewers like people who show they want the job, and a little bit of nerves can signal this.
I’ve often had conversations with clients after they have interviewed one of my more confident candidates where they say, “it went well and I know they can do the job but I’m just not sure they’re that keen.”
AKA, potential flight risk. AKA, no job offer.
Remember, they have already given you a huge buying signal by wanting to meet you as soon as possible so take confidence in that.
See it as a meeting where you are both equally evaluating each other rather than as a performance you might get wrong.
But if this is a persistent problem, no matter how much time you have to prepare, here’s an article to help you.
2. Deal with the practical aspects
Before we get on to the specific prep, read what they sent. Confirm the time, the time zone, the location or the meeting link, who you're meeting, and whether you've been asked to prepare anything.
Check whether it's a recruiter screen, a hiring manager, or a technical assessment. These test different things.
For a video interview, open the link now, don’t wait until interview time. Check the camera, the microphone and your background.
For an in-person, check the route and the parking so you know exactly what time you need to leave to get there on time.
Anything that needs downloading, charging or finding, do it while you still have time.
3. Do your research
Having very little notice is no excuse for knowing nothing about the company at interview.
Neither is “sorry but I have applied to so many roles can you just go over the job description please?”
Every recruiter or hiring manager wants to feel like you want their particular role at their specific company and not just any old job anywhere.
The position description and/or job advert
Don't spend hours on this, and don't read it like a checklist. You'll get no points for memorising it. Unless you are changing career, the duties are likely to be exactly what you expect.
Find the three or four requirements that really matter, and look for the trait underneath each one rather than the duty or essential skills listed.
For example, "Liaising with clients and subcontractors" means communication, negotiation and competing priorities. "Working with minimal supervision" means judgement.
Then stop. You're joining a company, not a job, and the company is where the useful information lives.
The company
Jake's call didn't come from nowhere. They'd won work that suited his background, which is exactly the sort of thing you'll find on a company's website and socials while everyone else is still reading the ad.
This will put you above your competition.
Look for the problems they're likely hiring someone to solve. A company expanding into regional work needs someone who can handle distance and logistics. One that's just won a contract needs someone who can scale without dropping quality. One that keeps mentioning staff development might be one lacking experienced leaders.
That's the question you're really looking to answer with your research. What do they need this person to fix or develop? Where can I show I understand their business and highlight the value I can personally bring?
Try to find one specific thing that genuinely interests you and connect it to your own experience or direction. For example, "I see you've just won [name] airport project and I've spent six years on earthworks in live airside environments, so I know where these jobs go wrong" is worth more than a generic statement about being a civil engineer.
The interviewers
If you know who's interviewing you, spend five minutes on LinkedIn checking their professional background. An Operations Director and a technical specialist will approach the same interview very differently which will help you choose the right angles for your answers.
Then stop. Whilst it would be useful information, you don't have time for a full analysis of shared contacts or interests so avoid going down that rabbit hole.
4. Prepare your 'tell me about yourself' response
Be prepared for a few different ways this question can be asked including:
- Walk me through your career history to date
- Tell me about your career journey so far
- What would you say have been your career highlights
Whichever way they ask it, this what you need to understand.
Employers rarely hire the most qualified person in the room. They hire the one who feels like the least risky decision. Someone they can picture turning up on a Tuesday, talking to their team, and handling the work without being managed closely.
That's the reality of who you're actually up against. Not the best candidate on paper, but the one who makes them feel safe.
So, before you start thinking about how to handle any interview question, ask yourself a couple first.
- Who am I as a professional, in one plain sentence?
- And what do I offer that this business would find useful in the first six months?
If you can't answer those two, you have nothing to hang the rest of your preparation on, and it will show within the first two minutes.
The way to convey this to the interviewer is to perfect the “tell me about yourself” question.
When they ask it, they're not asking for your life story. They're asking why they should hire you.
They already know you're a good fit on paper. But the problem is that they also think that about everyone else they shortlisted, which is why they invited all of you in.
Here's what this question is actually doing.
It warms up the conversation, it gives them a look at the soft skills your resume can't show, and it tells them which parts of your experience you think matter.
That last one is the important one. The areas you choose to highlight will steer every follow-up question they ask.
Some people panic, lots say too little, and far too many say far too much.
Never brush this one aside though as a formality to get out of the way before the real questions start.
And don't answer it with "what do you want to know?", because that sounds hesitant at best and confrontational at worst.
The 5Ps method
Your answer should only be 60 - 90 seconds so you want to make sure every word earns its place. You can achieve this using the 5Ps method.
1. Prepare
Read the ad and the company page, and note the top three hard skills, the top three soft skills, and any specifics like budgets, team sizes, systems or projects. Make notes.
2. Pitch
Write one sentence that positions you professionally. Not your job title, not your history. "I've got a strong background delivering major infrastructure projects across TMR and RMS, but project management is where I've created the greatest value."
3. Present
Your current role, briefly, plus one or two achievements that match what they need. Not a job description. Think of it as you're already doing the kind of work they're hiring for.
4. Past
The earlier roles that explain how you got here, connected as dots rather than listed as dates.
5. Position
Why this role makes sense for both of you, using one specific thing you learned about them. Not flattery, but factual based on your research.
Here’s an example of what this looks like in practice.
"I'm ready for a bigger challenge and, after reading about your expansion into the fintech sector, I could immediately see how my experience working with three market leaders in this space would allow me to make an impact from day one.
I've followed your organisation for some time because of its reputation for delivering industry-leading programmes. The opportunity to apply my business development experience within an organisation that's setting the benchmark in the sector is genuinely exciting.
One of the reasons I applied is because I've always admired your commitment to diversity and inclusion. Having led similar initiatives throughout my HR career, I saw a real opportunity to contribute while continuing to work in an area I'm passionate about."
Say it out loud twice. Then cut anything that adds length without adding value, and practice ending on a full stop rather than trailing off into "yeah, so, that's me."
And if you're prone to blanking, take a notepad in with key words on it. Not the whole answer. Just the key words.
Don't waste time memorising it. It doesn't need to be word perfect. You just need to know what you are saying and why you are saying it.
If you have enough time, here’s my full guide on getting this right.
5. Build a story bank, not STAR answers
- Situation: Outline the background or situation where you faced a problem or were given a responsibility.
- Task: Clarify your specific role or objective in that situation.
- Action: Detail the steps you took to address the issue or fulfil your responsibility.
- Result: Describe what happened as a result of your actions, including any impact or lessons learned
It came from 1974, built by Dr William Byham and DDI so interviewers could score candidates against the same rubric. It was never designed to help you win the interview. It was designed to help them record it.
Here's the short version of what goes wrong.
It rewards memorisation by using set scripts that make you sound robotic in the interview.
Takes far too long because you have to construct so many scripts for each situation you may be asked about.
And commits you to a story before you've heard the question.The 3S method
Stance is your approach to a class of problem, in two or three sentences. Not a story. Where you stand. "I don't think of a disagreement as a problem to be won. Everyone arguing is usually looking at a different part of the same risk, so my starting point is that they've seen something I haven't."
Steps is how you work through it, in order. First this, then that, then that. That's what makes you sound like someone with a method rather than someone with a good anecdote.
Setting is the specific time it happened. By the time you get here, the argument is already won. The story is just the evidence.
The interviewer asked about conflict and heard safety, judgement, communication and influence inside one answer. And notice where the risk sits. If they don't warm to your example, they've still heard a philosophy they can agree with and a process they can trust.
That's your insurance. STAR gives you one shot. If you pick the wrong story, nothing is holding you up. Lead with how you think and you've scored before the example even begins.
Three stories, five angles, one evening
This is why a story bank suits a last-minute interview so well.
You don't need a pile of stories. You need two or three that are genuinely yours, plus the ability to walk into each one from a different direction depending on what's asked. For example, a delayed delivery you recovered might answer a question about pressure, planning, negotiation, a difficult stakeholder, or a mistake and what you changed. Same event. Five ways in.
Most candidates do this backwards. They build thirty prepared answers and then panic trying to find the right one under pressure. You want the opposite. fewer stories, understood deeply, so you can pivot on the spot.
And there's the confidence side too.
A story you understand properly means you never arrive at a question with nothing. You always have somewhere to go. That's worth more for your pre-interview nerves than any amount of deep breathing.
Where to find your three stories
The test for a story worth keeping is simple. It's a time that made you take stock for a minute. Something that shifted how you saw a situation, or changed your mind about a person, or forced you to rethink what you thought was right.
You can still feel it when you tell it, and underneath it there's a certainty that it was good work. Not that anyone praised you for it. That you know was good work.
If you've been in your field a while, you already know which ones they are. You probably thought of one just reading that.
Then for each one, ask yourself:
- What did I actually do that made the difference?
- What did I see that a less experienced version of me wouldn't have?
- What did I protect or refuse to compromise on?
- And where was the moment it could have gone the other way?
That last question is the useful one, because the turning point is usually where your stance lives.
Use AI to do the recall for you
The hardest part of quick interview prep is trying to remember what you've actually done, at speed, under pressure, years after the fact. That's a human weakness but a machine strength.
Don't ask AI to write your answers. Ask it to interview you. It has infinite patience and it will keep digging until you produce a specific moment rather than a vague summary.
Give it your resume and this prompt:
You're an experienced interviewer helping me prepare for a job interview. I've uploaded my resume. Interview me about my career, one question at a time. Don't write answers for me, and don't move on until my answer contains a specific situation, what I actually did, and a concrete result. If my answer is vague, push back and ask for the detail. If I say "we", ask what I personally did. Start by asking which role on my resume I want to start with.
Answer it honestly. Voice input helps if talking is quicker than typing.
Then:
Now pull out every story I've told you that shows genuine pride or a real change in my thinking. For each one, give me a one-line summary, the specific situation, what I personally did, the result, and the interview topics it could answer, such as conflict, leadership, influence, failure or working under pressure. Put it in a table.
Check what comes back yourself. If a story is a real one it holds up under follow-ups. If it's inflated, it comes apart the moment they dig.
And a result doesn't need a percentage attached. An approved design, a resolved complaint, a safer process or a client who stayed are all specific outcomes.
Then the question that saves you the most time:
Here is the job description and here is my story bank. For each core requirement, tell me which of my stories proves it and how strongly, and the angle to enter from. Then tell me which of my stories proves nothing this role needs.
Read it critically. The AI has no idea what your workplace was actually like. If a pairing makes you wince, delete it.
Where you find a genuine gap, don't fake it. Say the closest adjacent thing you've done and be honest about the boundary.
6. Prepare for the obvious questions your stories won't cover
A story bank handles those tricky behavioural questions you're likely to be asked. A handful of direct ones need their own short answers.
Why are you leaving? Brief, honest, focused on what you want next. Explain a mismatch or a redundancy without showing bitterness for your current employer.
Why this company/job? The specific thing you found in your research. Not "great culture" and "exciting time to join" but facts you gained from your earlier research.
What are your salary expectations? Know what you'd realistically accept, and say plainly whether you mean base or package including super. If the range hasn't come up, ask what's been budgeted. Here's an article specifically covering this.
What's your greatest weakness? Pick a real weakness that isn't critical to the job, spend about a tenth of your answer on the problem and the rest on what you've done about it. Skip the perfectionist routine and the "I care too much" version. I've written about the six mistakes to avoid here.
What's your greatest strength? This isn’t about your best quality in isolation. It's the strength that most directly helps you perform in the job you are interviewing for. If it doesn’t link to the role, it doesn’t matter how impressive it sounds. This article will help you find yours.
Of course there are many more than these that could come up, but these are the core questions for when you have little time to prepare.
7. Prepare questions you want to ask
Inevitably, towards the end of your interview they will ask whether you have any questions for them. If you say no that can be a weak ending to an otherwise strong interview.
Brainstorm a list of questions such as what is a typical day, what does success look like in this role, why its available, development opportunities, the direction the business is going in, key challenges for the first 6 months, or more information on the team.
Choose questions you want the answers too but also show that you understand their business from the research you did.
Write them in a bound notebook that you will also use to make notes in during the interview.
Say "yes, thank you, I have prepared a few." This proves your interest in the role.
If you look through them and they have all been answered tell them this. That's a great ending because you have in effect said they are good at their job for being so thorough.
Conclusion
Depending on how long you have, set specific time limits for each of these 7 steps so you don't get carried away on one section and then not be able to go through the whole process.
Then, when you're in the interview, listen to their questions and say to yourself "what are they likely wanting to probe here?"
You can pause. You can ask them to clarify. You can take a breath and choose which angle to enter from. Nobody is timing you to the second, and an unhurried answer sounds like someone who knows what they're talking about.
And if you blank, breathe. A few seconds of silence is fine. You built a structure, not a script, so it will come back to you faster than a memorised paragraph would.
You can't rebuild your career, memorise every question and audit a business in an evening, and you don't need to.
What you need is who you are, what you offer, the problem this company probably wants solved, and two or three real stories you can enter from different angles. That's enough to walk in looking like the safe pair of hands they're hoping for.
FAQ
What if the interview is too short notice for me to attend?
Say so promptly, make your interest clear and offer two alternative times. For example: “I’m very interested in the opportunity, but I can’t make this afternoon at such short notice. I’m available tomorrow before 10am or Thursday after 2pm. Would either work?” You don’t need to give a detailed explanation or apologise repeatedly for having existing commitments.
Can I take preparation notes into the interview?
Yes. A page of brief prompts, relevant achievements and questions can help you stay focused. Refer to it when needed, but keep listening and maintain the conversation. For an online interview, avoid reading prepared answers from another window.
Should I stay up late to prepare for an interview the next morning?
No. Set times for doing each step and stick to them. Spending another two hours collecting company facts is unlikely to help if you’re too tired to listen properly or explain your experience clearly.
Should I tell the interviewer I haven’t had much time to prepare?
You don’t need to open with an apology or announce that you’re underprepared. Use the time you have and concentrate on explaining your relevant experience. If they expected a presentation or task you couldn’t reasonably complete at short notice, clarify that beforehand and agree on what’s achievable.
What if I haven’t received a job description?
Ask the recruiter or hiring manager for one, along with a brief outline of the interview. If there isn’t a formal description, ask what the person needs to deliver and which experience matters most. Use that information to guide your preparation, then clarify the responsibilities during the interview.
