This guide is about applying for jobs in the UK.

The night before an interview tends to look the same for everyone: a browser with fifteen tabs open, a vague plan to "read about the company", and a quiet hope that the right words will arrive on the day. They usually do not, because last-minute reading is not the same as preparation, and reading is silent while the interview is spoken.

Knowing how to prepare for an interview is mostly knowing what to prepare, in what order, and then saying it out loud until it is steady. The good news is that the work is finite. Once you treat preparation as a short routine rather than an open-ended worry, the panic has nowhere to live. This guide walks through that routine, and it pairs naturally with our wider guide to interview questions and answers, which covers the questions themselves in depth.

Why a routine beats cramming

Cramming fails for a simple reason: an interview tests recall under mild pressure, and the night before is the worst time to build recall. Information read once at 23:00 is gone by the morning. A routine spread across two or three evenings does the opposite, because each pass over the same material makes it easier to retrieve when a question lands.

There is a second reason. Most interview preparation advice is really a list of inputs, the company, the role, your own experience, the questions you want answered, and lists are easy to half-finish and forget. Turning those inputs into a fixed sequence means you can see what is done and what is left. The four parts below are that sequence, and the order matters: research feeds your stories, your stories shape your questions, and the logistics protect all three.

The four-part preparation routine

This is the core of how to prepare for an interview. Work through the four parts in order across a couple of sessions, then spend your final session rehearsing rather than gathering more.

Research the company and the role. Read the job description twice, then the company's own site and recent news. You are looking for the few specifics you can refer to naturally, not a dossier.
Prepare three flexible stories. Pick three real situations from your experience that show you doing the job well. Three is enough to cover most behavioural questions if each one flexes.
Write the questions you will ask. Draft five questions for the interviewer. Arriving with none reads as low interest, and good questions are part of the assessment.
Sort the logistics. Confirm the time, place or video link, what to bring, and the route. This is the cheapest part to get right and the most embarrassing to get wrong.

Research the company and the role

Start with the job description, because it is the single most useful document you have. Read it twice. The first read tells you what the job is; the second tells you which two or three requirements the interviewer will press hardest, usually the ones repeated or listed first. Those are the requirements your stories need to cover.

Then spend twenty minutes on the company itself: the homepage, the about page, any recent announcement, and the team or careers page if there is one. You are not memorising facts to recite. You are collecting two or three genuine specifics you can weave in when you explain why this role and this employer, the same specifics that turn a generic "I want to work here" into a credible one.

A quick note on the job description as a tool beyond research: it is also what the strongest interview answers are built from, because most behavioural questions are invitations to expand on a requirement listed there. If your matching and applications are part of the same effort, our guide to using AI across your whole job search shows how the description threads through every stage.

Prepare your three stories

Most interview questions, and almost all behavioural ones, are answered well by a short story with a clear result. You do not need a story for every possible question. You need three flexible ones, each built so it can be reshaped to answer several different prompts.

Choose situations that show range: one where you delivered something difficult, one where you handled a problem with people, and one you would call a genuine setback. Between them they cover the questions about strengths, pressure, conflict, and failure that come up again and again. Build each story so it sets the scene in a sentence, states what you were responsible for, describes what you actually did, and ends on a concrete outcome.

One story, three questions

The raw story: "A client moved a launch forward by three weeks. I was coordinating the four people producing the assets. I cut the review rounds from three to one, moved check-ins to mornings, and we delivered two days early. The client renewed the next year."

Asked about pressure: lead with the squeezed timeline and the calm way you re-planned it.

Asked about leadership: lead with coordinating the four people and the decision to cut the review rounds.

Asked about a result you are proud of: lead with the early delivery and the renewal.

That is the value of flexible stories over scripted answers. A script collapses the moment a question arrives in a different shape, while a story you know well bends to fit. For the full set of questions these stories need to cover, the interview questions and answers guide lists the twelve that appear most often.

Write the questions you will ask

Interviewers leave time at the end for your questions, and turning up with none is one of the few avoidable mistakes left in the process. Prepared questions also do quiet work for you: they signal that you have thought about the role as a real job rather than a destination. Draft five so you still have two or three left after the conversation answers the rest. These work in almost any interview:

What would success look like in the first six months?
How does the team measure good work?
What is the biggest challenge facing the team right now?
What do you enjoy about working here?
What are the next steps and the timeline?

