Lesson 8 of 8 · 50 min

Capstone: full behavioral mock + story bank

Story bank structure (8–12 cards), prompt-to-story mapping, card template, 45-minute mock protocol, TMAY, live grading rubric, blank recovery, integrity rules, and pass criteria before onsites.

Lesson 8 · Capstone

Full behavioral mock + story bank

Put the bank under timed pressure

You now have craft for rubric, STAR, ownership, conflict, failure, systems, and influence. The capstone installs a story bank structure and a full mock protocol so you can answer any common prompt by mapping to a prepared story in under ten seconds — then deliver with probe depth.

Done means: an 8–12 story bank mapped to prompt types, a 45-minute mock scored on the six dimensions, and rewrites for any story scoring ≤2 on a dimension. This is not resume work; it is interview operations.

Story bank structure

code

1STORY BANK (minimum viable)23  ID  Type            One-line stake                    Skills hit4  --  --------------  --------------------------------  --------------------5  O1  Ownership       unowned prod issue you drove6  O2  Project         proud project with cuts7  C1  Conflict win    disagreement → better plan8  C2  Conflict lose   overruled → clean commit9  F1  Incident        you contributed; prevention live10  F2  Non-incident    deadline/bet miss + planning change11  S1  System          designed/shipped subsystem12  S2  Debug/migrate   mystery or cutover13  L1  Prioritize      brutal no's with criteria14  L2  Mentor/influence person or cross-team adoption15  X1  Wildcard        customer obsession / integrity / ambiguity16  X2  Feedback        coachability with behavior change1718  Each card: 7 bullets max + 3 hard numbers + 3 probe answers.

Store the bank in a private doc. Rehearse retrieval: hear prompt → say story ID silently → open with stake. Never start speaking before the map is chosen.

Prompt → story mapping

code

1PROMPT CUES → DEFAULT STORY23  proud project / walk through project     → O2 or S14  beyond job description / ownership       → O15  disagreement / conflict / pushback       → C1 (have C2 ready)6  failure / mistake / incident             → F17  missed deadline / wrong bet              → F28  system design you built                  → S19  hardest bug                              → S210  prioritize / too much work               → L111  mentorship / help someone grow           → L2 mentor12  influence without authority              → L2 influence13  critical feedback                        → X214  ambiguous situation                      → O1 or S1 with ambiguity beat15  integrity / ethical                      → X1 (prepare honestly)

Story card template

code

1STORY CARD — O1 example fields23  Title:        Double-charge retry ownership4  Stake:        0.4% silent double-risk after gateway timeouts5  Role:         Backend payments IC; not on-call owner that week6  Actions:      repro → one-pager → TL review → flag ship → metric/page7  Result:       reports ~0; gateway change kept8  Residue:      idempotency checklist on money-path designs9  Tradeoff:     delayed non-money feature by 3 days10  Probe-role:   I owned worker+replay; TL API; PM customer comms11  Probe-diff:   would add chaos test for timeouts earlier12  Probe-disagree: PM wanted full freeze; I pushed surgical fix13  Numbers:      0.4%, 48h watch, 20-min review, ~0 reports

45-minute mock protocol

code

1MOCK PROTOCOL (solo with timer or partner)23  0:00–0:02   warm intro: 60–90s 'tell me about yourself' (role+domain+1 outcome)4  0:02–0:10   Q1 ownership / project5  0:10–0:18   Q2 conflict (include one probe: steelman / commit)6  0:18–0:26   Q3 failure / incident7  0:26–0:34   Q4 system story8  0:34–0:40   Q5 prioritization or influence9  0:40–0:45   self-score six dimensions; pick rewrite targets1011  Partner mode: partner only asks listed probes; no coaching mid-answer.

Score each answer 1–4 on Ownership, Agency, Conflict, Failure-learning, Judgment, Collaboration. Communication/time-control as a modifier. Any ≤2 requires rewrite within 48 hours.

Tell me about yourself (the opener)

Not a life story. 60–90 seconds: present role + domain, one shipped outcome with a number, what you want next tied to their work. No resume chronology from college unless you are new grad.

code

1TMAY TEMPLATE23  "I'm a [level] [role] focused on [domain]. Recently I [outcome + number] on [system].4   Before that [one prior beat]. I'm excited about [team problem] because [fit]."

Full mock answer keys (illustrative)

code

1Q: Ownership beyond JD → O1 payments retry (L3 worked story)2Q: Disagreement → C1 eng/PM launch split (L4)3Q: Overruled → C2 worker patch vs rewrite (L4)4Q: Failure → F1 flag default region outage (L5)5Q: System → S1 idempotency ledger (L6)6Q: Prioritize → L1 backlog criteria (L7)7Q: Mentor → L2 PR rollout bar (L7)89  In a real mock, use YOUR cards filled with real work only.

