Are Right, A Lot: Amazon Interview Questions and How to Answer

Are Right, A Lot is easy to over-read as "tell me about a time you were correct." That's not quite it. The principle name is deliberately "a lot," not "always," and Amazon is scoring your decision-making process, not whether the outcome happened to work out. A well-reasoned call that didn't pan out can be strong evidence; a lucky guess is not.

This guide covers the questions this principle triggers, why process beats outcome, and how to build an answer around genuine judgment.

What Are Right, A Lot actually means

The definition: leaders are right a lot. They have strong judgment and good instincts. They seek diverse perspectives and work to disconfirm their own beliefs. The "disconfirm their own beliefs" clause is the real test here: Amazon wants to see that you actively look for reasons you might be wrong before committing to a decision, not that you're simply confident.

Sample questions

• Walk me through your most difficult judgment call with no obvious right answer.
• Tell me about a time you sought out a perspective that disagreed with yours.
• Describe a strongly held opinion you reversed. What changed your mind?
• Tell me about a time you made a decision with incomplete data. How did you decide?
• Describe a time you were wrong. How did you find out, and what did you do?
• Tell me about a time your judgment was challenged and you turned out to be right.

How to structure a strong answer

Lead with the decision and why it was genuinely hard, not a call with an obvious answer dressed up as difficult. Spend most of the answer on your process: what information you gathered, whose disagreeing view you actively sought out, and what you did to test your own assumption before committing. Close with the outcome, but frame it as confirmation of a sound process rather than the entire point of the story.

"Our team was split on whether to rebuild a legacy service or patch it incrementally, and I initially favored the rebuild. Before committing, I deliberately asked the engineer most opposed to that plan to walk me through their concerns in detail, and their point about migration risk changed my recommendation to a phased patch instead. That approach shipped with zero downtime, versus an estimated two-week cutover for the rebuild."

What interviewers are listening for

• A genuinely difficult decision, not one with an obvious right answer. If there was no real tension, the story doesn't demonstrate judgment.
• Evidence you sought disagreement. Actively asking for an opposing view, and actually updating based on it, is the strongest possible signal for this principle.
• Process over outcome. A sound decision that didn't work out due to something you couldn't have known is still a strong answer if the reasoning was solid.
• Willingness to be wrong. A story where you reversed a strongly held opinion because of new evidence is one of the most convincing versions of this principle.

Common mistakes

The most common failure is a story that's really about a lucky outcome with no real decision-making tension behind it. The second is describing your judgment as unchanging or always correct, which contradicts the principle's explicit framing of seeking out disconfirming views. The third is skipping the process entirely and jumping straight to a good result, giving the interviewer nothing to evaluate about how you actually think.

This principle pairs closely with Have Backbone; Disagree and Commit and Dive Deep: sound judgment usually comes from digging into real information, and voicing it well often means disagreeing with someone respectfully. See the full Leadership Principles guide for how all 16 fit together.

Explaining your reasoning clearly under a live follow-up is a different skill than writing it down. Bar Raiser AI runs adaptive voice mock interviews that test your judgment the way a real Bar Raiser would.