Leadership Principles

Amazon's Leadership Principles

These 16 principles guide every decision at Amazon. They are the foundation of Amazon's culture and are used extensively in hiring.

---

1. Customer Obsession
"Leaders start with the customer and work backwards."

• What it means: Prioritize customer needs above all else
• Example question: "Tell me about a time you made a decision based on customer needs"
• Story tip: Show how you gathered customer feedback and acted on it

2. Ownership
"Leaders are owners. They think long term and don't sacrifice long-term value for short-term results."

• What it means: Take responsibility beyond your job description
• Example question: "Describe a situation where you took ownership of a problem outside your role"
• Story tip: Show initiative and follow-through on outcomes

3. Invent and Simplify
"Leaders expect and require innovation and invention from their teams and always find ways to simplify."

• What it means: Innovate while keeping things simple
• Example question: "How have you improved a process or system?"
• Story tip: Describe the problem, your creative solution, and the impact

4. Are Right, A Lot
"Leaders are right a lot. They have strong judgment and good instincts."

• What it means: Make good decisions with incomplete information
• Example question: "Tell me about a difficult decision you made with limited data"
• Story tip: Explain your reasoning process and how you validated your decision

5. Learn and Be Curious
"Leaders are never done learning and always seek to improve themselves."

• What it means: Continuously learn and explore new possibilities
• Example question: "How do you stay current with technology trends?"
• Story tip: Show your learning habits and how you've applied new knowledge

6. Hire and Develop the Best
"Leaders raise the performance bar with every hire and promotion."

• What it means: Build and develop high-performing teams
• Example question: "How have you mentored or developed someone?"
• Story tip: Describe how you identified potential and helped someone grow

7. Insist on the Highest Standards
"Leaders have relentlessly high standards that many may think are unreasonably high."

• What it means: Never settle for mediocrity
• Example question: "Give an example of when you refused to compromise on quality"
• Story tip: Show your standards and how you maintained them under pressure

8. Think Big
"Thinking small is a self-fulfilling prophecy. Leaders create and communicate a bold direction."

• What it means: Have a vision and inspire others
• Example question: "Tell me about a time you proposed an ambitious solution"
• Story tip: Describe your vision and how you got buy-in

9. Bias for Action
"Speed matters in business. Many decisions and actions are reversible and do not need extensive study."

• What it means: Act quickly when appropriate
• Example question: "Describe a time you had to make a quick decision"
• Story tip: Show you can balance speed with quality

10. Frugality
"Accomplish more with less. Constraints breed resourcefulness, self-sufficiency, and invention."

• What it means: Do more with less resources
• Example question: "Give an example of achieving results with limited resources"
• Story tip: Show creativity in resource constraints

11. Earn Trust
"Leaders listen attentively, speak candidly, and treat others respectfully."

• What it means: Build trust through integrity and respect
• Example question: "Tell me about a time you had to rebuild trust"
• Story tip: Show vulnerability and commitment to transparency

12. Dive Deep
"Leaders operate at all levels, stay connected to the details, and audit frequently."

• What it means: Understand the details deeply
• Example question: "Describe a time you used data to solve a problem"
• Story tip: Show your analytical process and attention to detail

13. Have Backbone; Disagree and Commit
"Leaders are obligated to respectfully challenge decisions when they disagree."

• What it means: Challenge decisions respectfully, then commit fully
• Example question: "Share an example of when you disagreed with a decision"
• Story tip: Show you can disagree professionally and commit to the team decision

14. Deliver Results
"Leaders focus on the key inputs for their business and deliver them with the right quality and in a timely fashion."

• What it means: Drive results and meet commitments
• Example question: "Tell me about a time you exceeded expectations"
• Story tip: Use specific metrics to quantify your impact

---

Additional Principles (added later)

15. Strive to be Earth's Best Employer
"Leaders work every day to create a safer, more productive, higher performing, more diverse, and more just work environment."

• Example question: "How have you created an inclusive team environment?"

16. Success and Scale Bring Broad Responsibility
"We started in a garage, but we are not there anymore. We are big, we impact the world, and we are far from perfect."

• Example question: "How do you consider the broader impact of your work?"

Story Bank Strategy

Prepare 8-10 stories that can cover multiple LPs:

Story Theme	LPs It Covers
Technical challenge	Customer Obsession, Dive Deep, Deliver Results
Disagreement with manager	Have Backbone; Disagree and Commit, Earn Trust
Mentoring junior	Hire and Develop the Best, Ownership
Tight deadline	Bias for Action, Deliver Results
Process improvement	Invent and Simplify, Frugality
Customer escalation	Customer Obsession, Earn Trust, Dive Deep
Learning new technology	Learn and Be Curious, Think Big
Quality vs speed decision	Insist on the Highest Standards, Bias for Action

STAR Story Template

Situation (15-20%):
"In my role at [Company], [brief context about the situation]."

