Behavioral & HR
Behavioral, HR, and resume interviews
STAR stories, Leadership Principles, resume deep-dives, and mock prompts.
Behavioral rounds fail strong coders who cannot tell true, structured stories. Use STAR: Situation, Task, Action, Result — with metrics.
Story bank checklist
- Owned a production incident end-to-end
- Disagreed with a lead and changed the outcome
- Delivered under tight deadline with tradeoffs
- Mentored or multiplied a teammate
- Made a technical bet that failed — and what you learned
- Cross-team influence without authority
- Customer/user obsession example
- Simplified a complex system
Amazon Leadership Principles — sample mapping
| Principle | What to prove | Avoid |
|---|---|---|
| Customer Obsession | User impact metrics | Purely internal vanity metrics |
| Ownership | You drove beyond your ticket | “That was another team’s job” |
| Dive Deep | Data you personally inspected | Hand-wavy root cause |
| Bias for Action | Reversible decision speed | Reckless changes with no safety |
| Disagree and Commit | Real dissent then commit | Fake conflict |
Mock prompts (practice aloud)
Tell me about a time you disagreed with your manager
Expected shape
Concrete decision, your data, how you escalated respectfully, final outcome, what you’d repeat.
Common mistakes
- Trashing your manager
- No resolution
- No learning
Describe a production outage you handled
Expected shape
Detection → mitigation → root cause → prevention. Include timelines and customer impact.
Follow-ups
- What would you automate?
- How did you communicate?
- What monitors were missing?
Resume deep-dive: walk me through Project X on your resume
Interviewers probe anything you wrote. For each resume bullet prepare: problem, your role, architecture sketch, hardest bug, metric, tradeoff.
HR / recruiter screen: Why this company? Why leave?
- Be specific about product/tech — not ‘prestige only’
- No badmouthing employers
- Compensation: defer detailed numbers until later stages if possible; know your range