Are Right a Lot - What It Means and What Interviewers Listen For - Amazon LP Competency

Definition

Are Right a Lot means consistently making sound decisions and good judgments based on data, experience, and intuition. The core test is whether the candidate can demonstrate they independently identified the right course of action, even under uncertainty.

Core Signal

Did the candidate independently identify the right solution based on data, analysis, and sound judgment?

Company Framing

Amazon wants owners who fix root causes and make high-quality decisions, not hired guns who patch symptoms or blindly follow orders.

What It Is NOT

• Completing assigned tasks well - that is execution, not Are Right a Lot
• Being perfect or never making mistakes - Amazon values learning from errors
• Simply following manager instructions or team consensus without question
• Relying solely on gut feeling without data or logical reasoning
• Showing confidence without backing it up with evidence or analysis

Candidate describes identifying a problem or opportunity that others missed or ignored.

"I noticed""nobody had flagged it""wasn't on my sprint"

Shows proactive insight and independent thinking beyond assigned scope.

Common Miss My manager mentioned it might be worth looking into

Candidate explains how they gathered data or evidence to validate their hypothesis.

"I analyzed logs""I ran experiments""I collected metrics"

Demonstrates data-driven decision making rather than guesswork.

Common Miss I just felt it was the right thing to do

Candidate articulates trade-offs considered and why they chose a particular approach.

"I weighed the cost versus benefit""I considered the risk of delay""I prioritized based on impact"

Shows mature judgment and ability to balance competing factors.

Common Miss I just did what seemed easiest

Candidate describes how they challenged assumptions or conventional wisdom.

"I questioned the existing process""I disagreed with the initial plan""I proposed an alternative"

Indicates intellectual humility and courage to improve decisions.

Common Miss I followed what the team decided

Candidate quantifies impact of their decision with metrics and business outcomes.

"This reduced errors by 30%""We saved $8K per week""Customer complaints dropped 20%"

Confirms the decision was not only right but materially valuable.

Common Miss The team was happy with the change

Candidate admits uncertainty and explains how they managed risk.

"I had 70% of the data I wanted""I mitigated risk by adding monitoring""I planned to iterate after launch"

Shows realistic judgment and ownership of outcomes despite imperfect info.

Common Miss I waited until I had all the data

Depth Tip

Action section = 70% of your answer. Situation+Task combined = 50 seconds max. Focus on what YOU did, with 3+ sentences starting with 'I'.

Manager-Assigned Initiation

"My manager suggested I look into this since I had bandwidth"

Ownership is binary - self-initiated or not. Manager-assigned = execution. No excellent execution recovers an assigned story.

DetectionAsk: Would I have done this if my manager said nothing? If no, find a different story.

Fix"I noticed X while doing Y. Nobody had filed a ticket. I decided to act because..."

Team Consensus Without Own Judgment

"We all agreed to follow the existing process"

Shows lack of independent judgment or challenge; candidate is a follower, not a decision maker.

DetectionAsk: Did I propose or evaluate alternatives independently?

Fix"I evaluated the options and recommended a different approach because..."

No Data or Evidence

"I just felt it was the right thing to do"

Decisions without data or analysis are guesses, not Are Right a Lot.

DetectionAsk: What data or facts supported your decision?

Fix"I analyzed logs and metrics which showed..."

No Quantified Impact

"The team was happy with the change"

Without measurable impact, the decision’s value is unproven.

DetectionAsk: How did you measure success or impact?

Fix"This reduced errors by 30% and saved $8K/week."

Blame or Escalation Without Solution

"I escalated it to the Payments team and they eventually fixed it"

Escalating without owning a fix is not Are Right a Lot; it’s passing responsibility.

DetectionAsk: What concrete action did I take to solve the problem?

Fix"I brought a complete fix and flagged it for visibility."

Passive Voice Throughout

"The problem was identified and then fixed"

Candidate was spectator not actor. Passive strips agency from every action.

FixUse active voice: 'I identified the problem and fixed it.'

Vague Language

"We improved the system"

No clarity on candidate’s specific contribution or decision.

FixSpecify: 'I improved the system by refactoring the caching layer.'

Overuse of 'We' or 'Team'

"We did it together"

Hides individual ownership and decision-making.

FixUse 'I' to highlight your role: 'I designed and implemented...'

Hedging or Uncertainty

"I think it might have helped"

Shows lack of confidence or clarity on impact.

FixState concrete results: 'This reduced latency by 15%.'

Overly Technical Jargon

"I optimized the RPC pipeline with gRPC multiplexing"

May confuse non-technical interviewer and obscure judgment.

FixExplain in business terms: 'I improved response time, reducing customer wait.'

Direct Triggers

• Tell me about a time you were right despite others disagreeing.
• Describe a decision you made that turned out to be correct.
• Give an example when you used data to make a tough call.
• How do you ensure your decisions are usually right?

Indirect Triggers

• Describe a time you solved a problem no one else noticed.
• Tell me about a time you challenged the status quo.
• Give an example of when you made a decision with incomplete information.
• Describe a situation where you had to balance risk and speed.

