How Much Should You Prepare for an Interview? A Time Budget

The number is the wrong thing to ask about. Most of what makes you good in an interview is prepared once and reused for every interview after it. Once you separate the one-time work from the per-interview work, the question stops being "how many hours" and becomes "which hours, and in what order."

Here is the budget I'd defend, what each block buys you, and the honest signal that you're done.

The budget: about five hours, split two ways

Split everything into reusable (do it once, use it for every interview this year) and per-interview (has to be redone for each company). Almost everyone gets this backwards and redoes the reusable part from scratch every time.

1. Six stories — 90 min — REUSABLE. Write six things you actually did, each with the situation, what you specifically decided, and how it came out with a number attached. Six covers most behavioural questions because interviewers ask the same six themes: conflict, failure, ownership, ambiguity, influence, and something you shipped. You write these once.
2. Your own resume, out loud — 30 min — REUSABLE. Read every line and answer "what would I say if they asked about this?" The lines you stumble on are the ones they will pick, because they are the vague ones.
3. The posting, closely — 45 min — per interview. Not skimmed. Write down the five things it is actually screening for and which of your six stories maps to each. Gaps you find here are what you prepare for; gaps you find in the room are what you lose to.
4. The company, specifically — 60 min — per interview. Not the About page. What did they ship in the last six months, what are they hiring for besides this role, and how do they write when they aren't marketing? Changelogs, engineering blogs, and job postings for other teams are worth more than the homepage.
5. Your questions for them — 30 min — half reusable. Three that show you read the posting, two that you actually want answered. The second kind matters more and is harder to fake.
6. One out-loud run — 30 min — per interview. Say your opening answer to a wall or a webcam. This is the step everyone skips and it is where the real errors show up.

The six stories, in more detail

This is the highest-leverage block, so it is worth being specific about what a finished one looks like. The failure mode is writing a summary instead of a story:

The second one is not longer because it is padded. It is longer because it contains a decision you made, a thing that went wrong, and numbers. Those three are what the interviewer is listening for, and none of them can be improvised convincingly.

It is the same standard that makes a resume line credible rather than decorative — the action verbs piece has the written version of this test.

If you have one day, not one week

This is the actual situation for most people, and "five to ten hours" is useless advice at 9pm the night before. Ninety minutes, in this order:

1. 30 min — three stories, not six. Ownership, failure, and something you shipped. Written down, with numbers.
2. 20 min — the posting. The five things it screens for, mapped to those three stories.
3. 20 min — the company. Their last two announcements and one specific observation you can say out loud.
4. 10 min — two questions you actually want answered.
5. 10 min — say your opening answer out loud once. Do not skip this one to buy more reading time; reading has sharply diminishing returns and speaking has almost none.

Ninety focused minutes beats six unfocused hours, and it comfortably beats the most common alternative, which is re-reading the company homepage until it is time to sleep badly.

The day of

• Do not learn anything new. Anything you add in the last two hours competes for recall with material you actually rehearsed.
• Re-read your six stories once, then close the document.
• Say your 60-second introduction out loud once. If you have not built one, that is the highest-value fifteen minutes available to you — see the 60-second self-introduction.
• Check logistics 90 minutes early, not 15. Link, room, name of the person, backup phone number.
• Have your resume open in a tab. They will reference it and you should be looking at the same document they are.

Where AI actually helps, and where it wastes your time

Useful for two things specifically: pulling the real requirements out of a posting, and being an opponent. It is close to useless as an answer generator, for the same reason it is a bad cover letter writer — it cannot supply your facts, and answers built from invented facts collapse on the first follow-up question.

• ✅ "Here's the posting. What are the five things this role is screening for, in priority order?"
• ✅ "Here's my story about the billing migration. Ask me the three hardest follow-up questions an interviewer would ask." — this is the best use, by a distance
• ✅ "Which of these six stories is weakest for this specific role, and what is missing from it?"
• ❌ "Write me an answer to 'tell me about yourself.'" — you will memorise something that isn't yours and it will sound like it

How to tell you're done

Preparation has sharply diminishing returns and no natural stopping point, which is why anxious people keep going all night and arrive worse than they were at hour three. Three signals that you have crossed the line:

1. You can tell all six stories out loud without notes, roughly two minutes each. Not word-perfect — word-perfect is worse.
2. You can name one specific thing about the company that is not on their homepage.
3. You are re-reading rather than producing. The moment your prep turns into rereading things you already wrote, you are done. Stop.

FAQ

Is five to ten hours per interview right?

For your first interview of a job search, roughly yes — but about two of those hours are one-time work. From the second interview on, two to three focused hours is realistic, and more than that is usually rereading rather than preparing.

How many interview questions should I prepare answers for?

None, in the sense of scripted answers. Six stories cover far more ground than twenty memorised answers, because interviewers ask the same handful of themes in endlessly different wordings. Prepare material that can be re-cut on the spot rather than answers that only fit the exact question you imagined.

What if I genuinely had no time to prepare?

Do the 90-minute version above, and if you have less than that, do the first item only: three stories with numbers, written down. Walking in with three real stories beats walking in having read the entire website.

Does preparing make me sound scripted?

Preparing the wording does. Preparing the material does the opposite — it frees you to listen to the actual question instead of scrambling for content while they are still talking. If you feel scripted, you rehearsed sentences when you should have rehearsed facts.