Anatomy

Letter	Meaning	Time budget	What to convey
S	Situation	20–30 s	Context, scale, stakes. One sentence on team/role/timeframe.
T	Task	15–20 s	YOUR specific responsibility. Not the team's. "I owned X."
A	Action	90–120 s	Concrete steps you took. Decisions, trade-offs, who you talked to. Use "I" not "we".
R	Result	20–30 s	Quantified outcome. Metric, business impact, lesson learned.

Common Traps

• "We" syndrome — interviewer can't tell what YOU did. Convert to "I drove the design", "I ran the load test".
• No metrics — "made it faster" → "p99 latency 800ms → 120ms, deflected 40% of timeouts".
• Hindsight bias — narrating decisions as if outcome was known. State the uncertainty you faced.
• Blame teammates — even if true, signals poor collaboration. Reframe as systems issue.
• Tech-only stories — for senior loops, behavioral signals matter more than code. Show influence, ambiguity, trade-offs.

Template

SITUATION (1 sentence)
  At [company], my team owned [system]. [Trigger event].

TASK (1 sentence)
  I was responsible for [specific outcome]. Constraint: [time / scope / dependency].

ACTION (3-5 beats)
  1. Investigated by [method] — found [insight].
  2. Considered options A/B/C. Chose A because [trade-off].
  3. Implemented [change]. Coordinated with [stakeholder].
  4. Validated via [test/metric].

