Describe a Time You Built Trust With a Skeptical Stakeholder - Bar Raiser Evaluate

Evaluate These Two Answers

"Tell me about a time when you earned trust from a skeptical stakeholder by addressing a problem that was not initially assigned to you."

SDE 2⏱ 3 minAmazon Bar Raiser. LP evaluated explicitly. Content scored, not delivery.

Score BOTH candidates on Ownership Signal, Action Specificity, and Quantified Impact BEFORE applying the full rubric.

If you scored Candidate A >40 total, your calibration is biased toward fluency. Bar Raisers ignore delivery and score content only.

Candidate A

During a sprint, I noticed the issue during a routine review and decided to investigate without being asked when we found a recurring issue with order processing delays. I found that the queue was overloaded during peak hours, causing delays. I deployed a fix that reduced processing delays by 25%, improving order throughput and customer satisfaction. Although it was a team effort, I ensured the problem was resolved quickly to maintain customer trust.

Fluent delivery, confident tone - most untrained evaluators score this high

Candidate B

I noticed skepticism from a key stakeholder when they questioned the accuracy of our order processing metrics, even though it wasn’t my team’s responsibility. I listened carefully to their concerns and validated the data discrepancies they pointed out. I then took initiative without any ticket or assignment, diving deep into logs and system metrics to identify that a misconfigured queue was causing intermittent delays during peak hours. I communicated my findings transparently and collaborated with the queue management team to deploy a fix that reduced delays by 30%, improving customer satisfaction scores by 12%. The stakeholder expressed appreciation for my proactive approach and the measurable impact, which strengthened our working relationship.

35-55 seconds longer - every extra second is signal-dense content

📊

Score Comparison

Dimension

Weight

Candidate A

Candidate B

structure star

15%

-

-

ownership signal

30%

-

-

action specificity

25%

-

-

quantified impact

20%

-

-

self awareness

10%

-

-

Total

40 No Hire

90 Strong Hire

AUTO-FAIL: my manager suggested I look into this since I had bandwidth - assigned task. Score 1. No Hire.

🚨

Auto-Fail Markers

manager-directed ownership

"Candidate A - my manager suggested I look into this since I had bandwidth"

Ownership requires self-initiation. Manager-assigned = execution. Score 1 on ownership_signal (weight=30) = No Hire always.

collective language hiding individual contribution

"Candidate A - we found that the queue was overloaded"

Using 'we' obscures individual ownership and initiative, weakening ownership signal. Score 1 on ownership_signal = No Hire.

📝

Bar Raiser Notes

Ownership weak - manager-directed; collective language obscures individual role; zero quantification of impact; no clear stakeholder validation; No Hire.

🔧

Fix-It Challenge

ownership_initiative

Before"my manager suggested I look into this since I had bandwidth"

→

After"I noticed the issue during a routine review and decided to investigate without being asked"

Demonstrates self-initiation and ownership rather than manager assignment

individual_contribution

Before"we found that the queue was overloaded"

→

After"I found that the queue was overloaded"

Clarifies personal ownership and initiative in identifying the root cause

quantify_impact

Before"I helped deploy a fix that improved processing times"

→

After"I deployed a fix that reduced processing delays by 25%, improving order throughput and customer satisfaction"

Adds measurable impact and business relevance to strengthen the result

🎓

Coaching Notes

• At Amazon, Earn Trust means proactively identifying and addressing issues without waiting for assignment; phrases like 'my manager suggested' signal lack of ownership and lead to automatic failure.
• Use first-person singular language to highlight your individual contribution; avoid collective 'we' that dilutes ownership signal.
• Quantify impact with metrics and connect improvements to customer or business outcomes to demonstrate the full scope of your contribution.
• Explicitly mention listening and validating stakeholder concerns to show empathy and build trust.
• Demonstrate self-awareness by acknowledging what you learned or how this experience improved your approach to cross-team collaboration.

⭐

Model Answer Guidance

A strong answer starts with noticing skepticism from a stakeholder and taking initiative without being asked. It includes listening and validating concerns, identifying root causes independently, and quantifying the impact of your fix on business metrics. Use clear first-person ownership language and connect results to customer trust or satisfaction. Avoid manager-directed phrases and collective language that obscure your role.