Bird
Raised Fist0
Amazon Leadership PrinciplesSignal: "I changed my mind after reviewing X data" -> "I led the new approach" -> "Impact: Y% improvement, $Z saved"

Tell Me About a Time You Changed Your Mind Based on New Evidence - Amazon LP Competency

Demonstrate data-driven humility and impactful pivots.

Choose your preparation mode3 modes available
📌
Definition

Are Right a Lot means consistently making good decisions by seeking diverse perspectives and updating your beliefs when presented with new evidence. The core test is whether you can admit when you were wrong and pivot based on data rather than ego or assumptions.

Core Signal
Did the candidate demonstrate intellectual humility by changing their mind based on new, relevant evidence?
🏢
Company Framing

Amazon expects leaders to be vocally self-critical and data-driven; being right a lot means you seek diverse inputs, challenge your own thinking, and pivot quickly when facts contradict your initial view.

🚫
What It Is NOT
  • Stubbornly sticking to your initial opinion despite contrary facts
  • Simply executing assigned tasks well without questioning assumptions
  • Changing your mind just to please others or avoid conflict
  • Guessing or making decisions without data or thoughtful analysis
  • Confusing confidence with correctness
Candidate explicitly states they changed their mind after discovering new data or feedback.
"I realized my initial assumption was incorrect""After reviewing the metrics, I changed my approach""New evidence showed that my first idea wouldn't work""I updated my plan based on feedback from the team"

Shows intellectual humility and data-driven decision making, core to Are Right a Lot.

Common Miss My manager mentioned it might be worth looking into
Candidate describes seeking diverse perspectives or challenging their own beliefs.
"I asked others for their opinions""I challenged my own hypothesis""I dug deeper into the root cause""I tested alternative solutions before deciding"

Demonstrates curiosity and rigor in validating assumptions before committing.

Common Miss I just trusted my gut feeling
Candidate quantifies the impact of changing their mind on the project or business.
"This prevented a potential $10K weekly loss""By pivoting, we improved system uptime by 15%""Changing course saved us two weeks of rework""The new approach increased customer satisfaction scores"

Amazon values measurable impact; this shows the candidate’s decision was not just right but consequential.

Common Miss We fixed the problem eventually
Candidate takes personal ownership for the decision to change their mind.
"I decided to change the design""I took responsibility to update the plan""I owned the communication of the new direction""I led the effort to implement the revised solution"

Shows ownership and accountability, not deflecting responsibility to others.

Common Miss The team decided to change the approach
Candidate explains how they balanced risk of acting without full information.
"I had 70% of the data but chose to act""I mitigated risk by adding monitoring""I planned contingencies in case the new approach failed""I escalated the uncertainty but moved forward"

Shows Amazon’s bias for action combined with Are Right a Lot’s demand for good judgment.

Common Miss I waited until I had all the data before acting
Candidate describes learning from the experience to improve future decisions.
"I documented the lessons learned""I proposed a process change to avoid similar mistakes""I shared the findings with other teams""I updated our playbook based on this outcome"

Demonstrates Learn and Be Curious and continuous improvement linked to Are Right a Lot.

Common Miss I just moved on to the next task
💡
Depth Tip