Live grading rubric (print this)

code

1DIMENSION        4 (Strong)                         2 (Lean)2---------------  ----------------------------------  ------------------------------3Ownership        End-to-end + residue                Tasks only4Agency           Acted under ambiguity + risk plan   Waited for perfect spec5Conflict         Steelman + rights + commit          Villain or no decision6Failure          Impact + prevention artifact        Blame or 'careful next time'7Judgment         Options + refuse + metrics          Buzzwords / no tradeoff8Collaboration    Named interfaces                    Lone hero or pure 'we'9Time             90–150s primary + probe depth       4min Situation / cut off

Week-of-onsite checklist

01Bank of 8–12 cards printed or offline-accessible.
02Two timed full mocks with scores written down.
03One conflict-lose and one real failure mandatory.
04TMAY recorded and under 90 seconds.
05Numbers memorized cold (not 'about a lot').
06Sleep and logistics — cognitive load is real.
07After each real interview, note which story misfired; rewrite that night.
08Never invent under pressure; map to closest true story or say a closer example.

Recovery when you blank

code

1BLANK RECOVERY23  1. Pause 2 seconds; restate the question.4  2. Pick type: ownership / conflict / failure / system / leverage.5  3. Open with stake sentence even if messy.6  4. If wrong story mid-way, pivot: "Better example for your question is…"7  5. Never fabricate numbers while panicking.

Pivoting to a better example is allowed once. Serial restarts look unprepared.

Integrity rules (non-negotiable)

True stories only. Accurate scope. Real numbers or honest qualitative deltas. If you cannot share confidential details, abstract the domain but keep the structure true. Lying is a hard fail when detected — and detection risk is non-zero.

The capstone is operational confidence: any common prompt → mapped card → 90-second spine → probe depth. That is what 'prepared' means for behavioral.

Final self-exam

code

1PASS CRITERIA BEFORE ONSITES23  [ ] 8+ cards filled with real work4  [ ] Types O/C/F/S/L covered5  [ ] One clean lose-conflict and one real failure6  [ ] Two mocks, no dimension ≤2 on primary stories7  [ ] TMAY ≤90s with one number8  [ ] Can explain six-dimension rubric cold9  [ ] Can compress any card to 60s PAR on demand

articleTIH — full behavioral question listTech Interview Handbook articleAmazon interviewing processAmazon Jobs articleExponent — behavioral mocks / questionsExponent articleHello Interview — behavioral practiceHello Interview

Checkpoint

You hear 'Tell me about a time you failed.' You have F1 (incident) and F2 (deadline). Which first?

AAlways F2 because incidents make you look badBPrefer F1 if impact+prevention are sharp; use F2 if they already heard an incident or ask about planningCInvent a third softer failure so you look humble but safe

Checkpoint

During a mock, your conflict story scores 2 on Conflict because it ends in 'we agreed to disagree.' Best fix?

AAdd more adjectives about how collaborative you areBRewrite the ending with decision owner, what shipped, your commit actions, and optional process residueCDelete all conflict stories because they are risky

Checkpoint

Best use of the last 5 minutes of a solo 45-minute mock?

AStart a new LeetCode problem to cool downBScore six dimensions per answer, mark ≤2, schedule rewrites within 48 hoursCRe-record every answer immediately in full before scoring

Checkpoint

You blank mid-answer and realize the story is a poor fit. Best recovery?

AFabricate a bridging detail so the poor fit seems perfectBPivot once: acknowledge and switch to a better mapped true story, then deliver cleanlyCStop the interview and ask to reschedule

Checkpoint

What is the minimum story bank shape before onsites?

AThree polished monologues you can recite for any questionB8–12 cards covering ownership, conflict win/lose, failure, system, prioritization, mentorship/influenceCOne story per job on your resume regardless of type

Could you run a 45-minute behavioral mock tomorrow with an 8–12 story bank and honest six-dimension scores?

New to itGetting thereConfident

Capstone locked

Bank 8–12 cards by type; 7 bullets + numbers + 3 probes each.
Map prompts to types in <10s; then open with stake.
45-minute mock protocol with six-dimension scoring.
TMAY 60–90s; blank recovery without fabrication.
Pass criteria: no primary dimension ≤2; real lose-conflict + real failure included.

Track complete. Rehearse the bank weekly until interviews; keep residue of real work fresh.

Sources

Free to read · better with Enzo

Learn it with Enzo

Save your progress, answer the checkpoints, and let Enzo quiz you on what you just read.

Continue with Enzo Sign up free