Skip to content
L5 Prep

Behavioral story bank

The behavioral round scores Leadership and Googleyness, and GCA leaks into it too. At L5 the bar is impact and influence beyond your own tasks.

Your stories

This mirrors the story bank table in 04-behavioral-story-bank.md, but the entries are saved in this browser rather than written back to the markdown. Write the full STAR text in the markdown file using the template below; keep the index here.

Themes covered by at least one story0 / 0

Ticks are saved in this browser only.

The behavioral round scores Leadership and Googleyness, and GCA leaks into it too. At L5 the bar is impact and influence beyond your own tasks.

Format

Use STAR, but weight it correctly. Most people spend 80% on Situation. Invert that:

  • Situation — 15%. Two sentences. Just enough context.
  • Task — 10%. What you specifically owned.
  • Action — 50%. First person, singular. “I decided…”, “I convinced…”, not “we”. Include the reasoning behind your choices — that’s where GCA is scored.
  • Result — 25%. Quantified. Latency, revenue, headcount, incidents, time saved. Then: what you learned or would do differently.

Hard limit: 2.5 minutes spoken. Time yourself. Anything longer gets cut off, and the interviewer stops writing notes.

Story bank (target: 10–12)

One story can cover 2–3 themes. Don’t write 12 separate stories — write 10 strong ones and map them.

# Story (1-line title) Themes covered Metric in the Result Rehearsed out loud
1 ☐
2 ☐
3 ☐
4 ☐
5 ☐
6 ☐
7 ☐
8 ☐
9 ☐
10 ☐

Themes you must be able to cover

Check each off once at least one story in the bank covers it.

Leadership / influence

  • Drove a project with no clear owner or ambiguous requirements
  • Influenced without authority — got another team or a skeptical senior to change direction
  • Made a technical decision under uncertainty with incomplete data
  • Mentored someone; what specifically changed for them
  • Pushed back on a bad plan from a manager or senior stakeholder
  • Led a cross-team or cross-org effort

Googleyness / collaboration

  • Conflict with a peer — how you resolved it and preserved the relationship
  • Handled a teammate who wasn’t delivering
  • Received hard feedback and what you actually changed
  • Prioritized ruthlessly / said no to a stakeholder, and how you framed it
  • Worked with an ambiguous or shifting requirement without stalling

Impact / ownership

  • Your most technically complex contribution (be ready to go 3 levels deep — they will drill)
  • A failure: something you shipped that broke, or a decision you got wrong
  • An incident/outage you handled, including the follow-through
  • Improved a process or the team’s velocity, not just code
  • Traded off scope vs. quality vs. deadline and defended the call

Story template

Copy this block per story.

### Title: ________________________________
Themes: ______________________________________
Company / timeframe: _________________________

SITUATION (2 sentences, no jargon)


TASK (what I owned — specific and singular)


ACTION (what I did, and WHY — 4–6 beats)
  1.
  2.
  3.
  4.
  Key decision + the alternative I rejected and why:

RESULT (quantified)
  Metric:
  Business/user impact:

REFLECTION
  What I'd do differently:
  What I learned that I've applied since:

LIKELY FOLLOW-UPS
  - Why not <obvious alternative>?
  - What did the person who disagreed with you say?
  - How did you know it worked?
  - What was the hardest part, technically?

Rules that separate an L5 answer from an L4 answer

  • Say “I”, not “we”. The interviewer must be able to isolate your contribution. Credit the team once, then own your part.
  • Every result has a number. If you can’t measure it, estimate it and say you’re estimating.
  • Show judgment, not just effort. What did you choose not to do, and why?
  • Always name the alternative you rejected. This is the single fastest way to signal seniority.
  • Show intellectual humility in at least two stories. Google specifically screens for people who can be wrong gracefully. A story where you changed your mind based on someone else’s argument is worth more than one where you were right all along.
  • Impact should extend beyond your immediate team in at least three stories.

Questions to ask your interviewers

Have 3 ready. Genuine, specific questions are a mild positive signal; generic ones are neutral; no questions is a mild negative.

  • What does the team’s on-call load actually look like week to week?
  • What’s the biggest technical debt item the team knows about but hasn’t fixed?
  • How do design decisions get made here — design docs, review forums, or informally?
  • What separates someone doing well at this level from someone doing exceptionally?
  • What’s changed about this team’s roadmap in the last 6 months?

Rehearsal protocol

  1. Write the story.
  2. Say it out loud, recorded, with a timer.
  3. Play it back. Cut every sentence that doesn’t add signal. Most first drafts lose 40%.
  4. Re-record. Target 2–2.5 min.
  5. Have someone ask you the follow-ups cold.
  6. Re-rehearse in Week 8 — familiarize, don’t memorize. Memorized answers sound memorized and lose the Googleyness read.