Amazon Leadership PrinciplesSignal: "I noticed" -> "I decided to act" -> "I fixed root cause" -> "Reduced customer pain by X%"

Describe a Time You Advocated for the Customer When Others Disagreed - Amazon LP Competency

Self-initiated customer advocacy beyond assigned scope

Choose your preparation mode3 modes available

Competency STAR Evaluate

📌

Definition

Customer Obsession means relentlessly advocating for the customer’s needs even when it requires going beyond your assigned role or challenging peers. The core test is whether you prioritized the customer’s experience over convenience or internal politics.

⚡

Core Signal

Did the candidate self-initiate action to improve the customer experience despite disagreement or lack of direct responsibility?

🏢

Company Framing

Amazon wants owners who fix root causes impacting customers, not hired guns who patch symptoms or wait for instructions.

🚫

What It Is NOT

Completing assigned tasks well - that is execution, not ownership
Fixing bugs only in your own codebase without considering customer impact
Waiting for a manager or team to assign the problem before acting
Escalating issues without proposing or driving a solution
Focusing on internal metrics without linking to customer outcomes

✅

Candidate clearly states they noticed a customer-impacting issue outside their team or sprint.

"I noticed""wasn't on my sprint""nobody had flagged it""no ticket was filed""customers were affected silently"

Shows proactive identification of customer pain points without being asked.

Common Miss My manager mentioned it might be worth looking into

✅

Candidate describes deciding to act despite no formal ownership or sprint allocation.

"I decided to act""even though it wasn't my team""no one else was addressing it""I took initiative""I prioritized customer impact over process"

Demonstrates ownership and prioritization of customer needs over internal boundaries.

Common Miss I waited for the team to assign the bug

✅

Candidate explains how they gathered data or customer feedback to validate the problem.

"I analyzed logs""I reviewed customer complaints""I dug into metrics""I confirmed the impact quantitatively""I spoke with affected customers"

Shows Dive Deep behavior and data-driven customer obsession.

Common Miss I heard from a colleague that customers were unhappy

✅

Candidate details how they proposed or implemented a fix that addressed root cause, not just symptoms.

"I fixed the root cause""I proposed a permanent solution""I automated the detection""I prevented recurrence""I improved the customer experience end-to-end"

Indicates long-term thinking and Invent and Simplify aligned with customer obsession.

Common Miss I patched the immediate bug and moved on

✅

Candidate quantifies impact on customers or business metrics.

"reduced customer complaints by 30%""improved uptime by 2 hours per week""saved $8K per week in lost revenue""increased customer satisfaction scores""prevented potential data loss for thousands"

Quantification links actions to real customer and business outcomes.

Common Miss The fix was appreciated by the team

✅

Candidate acknowledges challenges or disagreements and how they persuaded others to prioritize the customer.

"others disagreed initially""I convinced stakeholders""I escalated with data""I aligned cross-functional teams""I persisted despite resistance"

Shows leadership and persistence in customer advocacy.

Common Miss I just did it quietly without telling anyone

💡

Depth Tip

Action section = 70% of your answer. Situation+Task combined = 50 seconds max. Focus on what YOU did, not the team.

❌ 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-Only Scope

"This was a bug only in my team's codebase and I fixed it quickly"

Customer Obsession at Amazon expects cross-team or customer-facing scope, not just internal bug fixes.

DetectionCheck if the problem impacted customers beyond your immediate team or was visible externally.

Fix"I identified a customer-impacting issue affecting multiple teams and drove cross-team collaboration to fix it."

❌ Escalation Without Ownership

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

Escalating and waiting = routing not ownership. This confirms you handed it off without driving a solution.

DetectionDid the candidate bring a solution or just report the problem?

Fix"I flagged it for visibility but brought a ready-to-merge fix to minimize customer impact."

❌ Effort Without Impact

"I stayed late to help fix the issue before the deadline"

Effort alone is not ownership. Ownership requires self-initiated action with measurable customer impact.

DetectionIs the story about effort or about improving customer experience proactively?

Fix"I identified a customer pain point no one was addressing and implemented a fix that reduced complaints by 20%."

❌ Vague or Generic Claims

"I took ownership and made sure it was done"

Generic claims without specifics do not prove customer obsession or ownership.

DetectionLook for concrete examples, data, and specific actions.

