How to prepare for a job interview in 24 hours

Your interview is tomorrow, and you're probably about to prepare the wrong way: twenty open tabs, every page of the company website, and a late night writing perfect answers you never say out loud.

This article gives you an hour-by-hour plan for the day: research with a finish line, three flexible stories, and a short career narrative. It also covers the questions to ask and rehearsal you can actually hear. Work through it in order, protect a normal night of sleep, and stop when the checklist at the end is done.

The advice comes from Phyl Terry, whose book Never Search Alone has put thousands of candidates through job search councils; Lauren Ipsen, who recruits senior executives at Daversa Partners; and Matt Abrahams, who lectures on strategic communication at Stanford Graduate School of Business.

Plan how you'll spend the day

Work backward from the interview time. Company research will expand to fill whatever time you give it, so every block gets a time box and a finish line. The day should produce five things you can carry into the interview: a one-page role brief, a 60 to 90 second career narrative, three behavioral stories, a short list of questions for the interviewer, and a logistics plan.

Put the demanding blocks where your attention is strongest. Finish logistics before the last hour, stop at your normal bedtime, and review only the one-page brief on interview day. You'll get more from being rested with three usable stories than from one more hour of notes.

Turn the job description into a scorecard

Research should tell you what the company needs, where the role fits, and which parts of your experience matter. Keep facts that change an answer or create a question. Skip facts you'd only repeat to prove you visited the website.

Start with the job description

Copy the description into a working document and highlight five things:

• Outcomes: what this person is expected to improve, build, grow, fix, or own.
• Scope: team size, customers, geography, budget, systems, or functions involved.
• Repeated skills: words that show up several times usually signal the real evaluation criteria.
• Constraints: regulated environments, technical complexity, pace, travel, or cross-functional dependencies.
• Unknowns: phrases like "strategic initiatives" or "special projects" that deserve a clarifying question.

Then write one sentence that begins "They appear to need someone who can..." Treat it as a hypothesis you'll test in the interview.

Use a small set of company sources

Spend your hour on sources closest to the company and the work: the product, pricing, customers, careers, and leadership pages; recent product announcements, press releases, earnings materials, or founder updates; two or three customer reviews or community threads that show what users value; one competitor, so you understand the choice a customer is making; and the interviewer's public role history or writing. Keep a brief with three headings: facts, hypotheses, and questions.

One note like this improves several answers at once. It gives you a concrete reason for your interest, tells you which story to pick, and hands you a question that shows you did the work.

Build the four-column scorecard

Job descriptions mix outcomes, activities, credentials, and recruiting language. The scorecard forces you to decide what success probably looks like. Four columns:

1. Likely outcome: the change the company wants.
2. Evidence: one example showing you can contribute to that outcome.
3. Gap: an area where your experience is less direct.
4. Question: what you need to learn about scope, priority, or measurement.

For a customer success role, the outcomes might be improving onboarding, retaining larger accounts, building a repeatable renewal process, and bringing customer insight back to product. For an engineering manager: shipping a platform migration, improving reliability, developing managers, making planning more predictable.

Phyl Terry, author of Never Search Alone, teaches a stronger version of this exercise: draft your own version of the job description before you interview, framed as a job mission with OKRs.

Keep your first draft private. In the interview, ask "Which two outcomes matter most in the first six months?" and "How will you know this hire is succeeding?" The answers correct your scorecard, and a refined version can become an asset later in the process.

Build three stories that can answer a dozen questions

You can't predict every behavioral question in one evening, but you can prepare a small set of detailed stories that cover the traits most interviewers look for. Start with these three:

1. An unexpected obstacle. A moment when conditions changed, a plan broke, or a hard constraint appeared. Show how you assessed the situation and decided what to do.
2. A people or team issue. A conflict, a difficult feedback conversation, a missed handoff, or an alignment problem. Show how you understood the other person and moved the work forward.
3. A new opportunity. A customer need, process improvement, business opening, or risk you spotted before it was obvious. Show how you tested the insight.

Pick examples from the last few years when you can. Reach further back only when an older example is much closer to the role. Every story should contain actions you personally took and details a former colleague could confirm.

Build each story on one page

• Prompt cluster: the questions this story could answer, such as conflict, influence, failure, ambiguity, or leadership.
• Context: two sentences on the situation, your role, and the stakes.
• Goal: what you were responsible for accomplishing.
• Actions: three to five decisions or actions you took. Say "I" when it was you.
• Result: the measurable change, decision, learning, or follow-through.
• Reflection: what you learned and what you'd do differently now.