How to Recognize

Keywords: 'I noticed', 'without being asked', 'beyond my role', 'proactively', 'impact', 'trade-off', 'data-driven', 'challenged assumptions'.

Do Not Confuse With

OwnershipOwnership is about self-initiating and fixing root causes; Are Right a Lot focuses on making sound decisions and judgments.

Deliver ResultsDeliver Results is hitting a committed goal under pressure set by manager; Are Right a Lot is about independently identifying the right course of action.

Bias for ActionBias for Action emphasizes speed and decisiveness; Are Right a Lot emphasizes quality and correctness of decisions.

How did you verify your decision was correct after implementation?

Probes: Checks if candidate follows through and validates outcomes.

Weak

I assumed it worked because no one complained.

No active validation or measurement; passive assumption weakens Are Right a Lot signal.

Strong

I monitored key metrics for two weeks and saw a 25% drop in errors, confirming the fix.

""I validated success with concrete metrics post-launch.""

What trade-offs did you consider before deciding your approach?

Probes: Reveals depth of judgment and ability to balance competing priorities.

Weak

I just picked the fastest solution.

Shows lack of thoughtful decision-making; ignores risks or costs.

Strong

I balanced implementation speed against potential downtime and chose a phased rollout to minimize risk.

""I explicitly weighed risks and benefits before deciding.""

Did you consult others or challenge existing opinions before deciding?

Probes: Assesses intellectual humility and willingness to seek input or challenge assumptions.

Weak

I followed what the team decided.

No independent judgment or challenge; candidate is a follower.

Strong

I gathered input from three teams but ultimately proposed a different approach based on data analysis.

""I combined collaboration with independent judgment.""

How did you handle uncertainty or incomplete information?

Probes: Evaluates risk management and decision-making under ambiguity.

Weak

I waited until I had all the data.

Delaying action shows lack of Bias for Action and ownership of outcomes.

Strong

I acted with 70% of the data and added monitoring to catch issues early, planning to iterate.

""I managed risk by acting decisively with partial data and monitoring.""

Amazon

Are Right a Lot

Amazon looks for long-term thinking - fix root cause not just symptom. Candidates must show data-driven decisions and quantify impact.

Signal: "I also proposed adding X to prevent this class of problem in future services."

Example QTell me about a time you took ownership of a problem that wasn't yours and made the right decision.

What Elevates

Name the trade-off explicitly: I pushed sprint item back 2 days. Cost of inaction ($8K/week) exceeded cost of delay. Amazon credits candidates who articulate the trade-off explicitly and show root cause fixes, demonstrating ownership and strategic thinking.

Google

Good Judgment

Google values collaborative decision-making and data-backed reasoning but also expects candidates to seek consensus when appropriate.

Signal: "I gathered input from multiple stakeholders and synthesized data to recommend a path forward."

Example QDescribe a time you made a decision that was initially unpopular but proved correct.

What Elevates

Explain how you balanced data with stakeholder concerns and how you persuaded others with evidence and logic, showing both sound judgment and collaboration.

Meta

Move Fast and Be Bold

Meta emphasizes speed and iteration; being right a lot includes making fast decisions with incomplete data and learning quickly from mistakes.

Signal: "I acted with partial data and set up rapid feedback loops to course-correct."

Example QGive an example of a time you made a quick decision that turned out to be right.

What Elevates

Highlight how you balanced speed with risk and how you iterated based on early results, demonstrating agility and learning mindset.

Flipkart

Customer Obsession

Flipkart expects decisions to be grounded in customer impact and data; Are Right a Lot means anticipating customer needs and validating assumptions.

Signal: "I analyzed customer feedback and metrics before deciding on the feature rollout."

Example QTell me about a time you made a decision that improved customer experience.

What Elevates

Focus on how you used customer data to guide your decision and measured improvements post-implementation, showing customer-centric and data-driven judgment.

SDE 1

Handles tasks or bugs outside assigned scope with clear individual contribution and measurable team impact; stories do not require cross-team coordination but show independent judgment.

Anti-pattern Story limited to assigned tasks with no independent judgment or impact beyond immediate team.

SDE 2

Owns moderately complex problems involving multiple components; demonstrates data-driven decisions and quantifies impact; may involve coordination across teams and balancing trade-offs.

Anti-pattern Story lacks data-driven decision-making or measurable impact; no cross-team scope despite level expectations.

Senior SDE

Leads cross-team initiatives; challenges assumptions and proposes scalable solutions; balances trade-offs with long-term thinking and quantifiable business outcomes; influences broader technical direction.

Anti-pattern Story confined to own team codebase; Senior must show cross-team scope. Single-team ownership = SDE1 behavior. No Hire at Senior.

Staff Principal

Defines strategy for ambiguous problems affecting multiple teams or products; drives high-impact decisions with incomplete data; mentors others on judgment and decision-making; shapes organizational priorities.

Anti-pattern Story is tactical without strategic influence; no evidence of mentoring or shaping broader technical direction.

Cross-Team Bug Fix with No Ticket