Ask two or three, listen to the answers, and follow up on one of them. The follow-up is what proves the question was real rather than recited.

Sort the logistics

This is the part candidates skip because it feels too obvious to plan, and then it is the part that goes wrong. Confirm the start time and time zone, the exact place or the video link, and who you are meeting. For an in-person interview, check the route and aim to arrive about ten minutes early, not earlier, because a long wait in reception only adds nerves.

Decide what to take the night before so the morning is calm: a printed copy of your CV and the job description, a notebook and pen, any document the employer asked for such as right-to-work evidence, and your list of questions. For a video interview, the equivalent is a tested camera, microphone and connection, a tidy background, and a quiet room. Open the meeting link a few minutes early so a software update does not eat your start time.

What rehearsing out loud actually fixes

Everything above is preparation on paper, and paper is where most candidates stop. The step that separates a steady interview from a shaky one is saying your answers out loud before the day, because spoken answers expose what silent reading hides: the filler words, the story that runs to four minutes when it should run to two, the strong opening that trails off without a result.

Rehearsing in your head feels productive and proves almost nothing, since you never hear the gaps. Saying an answer aloud, even once, reshapes it. Record yourself on your phone, or rehearse with a friend who will ask the questions in a slightly different order than you expect. The aim is not a polished performance. It is to have heard your own answers enough times that the real ones come out calm.

The limit of practising alone is that you tend to ask yourself easy questions and judge your answers gently. Practising against questions built for the specific role removes both problems. That is what AI interview coaching is for: it builds a mock interview from the actual job description and your CV, asks role-specific behavioural and company-fit questions, flags weak answers with suggestions, and tracks improvement across repeated sessions, so your hardest question gets steadier each time. It runs whenever you have time, including late the night before. One honest limitation: interview practice currently runs in English, though the way you structure an answer carries across other languages.

Before the day: nerves and the final hour

Nerves are not a sign you are underprepared, and a small amount of adrenaline sharpens you. The aim is to keep them at a useful level, and a finished routine does most of that work, because there is nothing concrete left to worry about. The rest is managed on the day rather than prepared in advance.

In the final hour, resist the urge to learn anything new. Re-read your three stories and your questions once, then stop. Arrive or log in a little early, breathe slowly before you begin, and treat the first question as a warm-up rather than a verdict. If your mind goes blank during the interview, pause, take a breath, and ask for the question to be repeated. A short silence reads as composure, and the brief pause buys you the sentence you need.

Frequently Asked Questions

The routine

How do you prepare for a job interview?

Work through four things in order: research the company and the role from the job description, prepare three flexible stories that prove you can do the work, write the questions you will ask them, and sort the logistics so nothing surprises you on the day. Then rehearse your answers out loud, because saying them is the part that actually sticks.

How long before an interview should I start preparing?

Two or three evenings is enough for most interviews, and cramming the night before rarely helps. Spread the work so the research and stories land a few days out, then use the final session purely to rehearse out loud. A short run-through on the morning itself settles the nerves more than fresh preparation does.

On the day

What should I take to an interview?

Take a printed copy of your CV and the job description, a notebook and pen, any document the employer asked for such as right-to-work evidence, and the questions you plan to ask. For a video interview, swap the paper for a tidy on-screen window and a tested camera, microphone and connection.

How do I calm interview nerves?

Nerves shrink when preparation is concrete, so the routine in this guide is itself the main fix. On the day, arrive early, breathe slowly before you go in, and remember that a short pause before answering reads as composure. If your mind goes blank, ask for the question to be repeated rather than filling the silence.

Practising

How can I practise for an interview at home?

Practise out loud against questions built for the specific role rather than a generic list, ideally recording yourself or rehearsing with someone. AI interview coaching generates a mock interview from the actual job description and your CV, gives feedback on each answer, and runs whenever you have time, including the night before.

Conclusion: prepare the routine, then trust it

Preparing for an interview is not a talent, it is a routine: research the role, build three flexible stories, write your questions, sort the logistics, and rehearse the lot out loud. Done across a couple of evenings, it turns the night-before panic into a calm run-through. When you are ready to hear your own answers before it counts, the interview questions and answers guide gives you the questions to rehearse against.

Want to rehearse before it counts?

TalentAid turns the job description into a mock interview built for the role you actually applied for.

Start free and practise out loud