How to Prepare for a Job Interview in 48 Hours

Two days is enough, if you spend it on the right things

Most interview preparation advice assumes a week and a clear calendar. In practice you get an email on Tuesday afternoon confirming a Thursday morning call, and you have a job, or a family, or three other applications in flight.

Forty-eight hours is enough. What it is not enough for is what most people do with it: reading about the company until the night before, then going in with a head full of facts and no idea what to say about themselves.

The preparation that actually changes an interview is about your own material, not theirs. Knowing the company well enough to ask two intelligent questions takes about an hour. Being able to tell six stories about your own experience without groping for detail takes longer, and it is what the whole thing turns on.

Day one, first hour: read the posting again, properly

You last read it carefully when you applied, possibly weeks ago. Read it again and write down, in your own words, the three things this role is actually responsible for. Not the ten bullets. The three that would make someone say the hire worked.

Then write one sentence next to each: what in your history is closest to it. Fifteen minutes, and it gives you the spine of the whole interview, because almost every question is a variation on "tell me about a time you did one of those three things."

If you cannot fill in one of the three, that is the gap you will be asked about. Better to find it now than at minute twenty.

Day one, second hour: six stories

This is the part worth the most and the part people skip, because it is uncomfortable in a way that reading about the company is not.

Pick six things you have actually done. They should cover: something you built or shipped, something that went wrong, a disagreement you handled, something you improved that nobody asked you to, something you did with incomplete information, and the piece of work you are most proud of. Between them, those six cover most of what you will be asked.

For each one, write four lines. What the situation was. What you specifically did, not what the team did. What happened as a result. What you would do differently now. That last line is the one that separates a rehearsed answer from a real one, and it is the one most people have not thought about, which is exactly why interviewers ask.

Write them out as actual sentences, not bullet points in your head. The point is not to memorise them, it is that having written a thing once makes it far easier to say out loud coherently. Get the numbers, names and timeline straight now so you are not reconstructing them under pressure.

Every story has to be something you actually did, described the way it happened. An interview is where an overstated resume bullet comes apart, because the follow-up question is always about detail, and detail is what invention does not survive.

Day one, third hour: the company, and only what matters

One hour, not five. You need enough to ask good questions and to not be surprised. You do not need their funding history unless it is relevant to the role.

• What the company actually sells, and to whom. If you cannot explain their business in two sentences, keep going until you can. This is the one thing you genuinely cannot afford to get wrong.
• Something that changed recently. A launch, a funding round, a market they entered, a change in direction. It gives you something current to ask about, which is worth more than anything from the about page.
• Who you are talking to. Look up their role and how long they have been there. A hiring manager who joined six months ago is in a different position from one who built the team, and it changes what is useful to ask them.
• The product itself, if you can reach it. Sign up, use it, look at the pricing page. First-hand experience beats an hour of reading about it, and it is where your best question usually comes from.

Day two: say it out loud, then stop

Take your six stories and say each one out loud, once, start to finish. Not from the page. You will immediately notice which two are a mess, and those are the two to run again.

This feels silly and it is the highest return thing you will do. A story you have only thought about comes out at twice the length and half the clarity the first time you say it. That first delivery should not happen in the interview.

Rehearse the opening too. "Tell me about yourself" is answered badly by most people, as a chronological walk through a resume. A better shape is three sentences: where you are now, the thread connecting what you have done, and why this role is next. Ninety seconds, not five minutes.

Questions to ask, and what makes one good

Have four ready, expect to ask two. A good question is one where the answer would genuinely change how you feel about the job, and where they cannot answer it from a script.

• What does the first success look like for whoever takes this role? It gets at what the job is actually for, which job descriptions usually bury.
• What do people find hardest to adjust to about working here? Easier to answer honestly than a question about challenges, and the answer is almost always informative.
• How did this role come about? A backfill, a new function and a role someone was promoted out of are three very different jobs.
• Something specific from your research, about a change they made or a product decision. This is the one that shows you did the hour of work, and it is the only one on this list that is specific to them.

Do not ask about salary, holiday or remote policy in a first conversation with a hiring manager unless they raise it. Those are real questions and the recruiter is the right person for them.

The logistics people forget

These are boring and they are the ones that actually go wrong.

• Check the time zone on the invite, twice. This goes wrong more than anything else on this list.
• Open the video link the day before, not two minutes before. Find out then whether it wants a browser extension or an account you do not have.
• Know where you will physically be, and that it is quiet, for the whole slot plus fifteen minutes either side.
• Have the job description, your six stories and your questions open in front of you. On a video call nobody can see your notes, and there is no prize for working from memory.
• Get the interviewer name spellings right. You will want them for the follow-up message afterwards.

What to do in the last hour

Nothing new. Reread your three role responsibilities and your six story headlines, not the full text. Do not add a seventh story, do not keep researching. Cramming makes people worse, because it replaces what you rehearsed with things you half know. Then close it all and do something else for twenty minutes.

Afterwards

Write down, within the hour, what you were asked and what you wish you had said. You will forget by the evening, and if there is a second round you now have a list of exactly what to fix. If there is not, you still have it for the next company, and the questions overlap more than you expect.

Then send the note, the same day, referencing something only someone in that conversation could. How to Follow Up After a Job Application: Timing and Templates has an example of what that looks like, and it is the one message in a whole search worth spending real time on.

Two days of preparation is a lot to spend, which is a good reason to be deliberate about which roles get it, in the same way How to Tell If a Job Is Worth Applying To: 5 Questions argues for being deliberate about which ones get a tailored application. The roles you interview for should be the ones you already decided you wanted.