Fix"I noticed X was causing Y for customers, so I did A, B, and C resulting in Z% improvement."

🚩 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.'

🚩 We Did It Language

"We fixed the issue quickly"

Hides individual contribution, making it impossible to assess candidate ownership.

FixUse 'I' statements: 'I fixed the issue by...'

🚩 Overuse of Jargon or Buzzwords

"I leveraged synergies to optimize customer experience"

Sounds vague and rehearsed, obscuring real actions and impact.

FixUse clear, concrete language describing what you did and why.

🚩 Lack of Quantification

"The fix improved things significantly"

No measurable impact makes it hard to evaluate customer obsession.

FixProvide specific metrics: 'Reduced customer complaints by 25% within two weeks.'

🚩 Blaming Others

"The other team was slow to respond so I couldn't fix it sooner"

Shows lack of ownership and shifts responsibility away from candidate.

FixFocus on what you did to overcome obstacles, not on blaming.

🎯

Direct Triggers

Describe a time you advocated for the customer when others disagreed.
Tell me about a situation where you went beyond your role to improve customer experience.
Give an example of when you identified a customer problem no one else was addressing.
How have you handled a situation where your team did not prioritize a customer issue?

🔍

Indirect Triggers

Tell me about a time you took ownership of a problem outside your sprint.
Describe a situation where you had to convince others to change their approach.
Give an example of when you improved a process that impacted customers.
Tell me about a time you had to dive deep to solve a complex issue.

👁

How to Recognize

Keywords: without being asked, beyond your role, proactively, customer impact, self-initiated, no ticket filed, cross-team collaboration.

⚠️

Do Not Confuse With

OwnershipOwnership is about taking responsibility for any problem, but Customer Obsession specifically focuses on prioritizing the customer’s needs above all.

Deliver ResultsDeliver Results is hitting a committed goal under pressure, usually manager-set; Customer Obsession is self-initiating to improve customer experience even without assigned goals.

Bias for ActionBias for Action is about speed and decisiveness; Customer Obsession is about prioritizing customer impact even if it slows internal processes.

❓

How did you convince others who initially disagreed with your approach?

Probes: Candidate’s ability to influence and persist in customer advocacy despite resistance.

❌ Weak

I just told them it was important and hoped they would agree.

Vague and passive; shows lack of concrete persuasion or leadership.

✅ Strong

I gathered customer data and shared specific impact metrics, then proposed a phased plan addressing their concerns, which helped align stakeholders.

""I brought data and a clear plan to persuade skeptics to prioritize the customer.""

❓

What was the measurable impact of your action on customers or the business?

Probes: Quantification of customer obsession and business value delivered.

❌ Weak

The team appreciated the fix and things got better.

No metrics or concrete outcomes; weak evidence of impact.

✅ Strong

My fix reduced customer complaints by 40% within one month and prevented $10K weekly revenue loss.

""I quantified impact to show how my action improved customer experience and business metrics.""

❓

What challenges did you face and how did you overcome them?

Probes: Candidate’s resilience and problem-solving in customer advocacy.

❌ Weak

There were some delays but eventually it got done.

Minimizes obstacles and lacks ownership of overcoming them.

✅ Strong

I faced resistance due to sprint priorities, so I negotiated scope trade-offs and demonstrated cost of inaction to get buy-in.

""I overcame resistance by negotiating trade-offs and highlighting customer cost of inaction.""

❓

If you had to do it again, what would you do differently?

Probes: Self-awareness and continuous improvement in customer obsession.

❌ Weak

Nothing, it went well.

Lacks reflection and growth mindset.

✅ Strong

I would engage stakeholders earlier to reduce delays and automate monitoring to catch issues sooner.

""I reflect on improving stakeholder engagement and proactive monitoring next time.""

Google

Focus on the User and All Else Will Follow

Google emphasizes rapid iteration and user feedback loops to obsess over user experience, often prioritizing speed and experimentation.

Signal: Candidate describes launching a quick prototype to validate user impact before scaling.

Example QTell me about a time you improved a product feature based on user feedback.

What Elevates

Explain how you balanced speed and quality by launching a minimal viable change, gathered user data quickly, and iterated to maximize user satisfaction while minimizing risk. Detail how this approach aligns with Google's emphasis on rapid experimentation and user-centric design.