Shows candidate independently noticed a problem outside their scope, gathered data, and fixed root cause without assignment.

Webhook delivery (Platform team) silently dropping 0.3% payments - no alert, no owner watching, not your sprint, quantifiable impact.

Also covers: Ownership · Dive Deep · Deliver Results

Challenging Existing Process

Demonstrates intellectual humility and courage to question status quo and propose better solutions based on data.

Noticed manual QA step causing delays; analyzed data; proposed automation that cut release time by 40%.

Also covers: Invent and Simplify · Bias for Action · Learn and Be Curious

Data-Driven Trade-Off Decision

Shows mature judgment balancing competing priorities with quantified impact and risk management.

Decided to delay feature launch by 3 days to fix critical bug; quantified cost of delay vs customer impact.

Also covers: Deliver Results · Customer Obsession · Bias for Action

Stories Not Recommended

• Assigned Deadline Crunch - Staying late = effort not proactivity. Deadline was assigned. Effort is execution. Ownership is self-initiated.
• Team Project Without Individual Contribution - Using 'we' without specifying your role hides ownership and decision-making.

Prep Action

Select stories where you independently identified problems or decisions beyond your assigned scope, backed by data and measurable impact.

Consistently make sound, data-driven decisions independently.

Key Signal

"I noticed" -> "I analyzed data" -> "I weighed trade-offs" -> "I quantified impact"

Top Disqualifier

"My manager suggested I look into this since I had bandwidth"

Delivery Red Flag

"We did it together"

Prep Action

Prepare stories showing independent, data-backed decisions with measurable impact beyond assigned scope.

Practice

1. A candidate describes how they analyzed conflicting data sources, challenged assumptions, and proposed a new approach that improved forecasting accuracy by 15%. Which Amazon Leadership Principle does this primarily demonstrate?

easy

A. Bias for Action

B. Dive Deep

C. Are Right a Lot

D. Customer Obsession

Solution

1. Step 1: Identify the core behavior -- challenging assumptions and improving accuracy.
2. Step 2: Recognize this aligns with making good decisions and being right a lot -> Are Right a Lot
3. Step 3: Differentiate from Bias for Action (speed focus), Customer Obsession (customer focus), and Dive Deep (investigation focus without decision emphasis).

Hint: Challenging assumptions and improving accuracy -> Are Right a Lot

Common Mistakes:

2. Candidate answer: "My manager asked me to investigate why sales dropped last quarter. I worked with the team, and we found some issues. We fixed them, and the team was happy with the results." What is the PRIMARY weakness in this answer?

easy

A. Manager-assigned investigation, no self-initiation

B. Weak reflection on lessons learned

C. No second-order effect described

D. Too short and vague

Solution

1. Step 1: Identify who initiated the investigation -> Manager-assigned investigation, no self-initiation
2. Step 2: Recognize this destroys ownership and Are Right a Lot signals.
3. Step 3: Secondary issues like weak reflection or no second-order effect are present but not primary.

Hint: Manager asks -> ownership lost, fatal weakness

Common Mistakes:

3. "I challenged the initial assumptions by gathering additional data and proposed a new model that improved accuracy by 20%." Which LP/signal does this sentence primarily demonstrate?

medium

A. Are Right a Lot

B. Dive Deep

C. Bias for Action

D. Invent and Simplify

Solution

1. Step 1: Focus on challenging assumptions and improving accuracy -> Are Right a Lot
2. Step 2: This is core to Are Right a Lot, not just investigation (Dive Deep) or speed (Bias for Action).
3. Step 3: Invent and Simplify is about innovation, less about correctness.

Hint: Challenge assumptions + improve accuracy -> Are Right a Lot

Common Mistakes:

4. What does the phrase "My manager asked me to look into the issue" signal to the interviewer?

medium

A. Shows good communication with management

B. Indicates task assignment, ownership signal destroyed

C. Demonstrates proactive problem identification

D. Reflects strong time management skills

Solution

1. Step 1: Identify who initiated the action -> Indicates task assignment, ownership signal destroyed
2. Step 2: This destroys ownership and Are Right a Lot signals.
3. Step 3: It is not about communication quality or time management.

Hint: Manager asks -> ownership lost, fatal signal

Common Mistakes:

5. Candidate answer: "I noticed a recurring error in our data pipeline and independently investigated the root cause. I proposed a fix that reduced errors by 30%. We collectively decided to implement the change, and the team saw improved reliability. I also documented the process to prevent future issues." Which element is the disqualifier?

hard

A. I independently investigated the root cause

B. I proposed a fix that reduced errors by 30%

C. I documented the process to prevent future issues"

D. We collectively decided to implement the change

Solution

1. Step 1: Identify who initiated and drove the solution -> We collectively decided to implement the change
2. Step 2: Note the phrase 'We collectively decided' dilutes ownership and decision authority.
3. Step 3: Other elements show strong ownership, impact, and follow-through.
4. Step 4: Therefore, 'We collectively decided' is the subtle disqualifier.

Hint: "We collectively decided" -> subtle ownership dilution

Common Mistakes: