Success and Scale Bring Broad Responsibility: Amazon Questions
Success and Scale Bring Broad Responsibility is the newest of Amazon's leadership principles, added in 2021. Amazon's wording opens: "We started in a garage, but we're not there anymore. We are big, we impact the world, and we are far from perfect. We must be humble and thoughtful about even the secondary effects of our actions." It closes with the line interviewers quote most: "Leaders create more than they consume and always leave things better than how they found them."
What is Success and Scale Bring Broad Responsibility?
This principle is about second-order effects. At Amazon's size, a rounding error touches millions of people, so leaders are expected to think past "does this hit the metric" to "what else does this change, and for whom": communities, the environment, sellers, future maintainers of the system you are shipping.
For candidates, the practical translation is impact awareness at your own scale. You do not need a story about saving the planet; you need one where you noticed a consequence nobody asked you to consider, and acted on it.
What interviewers look for
- Secondary-effect thinking: you anticipated who else your decision would touch, beyond the obvious stakeholder.
- Leaving it better: systems, docs, teams, or processes that improved because you passed through them.
- Humility at scale: owning a decision that had unintended consequences and what you changed after.
Success and Scale interview questions
- Tell me about a decision of yours that had unintended consequences. What did you do?
- Describe a time you considered the broader impact of your work beyond your immediate goal.
- Tell me about a time you left a project, codebase, or team better than you found it.
- Have you ever flagged an ethical or fairness concern with something you were building?
- Describe a time you balanced business goals against a broader responsibility.
- What is something you built that outlived your involvement? Why did it last?
How to answer
The strongest stories show unprompted breadth: nobody assigned you the secondary effect, you went looking for it. Structure with STAR and be specific about who benefited beyond your team. And keep the humility real: a story that ends "and that is why I was right all along" misses the principle's core, which is that scale makes everyone's mistakes matter more.
Every principle interviews better with a prepared example: our story bank guide shows how to build one, and the Amazon Leadership Principles guide covers the rest of the list. Want practice against someone who has run these loops? Get matched with a coach.