How to Find Your Stories

You do not need a unique answer for every possible behavioral question. That approach is inefficient, it does not scale, and it produces shallow, forgettable responses. Across every major tech company, behavioral questions cluster around the same themes.

That means ten well-chosen stories can cover the vast majority of questions you will face. The key is choosing the right ten and tagging them so you can flex each story into three to five different question types. That's how you'll get the 20% of data that comes up 80% of the time.

This lesson walks you through the full system: how to select your stories, how to excavate the ones with buried impact, how to tag them for flexibility, and how to adapt them for a specific company.

5 flagship projects

These are easy to choose, because they are the most objective. Ask yourself: "What are my 5 most impressive projects?"

The work you are proudest of. The ones with the widest appeal and the clearest impact. Think about the projects where you made real decisions, drove real outcomes, and can speak in detail about the tradeoffs you navigated.

Pick projects that span different types of challenges if you can. For example: a zero-to-one launch, a complex optimization, a turnaround of a struggling product, a data-driven pivot, a cross-functional initiative. Variety gives you range.

5 people/leadership stories

These cover the human side of the job. You need stories from specific categories because interviewers are looking for specific signals. Your five people/leadership stories should include:

1. Conflict with a stakeholder above you in the org.
2. Conflict with a peer or cross-functional partner.
3. A failure or mistake. Calibrate this to your target level. If you are interviewing Below Senior, this can be a learning moment where you missed something and grew from it. If you are targeting Senior+, this should be a high-stakes miss with real consequences. The bigger the failure, the more credible you are.
4. Mentorship or developing others. Especially important for Senior+ roles, where your ability to grow the people around you is a core evaluation criterion.
5. Receiving negative feedback and changing because of it. This tests self-awareness. The best answers show specific feedback, your honest reaction to it, and a concrete change in your behavior afterward.

Use your archive as a memory jogger

Your first instinct will be to brainstorm stories from memory. Do that. But do not stop there.

Your current one-page resume has been edited ruthlessly. Every time you updated it, you trimmed experiences, compressed bullets, and cut whole roles to fit the page. The stories you dropped are not gone. They are buried in older versions. Resumes from three or four jobs ago often contain strong material, because the projects were bigger or harder, and you just stopped including them.

Create a Google Drive folder. Add every version of your resume you have ever had. Beyond resumes, add anything that documents what you have actually done:

• LinkedIn profile (export it as a PDF from your LinkedIn settings)
• Promotion packets or promo writeups
• Performance review self-assessments
• Brag docs, impact summaries, or 360 feedback you have received
• Any strategy docs, product specs, or launch writeups that capture a decision you owned

Now go back through these documents with your ten-story framework in mind. Look for projects you forgot about, conflicts you glossed over, failures you buried.

Check your level

A story might be well-told, specific, and genuine. It can still signal the wrong level.

The bottom line: every level up in seniority corresponds to a wider circle of impact.

After you have picked your initial ten stories, audit each one against this scale. Ask yourself: "Does this story land at the right altitude for the role I am targeting?"

If any of your stories feel thin or underscoped, they either need excavation or they need a replacement story.

Excavate the buried details of your stories

This is the step that separates a good story bank from a great one. Some of your strongest stories are not fully formed in your head yet. You lived through them, but you have never had to articulate what actually happened at the level of detail an interviewer needs.

Open Claude, ChatGPT, or sit down with a friend or coach. Give them this prompt:

I want to dig deeper into this specific project. Here are my raw notes and memories:

[Paste everything you remember, messy is fine]

Ask me questions to help flesh out the full story. I am specifically looking for:

• What was the impact?
• What was the key decision on this project?
• What approach did I choose and why?
• What alternative did I end up not choosing?
• What tradeoffs did I consider?
• Who were my stakeholders, and who did I influence?
• What were the moments of tension in that collaboration?
• How did I drive alignment when there was genuine disagreement?
• Did any process, roadmap, or strategic changes come from this?
• What would I do differently now?

