How to Prepare for a Behavioral Interview: Story Bank + Mock

Interviewing is a learnable test#

Like the SAT, interviewing rewards practice. The people who practice score well every time, and the people who wing it are surprised again and again.

It’s tempting to resent the format, since interviews are an artificial way to judge how someone will do a job. Mike Curti, a product leader who recently went through a search himself, lost a role he really wanted early on because he wasn’t yet practiced. He decided he couldn’t change the rules of the game, so he’d learn to play it. Things improved.

**Mike Curti**, product leader, formerly at Wayfair, fresh off his own job search

So err on the side of over-preparing. This is the one place in your search where spreading yourself thin is the wrong call. Give big interview loops the time they deserve. They rarely collide, so you can afford to.

How long to prepare for an interview#

A rough guide. Err high, and scale up for difficulty and for roles you care about most.

Stage	Prep time
Recruiter screen	2 to 3 hours
Hiring manager	5 to 7 hours
Final loop	10 to 15 hours
Big-tech loop	15 to 20+ hours

Start with the company#

Before you prepare yourself, find out what you’re preparing for: what they screen for, how the process runs, and what types of questions to expect.

Glassdoor and other review sites, for interview reports and question examples.
AI summaries of the company’s interview process, checked against the sources above.
Anyone in your network who works there or recently interviewed there. This is the best source by far, and another reason networking matters.
Job seeker communities on Slack, Discord and Reddit for your function.

Paid interview-prep packs and coaching sessions exist for specific companies. For a loop you really care about, they can be worth the money.

Build a behavioral interview story bank#

Your first story is your answer to “tell me about yourself,” and you already wrote it in step two. For the rest, go through the job description line by line. Every requirement should have a story from your experience behind it. Write each story down in a few bullets, using the answer structure below.

Most companies ask variations of the same behavioral questions: a time you led without authority, disagreed with your manager, failed, dealt with a difficult colleague, made a decision with incomplete data, changed your mind. Eight to ten strong stories can cover nearly all of them, because one good story can answer several questions.

AI promptBuild my story bank from a job description

Help me prepare a story bank for an interview.

Job description:
[PASTE]

My resume:
[PASTE]

1. List the 6–8 requirements or competencies this interview will most likely test, in priority order.
2. For each, suggest which experience from my resume is the best story to tell, and the backup. If nothing in my resume fits, say so plainly; that's a gap I need to prepare for.
3. List the 10 behavioral questions I'm most likely to be asked for this role, and map each to a story.
4. For my two weakest areas, tell me the gap question I should expect and how to answer it honestly.

Don't invent details about my experience. Where you need more, ask me.

Practice out loud with mock interviews#

Reading over your notes is not practice. Writing out answers isn’t really practice either. Gayle Laakmann McDowell, who wrote Cracking the PM Interview, says the biggest mistake candidates make is preparing alone, in writing. Interviews are interactive. Do mock interviews, even with a friend.

**Gayle Laakmann McDowell**, author of Cracking the PM Interview

Recording yourself helps too. Most people have no idea how long they talk until they hear it. A two-minute answer in your head is often eight minutes out loud.

You can practice for free with the voice mode in any AI chatbot, using the prompt below. If you want structured scoring and feedback on your delivery, Work Coach runs mock interviews too.

AI promptRun a mock interview with me

You're going to interview me for this role. Use voice mode if you can.

Role and company: [ROLE] at [COMPANY]
Job description: [PASTE]
Interview stage: [recruiter screen / hiring manager / final loop / specific round, e.g. product sense]
My resume: [PASTE]

Rules:
- Ask one question at a time and wait for my answer. Mix behavioral questions with questions specific to this role.
- Follow up the way a sharp interviewer would: ask for specifics, push on vague claims, and ask what I'd do differently.
- If I ramble past two minutes, interrupt me politely, the way a real interviewer would.
- After 5 questions, stop and give me feedback on each answer:
  - Did I lead with the result in the first sentence?
  - Was it specific, with numbers and my own actions (not "we")?
  - Did I include what I learned or would do differently?
  - Length, filler words, hedging.
  - The single biggest thing to fix.
