This is a preparation strategy, most associated with Amazon's Leadership Principles (LPs) but useful for any structured behavioral loop. "1–2 stories per LP" is the ideal; in practice you build a story matrix where strong stories cover multiple principles.

The story matrix

List the principles down one axis (for Amazon: Customer Obsession, Ownership, Invent and Simplify, Are Right A Lot, Bias for Action, Dive Deep, Deliver Results, etc.) and your real stories down the other. Mark which stories hit which principles.

                    Ownership  Bias-for-Action  Dive-Deep  Deliver-Results
Prod incident fix      ✓             ✓              ✓             ✓
Triage process         ✓             ✓                            ✓
Perf optimization                                  ✓             ✓
Mentored a junior      ✓
Migration to hooks     ✓                                          ✓

You don't need 12+ unique stories — you need ~10-15 strong ones where the best cover 3-4 principles each. Aim for full coverage with no LP left blank.

How to build each story

1. Write it out in full STAR — don't keep it only in your head.
2. Quantify the Result — %, time saved, users affected, bugs reduced.
3. Use "I" — interviewers score your actions.
4. Trim to ~90 seconds spoken; have a 30-second version too.
5. Practice out loud — the gap between "I know this story" and "I can tell it well" is large.

Don't forget the hard ones

• Failure stories — "a time you were wrong," "a time you missed a deadline," "feedback that was hard to hear." Every loop has these. A failure story must end in a genuine lesson and changed behavior.
• Conflict stories — peer, manager, cross-functional.
• "Disagree and commit" — strongly held opinion, overruled, committed anyway.

Why this works

Under interview pressure, recall collapses. A pre-built, practiced matrix means that whatever angle they ask from, you already have a mapped, rehearsed story — you're retrieving, not inventing.

What NOT to do

• Don't memorize word-for-word scripts — they sound robotic and fall apart under follow-up questions. Memorize the beats, speak naturally.
• Don't stretch one story to cover everything — interviewers compare notes; reusing the same story across an entire loop is a red flag.

Senior framing

The senior approach is treating behavioral prep like system design: map the requirement space (the principles), then build coverage. The depth of your follow-up answers ("dive deep" on the technical details of your own story) is what actually separates levels — so know your stories deeply enough to go three questions deep on any of them.