Prepare a 90-second version and a three-minute version of each. The short one gives the interviewer a complete answer. The long one is for when they ask how you made a decision, handled resistance, or measured the outcome.

For the full question bank and what hiring leaders at Stripe, Ramp, Webflow, and Meta say they listen for in the answers, including how they evaluate stories about ambiguity, use the behavioral interview questions guide. The short version for tonight: interviewers want to see how you made the decision, not just how it turned out. So say what you didn't know at the time, then explain what you checked first and why. For example: "We had three possible causes and only two weeks. I ranked them by customer impact and ease of testing, interviewed five affected customers, and ran the smallest test that could rule out the leading cause." One sentence like that shows the interviewer how you think.

Make your career story point at this job

A career narrative is a selective account of the choices that led to this interview. Keep older roles brief. Spend the time on decisions, strengths, and results that explain your fit for the work ahead. Use a four-part shape:

1. Present: your current role, scope, and the kind of problem you're good at solving.
2. Pivots: one or two moments that changed your direction or expanded your responsibility.
3. Pattern: the thread connecting your best work, like building early teams or simplifying technical products.
4. Next step: why this role and company fit what you want next.

Read it once, close the document, and tell it again from four bullets. Keep the facts and the sequence stable and let the sentences change. You want a familiar story you can tell while actually listening to the interviewer.

Lauren Ipsen recruits senior leaders at Daversa Partners and has watched candidates burn most of a job search learning to tell their own story. Her advice: don't let the interviews be the practice.

Say the full answer out loud. Listen for vague claims, missing impact, and an ending that never reaches this role. If the last sentence doesn't explain why this job fits what you want next, the answer isn't finished.

Map the questions you're likely to get

Make a one-page question map: likely question on the left, the story, evidence, or research note you'll use on the right. One strong example can answer several prompts when you shift the emphasis.

Motivation and fit

• Tell me about yourself.
• Why are you interested in this role?
• Why this company?
• Why are you considering leaving your current role?
• What's your greatest weakness?
• What are your salary expectations?

Connect your answers to actual work the role owns. Keep any explanation of a departure factual and brief, and speak respectfully about current and former employers. For a weakness, pick a real skill or behavior, describe where it matters, and explain what you're doing about it. For salary, research the role and location, ask for the approved range when appropriate, and don't invent a number under pressure. The salary negotiation scripts have exact wording for the recruiter screen and the offer conversation.

Behavioral evidence

The classic prompts ("tell me about a difficult problem", "a conflict", "a decision with incomplete information", "a failure", "a time you influenced without authority") should route to the three stories you already built. The behavioral questions guide covers the full list and what interviewers listen for. Whatever the prompt, prepare for the same three follow-ups: "What did you personally do?", "How did you measure the result?", and "What would you change?" Specific follow-up answers usually reveal more than the polished opening.

Role judgment

• What would you focus on in your first 30, 60, or 90 days?
• How would you approach the problem described in this role?
• Which metric would you use and why?
• How do you work with the functions this role depends on?
• What risk do you see in our current approach?

State your assumptions before answering any hypothetical. Use your scorecard to propose a direction, then name the information you'd need before committing to a plan.

Choose five questions that reveal the real job

Your questions should help you evaluate the work and understand how to succeed at it. Rank them, because many interviews leave time for only two or three, and drop any question the interviewer already answered.

End with a process question: "Is there anything else I can clarify, and what are the next steps?" It gives the interviewer a chance to surface a concern while you're still in the conversation.

Rehearse out loud, then stop rewriting

Reading your answers silently hides problems you'd catch the moment you said them out loud. Record a voice memo or video of five moments:

1. Your 60 to 90 second career narrative.
2. Your reason for wanting this role and company.
3. Each of your three behavioral stories.
4. A direct answer to one technical or role-specific question.
5. Your first two questions for the interviewer.

Listen once. Cut the long setup, replace vague verbs like "helped" with the action you took, and check every number. Then do a second pass without reading full sentences. If the point keeps getting buried, the clear-answer guide shows you how to shorten the opening, pick one example, and finish cleanly.

Use ADD for direct questions