- Then ask whether I want to redo my weakest answer.

Watch yourself back#

Practice only helps if you can see what to fix, and almost nobody has watched themselves interview. You’ll notice things in five minutes of playback that no amount of rehearsing in your head will show you: the answer that wandered for four minutes, the “we” where there should have been an “I,” the moment you lost the interviewer.

Record every mock interview. Most interviews happen on video calls now, so record on video. You’re checking what you said and how it came across on camera.

For real interviews, ask to record. People ask whether they can use a tool to record a real interview. You can, as long as you ask first. At the start, say:

How to ask to record an interview

“Do you mind if I record this, just for my personal use, so I can keep improving?”

Most interviewers say yes, and the question itself works in your favor: it’s a strong signal that you have a growth mindset. Never record without asking. Laws on recording conversations vary, and it’s a bad way to start a relationship anyway.

If they say no, that’s fine. Debrief instead: within fifteen minutes of hanging up, write down every question you were asked and what you said, as close to word for word as you can, and mark the answers you’d change.

When you watch or read it back, look for:

Length. Any answer over about two minutes, and where it started to drift.
The first sentence. Did it state the result, or start with background?
The question. Did you answer what they asked, or the question you’d prepared?
“We” versus “I.” Can they tell what you personally did?
Hedges and filler. “Kind of,” “I guess,” “just,” “sort of,” long pauses filled with “um.”
Their reactions. Where they leaned in, and where they redirected you. A redirect is a nudge (see curveballs).
How you look on camera. Eye line near the lens, decent light, energy at the start, and a smile when you say hello.

Keep a running list of patterns across interviews, and fix one at a time. It’s usually the same two or three habits every time.

You can do this yourself with the checklist above, or paste a transcript into any AI with the prompt below. A tool built for it saves the tedium: Work Coach reviews mock interviews and calls you have permission to record, and gives you an impartial read on how you came across.

AI promptReview my interview transcript

Here's a transcript (or my best reconstruction) of an interview for [ROLE] at [COMPANY]:
[PASTE]

Review it like a candid interview coach:
1. For each answer, tell me its approximate length, whether the first sentence stated the result, and whether I answered the question actually asked.
2. Flag every place I said "we" where the interviewer couldn't tell what I personally did.
3. List my filler words and hedges, with counts.
4. Point out moments where the interviewer seemed to redirect me or lose interest, and what they were probably looking for instead.
5. Name the two habits that hurt me most across the whole interview, and give me a specific drill for each before my next interview.

Be direct. Quote my own words back to me.

Answer with the result first (a better STAR method)#

Frameworks like STAR (situation, task, action, result) are fine, but plain STAR has two problems: it front-loads the boring context, and it hides your judgment. Fix both.

Hook. Open with one sentence that states the result. “I launched a product that reached 100,000 weekly active users in four months.”
Situation and task. Briefly. Only the context needed to understand why it was hard.
Action. What you did, specifically. Say “I,” not “we,” for the parts that were yours.
Result. The number, the outcome, what changed.
Reflection. What you learned, and what you do differently now.

The reflection is the part most people skip, and it’s where your judgment shows. Robert Hamilton, an interview coach and former Meta and Google PM, puts it in gym terms: the lesson is the gym membership, and changing how you work is actually going to the gym. Say what you do differently now.

**Robert Hamilton**, interview coach and former Meta and Google PM

Practice until each story sounds natural, not scripted. The substance of the story matters most. Delivery comes with reps.

Answer gap questions honestly#

“Have you managed people?” when you haven’t. “Have you worked in healthcare?” when you haven’t. Never lie or paper over it. Say it plainly, then tell a story that shows the same work without the title.

How to answer 'Have you managed people?' when you haven't

“I haven’t had direct reports. What I have done is lead a six-person project team across engineering, design and support for the billing migration. I ran the weekly planning, gave feedback to two junior PMs, and handled the conversation when one person wasn’t delivering. So I’ve done most of the work, without the title.”