RESULT (2 sentences)
  [Quantified impact]. [Lesson / what I'd do differently].

The 16 Principles

LP	Signal interviewer wants	Story angle
Customer Obsession	Started from customer pain, not internal request	Found user issue → drove fix despite roadmap
Ownership	Took responsibility beyond your scope	Fixed cross-team bug nobody owned
Invent and Simplify	Reduced complexity, not added it	Replaced 3 services with 1; killed dead code
Are Right, A Lot	Sound judgment under uncertainty	Disagreed with majority, data backed you
Learn and Be Curious	Picked up new domain quickly	Onboarded into ML/infra in 2 weeks
Hire and Develop	Mentored, raised someone's bar	Coached intern → full-time, 1:1s with junior
Insist on Highest Standards	Refused to ship subpar quality	Pushed back on launch over reliability gap
Think Big	Long-term, broad scope	Proposed platform vs. one-off fix
Bias for Action	Moved fast under uncertainty; reversible decisions	Shipped MVP in 1 week to validate
Frugality	Did more with less; cost-aware	Cut infra spend 40% with caching
Earn Trust	Vulnerability, listening, candor	Admitted mistake; received & acted on feedback
Dive Deep	Ground-truth investigation, not delegated	Read packets / DB logs to find root cause
Have Backbone; Disagree and Commit	Pushed back, then aligned once decided	Raised concern in design review; executed losing position
Deliver Results	Hit goal despite blockers	Shipped on date with scope cut, not slip
Strive to be Earth's Best Employer	Inclusion, growth of others	Created onboarding doc, mentored across teams
Success and Scale Bring Broad Responsibility	Considered downstream effects	Privacy/safety/cost review before launch

Bar Raiser

Independent senior interviewer, NOT on the hiring team. Veto power. Looks for "raise the bar" — would this hire be in top 50% of current employees at this level? Trained to detect rehearsed answers.

Four Rubrics

• General Cognitive Ability (GCA) — problem decomposition, analytical reasoning. Often via open-ended scenario: "How would you approach X?"
• Role-Related Knowledge (RRK) — coding + system design + domain.
• Googleyness — comfort with ambiguity, bias for action, collaborative, intellectual humility.
• Leadership — emergent leadership without authority, navigating ambiguity, ownership.

Stock Questions

• Tell me about a time you had to work without clear direction.
• Describe a project where you had to influence without authority.
• What's a time you changed your mind based on new information?
• How do you handle disagreement with a senior engineer?
• Tell me about a time you failed.

Meta

• Drive — pushed past obstacles, raised the bar.
• Direction — set vision, made decisions under uncertainty.
• Influence — moved teams without authority.
• Move Fast — shipped quickly, accepted reversible risk.
• Conflict — direct disagreement story is REQUIRED. Refusing to give one = auto-fail.

Microsoft

• Growth mindset — "learn it all" not "know it all". Story of changing your mind.
• Customer obsession + collaboration.
• "As Appropriate" depth screen — less aggressive than Amazon Bar Raiser.

Netflix

• "Stunning colleagues" — high autonomy + high accountability.
• Keeper test: would I fight to keep this person? Story of independent judgment.
• Context not control — show alignment via context, not approvals.

Apple

• Craft & quality obsession — story of polish past "good enough".
• Functional silos — work cross-functionally, but defer to design/PM in their domain.
• Secrecy mindset — comfort with limited visibility.

The 12 Stories

1. Major technical project you led — covers ownership, deliver results, think big, drive.
2. Project that failed / shipped late — failure, learning, recovery.
3. Disagreement with peer or manager — backbone, conflict, earn trust.
4. Ambiguous problem you scoped — direction, GCA, ownership.
5. Tight deadline / scope cut — bias for action, deliver results, frugality.
6. Mentoring / hiring — hire and develop, leadership, Googleyness.
7. Tech debt / refactor — invent and simplify, highest standards.
8. Cross-team influence — influence, earn trust, direction.
9. Production incident / debug — dive deep, ownership, customer obsession.
10. Cost / efficiency win — frugality, invent and simplify.
11. Customer issue you championed — customer obsession, ownership.
12. Time you changed your mind — earn trust, learn and be curious, growth mindset.

Reframing

Same story, different lead-in based on question:

Question	Lead with
"Tell me about ownership"	"I noticed an issue nobody owned..."
"Tell me about a tough decision"	"I had to choose between two approaches..."
"Tell me about influence"	"I needed buy-in from a team I didn't own..."

"Tell me about a failure"

• Pick a real failure with material impact (not "I shipped a typo").
• Own it — no blaming external factors.
• 3 parts: what failed, why (root cause), what you changed in your behavior.
• Avoid: failure that's actually a flex ("I worked too hard").

"Disagreement with manager"

• Show backbone — you DID push back.
• Show data — your case had merit (numbers, evidence).
• Show commitment — once decision was final, you executed wholeheartedly.
• Outcome can go either way: you were right, or they were right and you learned.

"Time you handled ambiguity"

Structure: undefined problem → defined the problem yourself → broke into milestones → executed → adjusted as info arrived. Emphasize the act of defining not executing.

"Tight deadline"

• Show triage: what stays in scope, what cuts, what defers.
• Show stakeholder communication: did you renegotiate or just absorb?
• Show quality bar: cutting scope ≠ cutting tests.

"Biggest mistake"

Different from failure — mistake is a specific decision you'd reverse. Prefer technical: chose wrong DB, over-engineered abstraction, premature scaling. Show present-day judgment: "Today I'd ___".

"Feedback that changed you"

Receive criticism + integrate it = earn trust + growth. Pick something specific (communication, scope, depth). Avoid trivial (typo, formatting). Show before/after behavior delta.

Questions you should ask back

• "What does success look like for someone in this role at 6 / 12 months?"
• "How does the team handle disagreement on technical direction?"
• "What's the biggest challenge the team is facing right now?"
• "How is engineering quality measured here?"

Level Expectations

Level	Behavioral weight	Required signals
L3 / E3 / SDE-1	~10%	Coachable, curious, basic ownership
L4 / E4 / SDE-2	~20%	Independent execution, team collaboration
L5 / E5 / SDE-3 (Senior)	~30%	Cross-team influence, mentorship, project ownership
L6 / E6 / Staff	~40%	Org-level impact, ambiguity, scope-setting, hire and develop
L7+ / Principal	~50%	Multi-quarter strategy, exec influence, talent magnet

Loop Rounds

• Recruiter screen — motivation, comp, timeline. Don't over-share comp; deflect to "competitive process".
• Hiring manager — fit, stories about the team's work area. Research their team.
• Peer behavioral — collaboration, conflict, team dynamics.
• Bar raiser / cross-functional — leadership, judgment. Hardest round.
• Skip-level / director — strategy, business sense, long-term thinking.

Auto-Fail Triggers

• Speaking poorly about ex-employer / coworkers — interviewer assumes you'll do the same to them.
• No specifics — "I led many projects" with no examples.
• Refusing to discuss failure or weakness.
• Defensive on follow-ups — interviewer challenges, you double down rather than reflect.
• Mismatch between resume claim and story detail.
• Inability to articulate what you'd do differently.

Language Hygiene

Avoid	Replace with
"We did X"	"I drove X. The team executed Y."
"It was a mess"	"The system had [specific issue]"
"My manager was bad"	"My manager and I had different views on priorities"
"Obviously..."	"In hindsight..." (don't make interviewer feel dumb)
"I always..." / "I never..."	"In this case..." (avoid absolutes)