0Tell Me About a Time You Had to Choose Between Two Competing Valid Approaches - Amazon LP Competency
Choosing wisely between competing valid options with data.
Are Right a Lot means consistently making sound decisions by using good judgment, deep understanding, and seeking diverse perspectives. The core test is how a candidate chooses wisely between multiple valid options under uncertainty.
Amazon expects leaders to be owners who dive deep into data and context, challenge assumptions, and make high-quality decisions that stand the test of time.
- Completing assigned tasks well - that is execution, not judgment.
- Being stubborn or refusing to listen to others.
- Claiming to be right without data or reasoning.
- Making quick guesses without thoughtful analysis.
- Avoiding decisions by deferring to others.
Shows the candidate does not rely on gut feeling but seeks evidence to be right.
Demonstrates nuanced thinking and ability to handle complexity.
Shows humility and practical judgment under ambiguity.
Indicates openness and intellectual humility, key to being right a lot.
Connects decision quality to measurable business outcomes.
Spend about 70% of your answer on the Action section, detailing your thought process and decision criteria. Limit Situation and Task combined to 50 seconds to maximize time for explaining your reasoning.
- Tell me about a time you had to choose between two competing valid approaches.
- Describe a situation where you made a decision with incomplete information.
- Give an example of when you challenged your own assumptions to make a better decision.
- Tell me about a time you were right despite initial doubts from others.
- Describe a complex problem you solved where multiple solutions were possible.
- Tell me about a time you had to balance trade-offs in a technical decision.
- Give an example of when you learned something new to improve your decision.
- Describe a time you influenced others to adopt your approach.
Keywords: 'trade-offs', 'data-driven', 'validated assumptions', 'challenged hypothesis', 'weighed options', 'mitigated risk', 'experimented', 'consulted experts'.
"I assumed it worked because no one complained."
No evidence of validation or learning; shows lack of ownership and rigor.
I monitored key metrics post-launch and saw a 25% reduction in errors within two weeks, confirming the decision’s effectiveness.
"I just picked the fastest solution."
Ignores complexity and nuance; suggests shallow thinking.
I prioritized scalability over initial speed because the system needed to handle growth, accepting a 10% latency increase temporarily.
"I made the decision on my own without input."
May indicate arrogance or narrow viewpoint, reducing decision quality.
I discussed options with the database team and product manager to incorporate their insights before finalizing.
"Nothing, it was perfect the first time."
Shows lack of reflection and growth mindset.
I would gather more user feedback earlier to catch edge cases sooner.
Amazon looks for long-term thinking - fix root cause not just symptom. Leaders dive deep into data and challenge assumptions.
Amazon values candidates who explicitly articulate the trade-offs they considered, including costs and benefits, and who demonstrate ownership by explaining the consequences of their decision on business metrics such as cost savings or performance improvements. For example, stating: 'I pushed the sprint item back 2 days because the cost of inaction was $8K per week, which exceeded the cost of delay.' This level of detail and ownership elevates the answer.
Google values data-informed decisions but also creativity and user focus. Emphasis on scalable, elegant solutions.
Highlight how you integrated user feedback with technical trade-offs to arrive at a solution that scales and delights users.
Meta prioritizes speed and iteration. Being right a lot means making good decisions quickly and learning fast from mistakes.
Explain how you balanced speed with risk, ran experiments, and iterated based on results to improve the decision.
At this level, candidates handle tasks or bugs outside their assigned scope with clear individual contributions and measurable impact on their immediate team. They do not yet coordinate across teams but demonstrate sound judgment within their domain.
Candidates own decisions involving multiple components or teams, explicitly weigh trade-offs using data, and mitigate risks. Their decisions impact multiple teams or customers, showing broader scope and responsibility.
Senior engineers lead complex decisions with ambiguous or incomplete data across multiple teams. They challenge assumptions, influence others, and quantify long-term business impact, demonstrating leadership in judgment.
At this highest level, candidates define decision-making frameworks for ambiguous, high-stakes problems affecting entire organizations. They mentor others on judgment quality and drive systemic improvements in decision processes.
Shows ability to evaluate multiple valid technical solutions involving different teams, requiring data gathering and trade-off analysis.
Demonstrates judgment in making decisions with incomplete data and planning contingencies.
Highlights intellectual humility and willingness to question initial ideas to find better solutions.
- Routine Bug Fix in Own Team - Does not show cross-team scope or decision-making between valid options; mostly execution.
- Effort Without Initiative - Staying late or working hard on assigned tasks shows effort but not judgment or ownership.