A practical guide
You cannot become a different candidate overnight. You can read the role, choose a few true examples, and write a page you will actually use in the morning. The schedule below is a suggestion, not a rule.
A full preparation plan assumes several days: research, practice out loud, a mock with another person, a second pass after you have slept. You have found out about the interview late, or the search has piled two conversations into one week. The useful move is to protect a short list of tasks and to stop when they are done. An evening spent rewriting your life story, or revising an entire technical syllabus, usually produces a script you will not remember and a late night you will feel in the room.
Keep thisOne evening is enough to be specific. It is not enough to invent experience. Choose a few true examples, write them on one page, and stop.
CareerOneStop, a careers site sponsored by the US Department of Labor, tells candidates to research the employer, practise answers with real examples, prepare questions, and handle the practical details of the day. For the day itself it suggests arriving, or signing on to a video call, 10 to 15 minutes early. That is their guidance for the appointment, not a block to rehearse all evening. The National Careers Service, the government's careers advice service in England, suggests STAR examples kept short and conversational, so you do not sound as if you memorised a text. Both points fit one evening better than a long plan does.
01
It can make you fluent in the material you already have. That means the advert, the CV you sent, any form or statement, three scenes from your work, one honest line on a gap, and a few questions that could only be asked of this employer. It cannot create a project you did not do, a tool you have not used, or a calm that comes from having told the stories several times. If a story is thin, leave it off the page. A quiet truthful answer beats a vivid one you cannot sustain past the first follow-up.
Start by opening the application you actually sent. People prepare against a CV they wish they had submitted. The interviewer may have the other file. Check the title you used, the tools you named, and any gap you already disclosed. Do not prepare from memory of the CV.
If the interview is the result of a run of silence, or of several interviews that are not converting, the evening is still for this conversation. The wider diagnosis can wait. Finding where the search is stuck is a calmer job for a day when you are not about to be asked about a project.
02
Suggested, not a ruleThe blocks below are one way to spend a single weeknight, about two hours, then stop. Shorten them, swap them, or drop one if the interview is a technical screen or you have less time. Nothing here is a required duration.
Put the advert, the CV you sent, and any statement or form answers on the desk together. Mark the three requirements they repeat. Ignore the rest for tonight. If a requirement is a tool you did not claim, do not add it now. Note it as a gap you will answer honestly if they ask. The apply, clarify, or skip distinction still holds: a missing nice-to-have is a sentence, a missing core is something you should expect to be asked about.
One example per repeated requirement. Use a rough STAR shape: where you were, what you did, what changed. A few lines each, the length of something you can say. Pull scenes you have already told the truth about on the CV. If a bullet is only a duty, do not promote it tonight. Showing a change without a fake number is the standard. If you wrote a supporting statement, start from those paragraphs. They are the stories you already promised.
Read the page a candidate would read: what the product does, who it is for, a recent public note from the team if you can find one quickly. Stop when you can ask one question that would not fit a different company. You are not writing a briefing on the industry. If the interview is a coding screen, a SQL exercise, or a case, swap this block for a short practice of that kind of problem. Do not try to revise a whole syllabus. One problem, done slowly, is the useful version.
Three is enough. CareerOneStop suggests asking about the work itself: what a day looks like, how the work is judged, and what is hard in the role. Add the question that came from their product, and drop any question whose answer is on the advert. Leave pay for the moment they raise it, unless they have asked you to come prepared to discuss it.
The link or the route. The interviewer's name, if you have it. A copy of the CV. What you will wear, decided once. For a video call: the room, the light, the charger, and a trial of the link if the invite allows it. Write the details on the brief so you are not searching in the morning.
One pass, not a rehearsal until it is word-perfect. The National Careers Service warns against sounding rehearsed. If you stumble, note the first sentence you want to start with, and leave the rest loose. Then close the laptop. Sleep is part of preparation. A second hour of polishing usually removes the plain sentences and puts the adjectives back.
If you only have 45 minutes, keep three blocks and label them as a shorter suggestion, still not a rule: 15 minutes on the advert and your application, 20 minutes on two examples, 10 minutes on logistics and one question. Drop the company research before you drop the examples. If you have two interviews tomorrow, run the schedule once for the first, then only swap the employer, the three requirements, and the questions. Do not write twelve stories.
03
You will not know the exact wording. You can know the shape of four answers. Write the shape on the brief. Do not write a paragraph you intend to recite.
About a minute is a suggestion for the length, not a target to hit. Present role, the most relevant work before it, and why this conversation. Stop before your first job unless they ask. The point is to land on the requirement they care about, not to prove you have a biography.
One true reason tied to the work: the kind of system, the users, the problem. Flattery about the brand is easy to say and hard to follow up. If you applied because you need a job, you can still name what in this role you can do well. Those are different sentences. Use the second.
One honest sentence, then what you did or what you learned. Do not narrate the employer's failings. If you do not know a tool, say so and say how you would find out, or name the nearest tool you have used. Do not claim it in the room because the evening felt too late to be precise.
Say what you do know, say the edge of it, and say the next step you would take. Guessing a confident wrong answer is the failure mode of a tired evening. For a live exercise, talk through the approach you would use on a normal day, including where you would look something up. They are often listening for that, not for a memorised solution.
04
This page is illustrative. It is the length you are aiming at: one screen, or one sheet of paper. Yours should be duller and more specific. Specific is the point.
Notice the brief does not contain a model answer in full sentences. It contains reminders. If you need the full paragraph in front of you, you are about to read it aloud, which is the outcome the evening was supposed to avoid.
05
Reread the brief and nothing else. Eat. For a video call, open the link once, check the camera and the name on the screen, then wait. CareerOneStop's suggestion of 10 to 15 minutes early is a sensible buffer for a missed turning or a software update. It is not a reason to sit in the call for half an hour. Have the brief beside you, off camera if you can, as notes rather than as a script. For an in-person interview, paper is enough. Do not bring a laptop full of extra research you will not use.
If you are asked something you prepared, start with the first sentence you chose and then talk. If you are asked something you did not prepare, pause. A short pause reads as thought. Filling it with a story from the wrong job reads as evasion. You can say "the closer example is this one" and move to a scene you trust.
After the interview, write five lines: what they cared about, what you would answer differently, and whether you still want the role. That note is worth more than another hour of preparation tonight would have been. It is also how, later, you tell a pattern of interviews that do not convert from a single awkward question.
06
Copy this into a note, or print it and fill one page. If it spills onto a second page, you have written scripts. Cut back to reminders.
The file you sent, not the one you prefer.
07
Enough to be accurate and specific about work you have done. Not enough to fake a skill, and not a substitute for practice if you have several days. If you have longer, keep the same tasks and say the examples out loud more than once. The schedule is a suggestion for the short case, not the ideal length of all preparation.
No. Notes and one out-loud pass are the evening's work. Memorised paragraphs tend to answer the question you hoped for, and they crack when the interviewer asks "what did you do next?"
Swap the employer-research block for one practice problem of the kind they named. Still read the advert and your CV. Still prepare the gap you will not bluff. A technical screen is still a conversation about work you have and have not done.
One brief per interview. Reuse a story only if it is true for both roles. Change the three requirements and the questions. Do not try to hold both companies in your head without the page.
08
Sources checked 10 November 2026. The timings in this guide are a suggestion for one evening. They are not those organisations' schedules.