Spend about 50 seconds on Situation and Task combined, then 70% of your time on Action detailing your thought process, data gathering, and decision to pivot; finish with a quantified Result and lessons learned.

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 yourself: 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..."
No Evidence of Mind Change
"I stuck to my original plan despite some feedback"
Are Right a Lot requires intellectual humility and willingness to pivot; ignoring new evidence signals rigidity.
DetectionListen for explicit statements about changing opinion or approach based on data.
Fix"After seeing the new data, I realized my initial approach was flawed and adjusted accordingly."
Vague or Generic Impact
"We fixed the problem eventually"
Without quantifiable impact, the story lacks evidence that the decision to change was meaningful or valuable.
DetectionCheck if candidate provides metrics or business outcomes tied to their decision.
Fix"By changing the design, we reduced error rates by 20%, saving $5K weekly."
Group Ownership Without Individual Contribution
"We decided to change the approach after team discussion"
Amazon looks for individual ownership; diffusing credit to the group hides candidate’s role and weakens signal.
DetectionAsk: What exactly did you do? If answer is 'we', probe for personal actions.
Fix"I led the analysis and proposed the new approach after reviewing the data."
Changing Mind Due to Pressure, Not Evidence
"I changed my mind because my manager insisted"
Changing opinion due to external pressure rather than new facts shows lack of independent judgment.
DetectionListen for reasons behind pivot; if only external pressure, story fails Are Right a Lot.
Fix"I changed my mind after analyzing the new logs that contradicted my initial hypothesis."
🚩 Passive Voice Throughout
"The problem was identified and a fix was implemented"
Candidate was spectator not actor. Passive strips agency from every action.
FixUse active voice: "I identified the problem and implemented the fix."
🚩 Overuse of 'We' Without Clarification
"We decided to change the design"
Obscures candidate’s individual contribution; interviewer cannot assess ownership.
FixSpecify your role: "I proposed and led the design change."
🚩 Hedging Language
"I think I might have changed my mind"
Sounds uncertain and reduces confidence in candidate’s judgment.
FixState confidently: "I changed my mind after reviewing the data."
🚩 Lack of Specifics on Evidence
"Some data suggested a problem"
Vague evidence weakens credibility of decision to pivot.
FixSpecify: "Metrics showed a 15% drop in throughput starting last week."
🚩 No Quantified Impact
"The change helped the team"
Without metrics, impact is anecdotal and less convincing.
FixQuantify: "The change improved system uptime by 10%, reducing customer complaints by 30%."
🎯
Direct Triggers
  • Tell me about a time you changed your mind based on new evidence.
  • Describe a situation where you realized your initial approach was wrong and what you did.
  • Give an example of when you had to admit you were wrong and pivot.
  • Have you ever made a decision that you later reversed? What caused the change?
🔍
Indirect Triggers
  • Describe a time you had to learn something new to solve a problem.
  • Tell me about a time you received critical feedback and how you responded.
  • Give an example of when you had to adjust your plan due to unexpected data.
  • Describe a situation where you challenged your own assumptions.
👁
How to Recognize

Keywords: changed my mind, new evidence, updated my approach, realized I was wrong, pivoted, challenged assumptions, data showed, feedback caused me to rethink.

⚠️
Do Not Confuse With
OwnershipOwnership is about self-initiating and taking responsibility; Are Right a Lot focuses on decision quality and intellectual humility.
Bias for ActionBias for Action emphasizes speed and decisiveness; Are Right a Lot emphasizes correctness and willingness to revise decisions.
Learn and Be CuriousLearn and Be Curious is about seeking new knowledge; Are Right a Lot is about applying that knowledge to improve decisions.
What specific data or feedback made you change your mind?
Probes: Tests whether candidate’s pivot was based on concrete evidence or vague impressions.
❌ Weak

"I just felt it wasn’t working anymore."

No concrete evidence; sounds like a gut feeling, not data-driven decision.

✅ Strong

I reviewed the error logs and saw a 25% increase in failures after deployment, which contradicted my initial assumption that the code was stable.

""I changed my mind because the error rate jumped 25%, proving my initial assumption wrong.""
How did you ensure your new approach was better before fully committing?
Probes: Evaluates candidate’s rigor and risk management before pivoting.
❌ Weak

"I just switched immediately without testing."

Shows rash decision-making without validation, risking bigger problems.

✅ Strong

I ran a small-scale A/B test comparing the new approach against the old one, monitored key metrics for 48 hours, and confirmed improvements before rolling out fully.

""I validated the new approach with an A/B test before full deployment.""
What was your personal role in driving the change after you decided to pivot?
Probes: Assesses individual ownership and leadership in executing the new plan.
❌ Weak

"The team handled the implementation after I suggested it."

Diffuses ownership; candidate appears passive and not accountable.

✅ Strong

I wrote the new design document, coordinated with the QA team for testing, and led the deployment to production.

""I led the design, testing, and deployment of the new solution.""
What did you learn from this experience that you applied later?
Probes: Checks for self-awareness and continuous improvement mindset.
❌ Weak

"I just moved on to the next project."

No reflection or learning; misses opportunity to grow.

✅ Strong

I documented the root cause and updated our monitoring dashboards to catch similar issues earlier in the future.

""I improved our monitoring to prevent recurrence of this issue.""
AM
Amazon
Are Right a Lot

Amazon looks for leaders who are vocally self-critical and data-driven; being right a lot means you seek diverse inputs, challenge your own thinking, and pivot quickly when facts contradict your initial view.

Signal: Candidate says: 'I updated my plan after reviewing the metrics and feedback, even though it meant pushing back delivery.'
Example QTell me about a time you changed your mind based on new evidence.
What Elevates

To elevate your answer at Amazon, explicitly name the trade-offs you made, such as delaying delivery by two days, and quantify the impact, like avoiding a potential $8K weekly loss. This shows clear judgment, ownership, and understanding of business consequences, which Amazon highly values.