Task (10-15%):
"I was responsible for [specific task/expectation]."

Action (50-60%):
"I took the following steps:
1. First, I [action 1] to [purpose].
2. Then, I [action 2] to [purpose].
3. Finally, I [action 3] to [purpose]."

Result (15-20%):
"As a result, [quantifiable outcome]. This led to [broader business impact]."

Story Quality Checklist

• Specific situation, not generic
• YOUR actions (not team's actions)
• Quantifiable results (numbers, metrics)
• Clear connection to the LP
• Demonstrates growth/learning
• Concise (2-3 minutes when spoken)

Common Follow-up Questions

1. "What would you do differently?"
2. "What did you learn from this experience?"
3. "How did this impact the team?"
4. "What was the biggest challenge?"
5. "How did stakeholders react?"

LP-to-Role Mapping

Role Type	Key LPs to Emphasize
SDE	Customer Obsession, Deliver Results, Dive Deep
TPM	Ownership, Think Big, Deliver Results
PM	Customer Obsession, Invent and Simplify, Bias for Action
SDE Manager	Hire and Develop the Best, Earn Trust, Insist on Highest Standards

Customer Obsession Story

Situation: A major client reported intermittent API failures affecting 10K daily users.

Task: I was responsible for diagnosing and resolving the issue within 24 hours to prevent customer churn.

Action:

1. I set up real-time monitoring to capture failure patterns and identified a race condition in the connection pool
2. I coordinated with the infrastructure team to implement a connection pooling fix
3. I personally reviewed the deployment to production and monitored metrics for 6 hours post-deployment

Result: API uptime improved from 97.2% to 99.95%. Customer ticket volume dropped 85% in the following week. Client renewed their $2M annual contract.

---

Ownership Story

Situation: Our team's deployment process was manual, error-prone, and took 4+ hours each release.

Task: While not my responsibility, I decided to investigate automation opportunities to improve team velocity.

Action:

1. I researched CI/CD best practices and proposed a GitHub Actions pipeline
2. I built the pipeline in 2 days, including automated testing and staged rollouts
3. I documented the process and trained 3 team members on maintenance

Result: Deployment time reduced to 15 minutes. Zero deployment errors in 6 months. Team velocity increased 30%. The pipeline was adopted by 2 other teams.

---

Have Backbone; Disagree and Commit Story

Situation: The team decided to use a NoSQL database for a new feature, but I believed a relational DB was more appropriate.

Task: I needed to voice my concerns while respecting the team's decision-making authority.

Action:

1. I documented my analysis showing ACID compliance was critical for this use case
2. I presented data showing NoSQL would require 3x more code for transaction management
3. The team chose NoSQL anyway; I committed fully and helped optimize the implementation

Result: Six months later, we hit data consistency issues. My earlier analysis was validated. We migrated to PostgreSQL, but I learned to advocate more strongly for architectural concerns.

---

Deliver Results Story

Situation: We had 2 weeks to deliver a critical feature for a product launch affecting 500K users.

Task: I needed to design and implement the recommendation engine while managing technical debt.

Action:

1. I broke the feature into MVP scope and stretch goals with clear priorities
2. I implemented core collaborative filtering first, then optimized with caching
3. I coordinated with frontend and QA daily to ensure integration didn't block progress

Result: Delivered 2 days ahead of schedule. Feature drove 15% increase in user engagement. Recommendation click-through rate was 23%, exceeding the 18% target.

---

Frugality Story

Situation: Our team's AWS bill was $45K/month and growing, with no budget increase approved.

Task: I needed to reduce costs without impacting performance or reliability.

Action:

1. I analyzed usage patterns and identified 40% of instances were over-provisioned
2. I implemented auto-scaling and right-sizing, reducing costs by $18K/month
3. I set up cost monitoring dashboards to prevent future waste

Result: Saved $216K annually. Infrastructure reliability actually improved (fewer over-provisioned instances = cleaner monitoring). Dashboard became a team standard.

---

Learn and Be Curious Story

Situation: Our team used legacy Java patterns while industry was moving to reactive architectures.

Task: I wanted to modernize our approach but had no formal training budget.

Action:

1. I completed 3 online courses on reactive programming in evenings
2. I built a proof-of-concept demonstrating 60% latency improvement
3. I presented findings to team and led weekly lunch-and-learn sessions

Result: Team adopted reactive patterns for 2 new services. P99 latency dropped 45%. I became the team's go-to expert on reactive architecture.

---

Common Follow-up Question Strategies

Follow-up Question	What They're Testing	How to Answer
"What would you do differently?"	Growth mindset	Be specific about changes, show self-awareness
"What did you learn?"	Learning orientation	Connect to broader principles, show application
"How did the team react?"	Collaboration	Show influence without authority
"What was the hardest part?"	Problem-solving	Focus on decision-making under uncertainty
"Why not a different approach?"	Judgment	Explain reasoning process and alternatives considered