Matt Abrahams teaches strategic communication at Stanford Graduate School of Business. For on-the-spot questions like "What's your experience with enterprise customers?", he recommends a structure he calls ADD: answer, detailed example, describe the relevance.

Here's all three parts in one answer, about thirty seconds out loud.

Use the longer story structure for behavioral questions. Use ADD when the interviewer asks for a position, a summary of experience, or a quick explanation. Lead with your answer, prove it once, connect it to the role, and let the interviewer ask for more detail when they want it.

Spend the flex block on the interview you'll actually face

Keep the research, scorecard, narrative, questions, logistics, and sleep no matter what. Then use up to two hours on the format you expect. Ask the recruiter what the round covers, how long it runs, which tools are allowed, and how it's evaluated.

Technical interview

• 30 minutes: review the stated format and the core concepts closest to the role. Use the job description to narrow the list.
• 60 minutes: solve one representative problem out loud. Clarify requirements, state assumptions, compare approaches, test the result, discuss tradeoffs.
• 30 minutes: check the coding environment, shared editor, whiteboard, or portfolio materials.

Interviewers need to hear your reasoning, so narrate enough for them to follow how you frame and test the problem. If you get stuck, summarize what you know, name the uncertainty, and propose the next check.

Case interview

• 30 minutes: review the case type and practice clarifying the objective, time horizon, constraints, and success measure.
• 60 minutes: run one full case with a timer. Organize the problem, request or interpret data, show your calculations, and update your view as evidence arrives.
• 30 minutes: practice a one-minute synthesis: recommendation, strongest evidence, key risk, next step.

A framework should organize the specific case in front of you. Say why each branch matters and revise the structure when the facts point somewhere else.

Presentation interview

• 30 minutes: confirm the audience, the decision, the time limit, and the requested format. Write the one sentence you want the panel to remember.
• 60 minutes: tighten the opening, evidence, recommendation, and close. Rehearse with the actual slides and leave room for questions.
• 30 minutes: export a PDF backup, check links and fonts, confirm screen sharing, and practice likely challenges to your recommendation.

Finish a few minutes under the limit, keep supporting detail ready for questions, and know which slide you can skip if the discussion runs long.

In the final hour, stop studying

Logistics deserve a written checklist because small problems use up attention you need for listening and thinking. Handle the setup before the last hour, then close the research tabs.

Eat something familiar, keep your normal caffeine routine, and protect sleep. You'll remember your examples and read the interviewer far better rested than tired.

The final-hour countdown

The last hour is for settling in and recalling what you built during the day. Reading anything new now just fills your head with stray facts right when you need to pull up your stories.

1. 60 to 45 minutes before: test the setup or route. Join the waiting page if possible, plug in the laptop, set out materials, or confirm the last leg of the trip.
2. 45 to 30 minutes before: skim the one-page brief. Role outcomes, three stories, narrative bullets, interviewer names, five questions. Don't reread full scripts.
3. 30 to 20 minutes before: take care of your body. Restroom, water, a small snack if you need one.
4. 20 to 10 minutes before: warm up. Stand, breathe slowly, say your opening answer once, and settle.
5. Final 10 minutes: stop preparing. Silence devices, close notes you won't use, and join five to seven minutes early.

Frequently asked questions

Is 24 hours enough time to prepare for an interview?

Twenty-four hours is enough to make a real difference for a first-round or behavioral interview. Use the day to identify the role's likely outcomes, prepare three adaptable stories, rehearse a short career narrative, choose questions, and check logistics. A substantial presentation, portfolio review, technical screen, or case exercise may need a narrower plan.

How many behavioral interview stories should I prepare?

Prepare three detailed stories: an unexpected obstacle, a difficult people or team situation, and an opportunity you identified. Pick examples that can also demonstrate leadership, judgment, collaboration, failure, learning, or influence.

How long should an interview answer be?

A direct question may need 30 to 60 seconds. Aim for a 60 to 90 second opening version of a behavioral story, then expand toward three minutes only when the interviewer asks for more detail.

Should I memorize interview answers?

Memorize the shape of each answer and the facts that must be accurate, and keep the wording flexible. Bullets for the opening, actions, result, and lesson make it easier to sound natural and answer the question you were actually asked.

What should I do if I don't know an interview answer?

Pause, clarify the question if needed, and state what you know. Then explain how you'd find the missing information or work through the decision. For a hypothetical, make your assumptions visible before describing your approach.

The 24-hour plan on one page