Why seniors fail the behavioral round
Senior engineers rarely fail a loop on the system design round. They fail on the round they prepared for in the taxi: "Tell me about a time you disagreed with your manager." The answer comes out vague, the story is about the team, and the interviewer writes "no clear ownership" in the notes.
At Amazon an onsite loop is usually four or five interviews, and each one probes two leadership principles. Interviewers compare notes in the debrief. A story you told in round two and again in round four gets noticed. Other big companies run the same pattern under different names: Google calls it "Googleyness and leadership", Meta has a separate behavioral round for E5 and up.
Prep guides disagree on how many stories you need: four, eight to ten, twelve to fifteen. My position: the number is wrong as a target. What matters is coverage. Below are the fifteen situations a senior loop keeps probing. Fill each slot from your own work, and five or six well-chosen stories can cover most of them.
STAR, briefly, and what seniors get wrong
Situation, Task, Action, Result. Everyone knows the letters. The failure is in the proportions. A typical mid-level answer spends 70 percent of the time on the situation. A senior answer spends one sentence there and the rest on decisions.
| Part | Share of a 3-minute answer | What it must contain |
|---|---|---|
| Situation | ~20 seconds | Team size, system, why it mattered, one number |
| Task | ~10 seconds | What was yours, specifically |
| Action | ~100 seconds | Two or three decisions, the option you rejected, who you had to convince |
| Result | ~50 seconds | A number, what broke anyway, what you would do differently |
The last item, "what you would do differently", is where seniors earn the level. A story with no regret sounds rehearsed.
The 15 story slots
Each row is a situation, not a question. Interviewers phrase them in many ways; the situation underneath stays the same.
| # | Slot | Typical phrasing | What a senior answer shows |
|---|---|---|---|
| 1 | Disagreed with a manager or lead | "Tell me about a time you pushed back" | Data before opinion, then commitment once decided |
| 2 | A decision that turned out wrong | "Your biggest mistake" | You noticed it first, and the fix you put in place |
| 3 | Production incident you owned | "A time something broke" | Calm sequence, communication, the follow-up that stopped a repeat |
| 4 | Influence without authority | "Convinced another team" | Their incentives, not your arguments |
| 5 | Cut scope to ship | "Tight deadline" | What you dropped and how you told the stakeholder |
| 6 | Raised the bar on quality | "Improved a process" | A measurable before and after |
| 7 | Mentored someone who struggled | "Developed a teammate" | Specific feedback, and how you knew it worked |
| 8 | Gave hard feedback to a peer | "Difficult conversation" | Private, specific, timely; what changed after |
| 9 | Ambiguous problem with no spec | "Unclear requirements" | How you turned it into two or three options |
| 10 | Customer or user pain you fixed | "Went beyond your role for a user" | You looked at real usage, not a ticket |
| 11 | Technical debt you paid down | "Long-term over short-term" | How you sold the time to the business |
| 12 | Said no to a senior stakeholder | "Refused a request" | An alternative offered together with the no |
| 13 | Learned something fast | "New technology under pressure" | The shortcut you took and what you skipped on purpose |
| 14 | Cross-team project you led | "Largest project" | Coordination cost, the dependency that nearly failed |
| 15 | Failure with no rescue | "A project that failed" | Honest result, what you would stop doing |
How to fill the slots from your own work
Do this on paper, once, for about two hours.
List your last three years by quarter
Twelve rows. For each, one project and one thing that went badly. Most people find their best stories in the "went badly" column.
Map rows to slots
One story usually fills two slots: the incident (3) is often also the quality story (6). Mark the primary and the backup slot.
Find one number per story
Latency, error rate, hours saved, people affected. If there is no number, find the closest honest one: "about 40 support tickets a week".
Write the "I" sentences
Three sentences that start with "I decided", "I proposed", "I told". If you cannot write them, the story belongs to someone else.
Say each story out loud, timed
Three minutes. Then answer two follow-ups: "what would you change?" and "what did your manager think?". A partner on a pair mock asks these better than a mirror.
Five mistakes that sink senior answers
- The hero story. Everyone else was wrong, you saved the project. Interviewers hear it in almost every loop and trust it less each time.
- The 2019 story. If your best example is six years old, the interviewer wonders what happened since. Keep most stories within the last three years.
- The team "we". Fine for context, fatal for actions. Count your "I"s after recording yourself once.
- No conflict at all. Senior roles are paid to handle disagreement. A career with none sounds like a career with no influence.
- Reading the principle back. "This shows my customer obsession." Let the interviewer map it; naming the principle sounds like a script.
A one-week plan
| Day | Task | Time |
|---|---|---|
| Mon | Quarter list and slot map | 2 h |
| Tue | Write six stories in STAR, one number each | 1.5 h |
| Wed | Record yourself, cut each to three minutes | 1 h |
| Thu | Pair mock: five stories, partner asks two follow-ups each | 45 min |
| Fri | Fill the two weakest slots, second mock with a different partner | 1.5 h |
The short version
Cover fifteen situations, not fifteen scripts. One sentence of context, most of the time on your decisions, a number at the end and one thing you would change. Do not tell the same story twice in one loop. Then say them out loud to someone who will interrupt.
Related: stop memorizing STAR, pick better stories, the last week before an interview, how structured interviews are scored.
Questions readers ask
-
Do I really need fifteen stories?
You need fifteen slots covered. Five or six strong stories can fill most of them if each has two angles. The point of the list is to find the gaps before the interviewer does.
Link to this answer -
Can I reuse a story in two rounds of the same loop?
Avoid it. Interviewers write notes and compare them in the debrief, so the same story twice reads as a thin career. Use a different one, even if it is weaker.
Link to this answer -
'I' or 'we'?
'We' for the context, 'I' for every decision and action. Senior loops are scored on what you personally did; a team success with no visible 'I' scores low.
Link to this answer -
How long should one answer be?
Two to three minutes before the first follow-up. The result and what you would change take the last third; most people spend it all on the situation.
Link to this answer -
How is this different from the STAR article on the blog?
That one argues for choosing stories over memorizing a script. This one is the checklist of fifteen slots a senior loop tends to cover, with an example for each.
Link to this answer
Sources
- Amazon: Leadership Principles
- IGotAnOffer: Amazon behavioral interview questions
- Coffee Is Not A Strategy: Amazon LP interview prep, the 4 stories you need
- Google re:Work: Use structured interviewing
Figures were checked against these pages in October 2026. Pay and dates change; the links show where to recheck.