Gap questions are predictable from the job description. Prepare them in advance.

Prepare for the stumpers#

Most “hard” interviews are preparable: case interviews, take-home assignments, technical screens, product sense, system design. These have known formats and a lot of free practice material. Practice them relentlessly, the way MBA students drill cases.

Handle curveballs#

Sometimes you’ll get a question you truly can’t prepare for. That’s a test of how you think when you’re nervous and out of your depth. Show that you ask good questions, reason through the problem out loud, and are coachable.

When the interviewer nudges you, take the nudge. Ben Erez, a former Facebook PM who now coaches candidates, says an interviewer who interrupts or redirects you usually isn’t being aggressive. They’re telling you you’re not giving them the signal they need yet, and giving you another chance.

**Ben Erez**, co-host of Supra Insider, former Facebook PM and interview coach

Take a breath. Think out loud. Silence is fine: “Give me a second to think about that” reads as composure, not weakness. The stress is the test.

How you come across#

You have to clear a bar of competence. But past that bar, being likable is the much easier lever, because people want to work with people they like.

Ethan Evans has interviewed more than 2,500 people as an Amazon VP. He says the top two factors in any interview are appearance and enthusiasm. If you seem judgmental of the company, like they have to sell you, you’ll turn them off. He goes into every interview wanting the offer, even when he’s already decided he doesn’t want the job.

**Ethan Evans**, retired Amazon VP who has interviewed more than 2,500 people

Concretely:

Smile, and use their name.
Be genuinely curious about their work.
Match their energy.
Never badmouth a former employer or colleague, even when asked about a conflict.

Questions to ask at the end of an interview#

Same principle as the recruiter screen: a couple of really good questions that leave them more excited about you, aimed at who specifically they want and what success looks like. A few that work at the end of an interview:

“What would make someone exceptional in this role in the first six months, beyond what’s in the job description?”
“What’s the biggest problem this team needs solved right now?”
“What do the strongest people on your team have in common?”
“How will you measure whether this hire worked out a year from now?”
“What’s something about the team or the work that surprises people when they join?”

Then end with: “Do you have any feedback for me on this interview?” It shows a growth mindset, and it flips the dynamic. How they handle an unexpected request for feedback tells you a lot about what working with them would be like. Some interviewers are told not to give feedback. Take what you get and don’t push.

Anneli Scopazzi suggests an even more direct version for the hiring manager: “What are your hesitations about me?” (You’ll also see it phrased as “Do you have any reservations about hiring me?”) It’s scary, but you’re still in the room and can address the concern before the debrief. She used it herself at Palantir and thinks it kept her in the process.

**Anneli Scopazzi**, founder of Boulevard Recruiting, formerly in recruiting leadership at Figma, Notion and Palantir

She adds a caveat: don’t ask every interviewer the same question, because they compare notes. Ask the hiring manager, and the recruiter.

After the interview: thank-you email and follow-up#

Send a thank-you email the same day. Short, specific, one line about something you discussed.
Update your tracker, and tell anyone who referred you how it went.
If you have to chase, chase lightly. You’re making sure you didn’t fall through the cracks, not trying to change the outcome. A company that doesn’t follow up at all is a red flag in itself. Sometimes it’s just the recruiter. Sometimes it’s a sign of broader dysfunction.

Thank-you email after an interview (short)

Subject: Thank you

Hi Maya, thanks for the conversation today. I keep thinking about your point that activation, not acquisition, is the constraint this year, which is the problem I most want to work on. I’m even more excited about the role than when we started. Best, Jordan

Follow-up email after an interview with no response

Hi Sam, I wanted to check in on the senior PM role. I really enjoyed meeting the team last week and I’m still very interested. Is there anything else you need from me, and is there an updated timeline? Thanks, Jordan

If you don’t get the job, it’s still worth one line asking for feedback. Many companies won’t give it, but the ones that do often tell you something useful.