GO
Google
Good Judgment

Google values data-driven decisions but also emphasizes collaboration and consensus-building before pivoting.

Signal: Candidate says: 'I gathered input from cross-functional partners and incorporated their feedback before changing course.'
Example QDescribe a time you revised your approach after new information surfaced.
What Elevates

Highlight how you balanced data with stakeholder alignment, showing both analytical rigor and teamwork, which Google highly values.

ME
Meta
Move Fast

Meta prioritizes speed and iteration; changing your mind quickly to improve outcomes is valued even if data is incomplete.

Signal: Candidate says: 'I had partial data but chose to pivot quickly to avoid bigger issues, planning to iterate after launch.'
Example QGive an example of when you had to pivot your plan rapidly.
What Elevates

Explain how you balanced speed with risk, showing bias for action while managing uncertainty, which aligns with Meta’s culture.

FL
Flipkart
Customer Obsession

Flipkart expects decisions to be driven by customer impact; changing your mind must be justified by improved customer experience.

Signal: Candidate says: 'I changed the feature design after customer feedback showed confusion, improving usability scores by 10%.'
Example QTell me about a time you changed your mind to better serve customers.
What Elevates

Focus on how the pivot directly benefited customers, quantifying the improvement and showing customer obsession.

SDE 1

At this level, candidates handle tasks or bugs within their assigned scope, showing clear individual contribution and impact within their immediate team. Cross-team coordination is not expected, but evidence of self-initiation and data-driven pivot is important.

Anti-pattern Story is purely assigned work with no evidence of self-initiation or mind change; impact limited to own tasks.
SDE 2

Candidates demonstrate ownership of moderately complex problems involving multiple stakeholders. They show clear data-driven pivots, quantify impact, and begin influencing beyond their immediate team by communicating trade-offs and decisions effectively.

Anti-pattern Story lacks quantifiable impact or cross-team scope; candidate cannot clearly explain why they changed their mind.
Senior SDE

Senior engineers lead cross-team initiatives requiring deep analysis and judgment. They articulate trade-offs and risk management clearly, drive significant business impact, and mentor others on decision quality and intellectual humility.

Anti-pattern Story confined to own team codebase without cross-team influence; no evidence of risk management or trade-off analysis.
Staff Principal

Staff or Principal engineers own large-scale, ambiguous problems spanning multiple teams or organizations. They anticipate future risks, balance incomplete data with bold decisions, and set standards for Are Right a Lot across the organization, influencing culture and processes.

Anti-pattern Story is tactical and reactive rather than strategic; candidate fails to demonstrate long-term thinking or influence beyond immediate projects.
📖
Cross-Team Bug Discovery

Shows candidate noticed an issue outside their team, took initiative to investigate, and changed their initial hypothesis based on data. Demonstrates ownership, Are Right a Lot, and Dive Deep.

Webhook delivery (Platform team) silently dropping 0.3% payments - no alert, no owner watching, not your sprint, quantifiable impact.
Also covers: Ownership · Dive Deep · Bias for Action
📖
Pivot After Customer Feedback

Candidate changed product design after analyzing customer complaints, showing intellectual humility and customer obsession.

Feature rollout caused confusion; candidate analyzed feedback, revised UI, and improved NPS by 5 points.
Also covers: Customer Obsession · Learn and Be Curious · Deliver Results
📖
Data-Driven Process Improvement

Candidate challenged existing process assumptions, gathered metrics, and implemented a better workflow, reducing errors by 20%.

Manual QA process causing delays; candidate proposed automation after data analysis.
Also covers: Invent and Simplify · Dive Deep · Bias for Action
🚫
Stories Not Recommended
  • Effort Without Pivot - Staying late or working hard on assigned tasks shows effort but not intellectual humility or willingness to change mind.
  • Manager-Assigned Task Execution - Stories where candidate acted only because manager assigned the task lack self-initiation and ownership, critical for Are Right a Lot.
🎯
Prep Action
Select stories where you personally identified a problem, gathered new evidence, and changed your approach with measurable impact; practice articulating your thought process and trade-offs clearly.
Demonstrate data-driven humility and impactful pivots.
Key Signal
"I changed my mind after reviewing X data" -> "I led the new approach" -> "Impact: Y% improvement, $Z saved"
Top Disqualifier
"My manager suggested I look into this since I had bandwidth"
Delivery Red Flag
"The problem was identified and a fix was implemented"
Prep Action
Prepare stories where you self-initiated investigation, pivoted based on concrete evidence, and quantified the business impact.