Let the AI or your partner interview you. Answer the questions in whatever order they come. The questions force you to articulate things you have internalized but never had to explain out loud.

This is especially helpful for stories where you suspect there is a higher-level impact than what is visible in how you have described them, and stories where you can't remember many details.

Tag your stories for modularity

This is where your ten stories become fifty answers. The tagging system is what turns a small story bank into comprehensive coverage.

Each story gets tagged with attributes that describe its underlying themes. When you hear a question in an interview, you are not searching for "the right story." You are matching tags.

These 15 tags were selected because they came up the most often in interviews for PM roles at top companies in the last 6-12 months:

1. Conflict or stakeholder tension
2. Data-driven decision
3. Heavy cross-functional collaboration
4. High complexity/technical depth
5. Trade-offs under constraint
6. Ambiguity/incomplete information
7. Influence without authority
8. 0-to-1/greenfield
9. Took ownership of something nobody assigned
10. Realizing you were wrong/failure
11. Customer obsession/user empathy
12. Multiple teams or orgs involved
13. Receiving or giving difficult feedback
14. Shipped under time pressure/cut scope
15. Mentorship/people development

Each story should carry three to five tags. Ten stories, times three to five tags each, give you thirty to fifty possible story-question matches. That is coverage.

When an interviewer asks, "Tell me about a time you had to influence without authority," you scan your tags for stories marked with cross-functional collaboration, stakeholder tension, or multiple teams. You pick the best match and adapt your telling.

Validate with AI

Once you have your ten stories selected and tagged, you can use AI to check for gaps. Upload your resume archive into a Claude Project or paste your story summaries into a chat and run this prompt:

Here are my 10 behavioral stories for PM interviews, with their tags:

[Paste your story list with tags]

I am targeting [level] at [type of company].

Do three things:

1. Flag any common behavioral question themes that my current bank does not cover well.
2. For each story, tell me whether the impact level matches my target or reads lower than it should.
3. Suggest any experiences from my archive that I might be overlooking.

This is AI as a second pair of eyes, not as the architect. You picked the stories. AI validates them.

Company-specific adaptation

Everything above builds your core story bank. These are your stories, independent of any particular company.

But when you are targeting a specific role, you need to filter and emphasize differently. This is a separate step, done after your core bank is solid.

For each company you interview with, create a separate Claude Project (or conversation). Paste the job description and run this prompt:

I am interviewing for [role title] at [company]. Here is the job description:

[Paste full JD]

Do two things:

1. Research [company] deeply. I want to understand their current strategy and priorities; recent product bets or organizational shifts; what this specific role signals about what they are optimizing for; and any culture signals (values, leadership principles, or known interview patterns) that should shape how I tell my stories.

2. Based on your research and the JD, write an "ideal candidate profile": a concrete description of the person they are trying to hire. What experiences would this person have? What behaviors would stand out? What impact level and scope would their stories demonstrate? Be specific enough that I can use this as a filter when choosing which of my experiences to highlight.

Now take that profile and hold it up against your ten stories. Which five or six stories best match what this company is looking for? Which tags should you emphasize in your telling? Are there any stories that need to shift emphasis to land differently for this audience?

Your assignment

Complete these steps to get your 20% of the stories that come up 80% of the time in interviews.

1. Brainstorm your ten stories from memory: five flagship projects, five people/leadership stories.
2. Go through your resume archive and look for stories you forgot or undervalued.
3. Audit each story against the level scale. Does it match your target?
4. Excavate any story that feels thin or underscoped. Let AI or a friend interview you about it.
5. Tag each story with three to five of the 15 tags.
6. Run the validation prompt to check for gaps.
7. When you have a specific company target, run the company research prompt and filter your bank.

By the end, you should have ten stories you know deeply, tagged for flexibility, and ready to be practiced. The next lesson teaches you how to practice them.