Tell Me About a Time You Raised a Concern About a Product's Impact on Users - Google Evaluate

Evaluate These Two Answers

"Tell me about a time you noticed a problem that wasn’t your team’s responsibility and took action to fix it without being asked."

SDE 2⏱ 3 minGoogle behavioral round. Competency holistic. LP never named explicitly.

Score BOTH answers 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

I noticed a recurring issue causing user errors during my sprint work. No ticket was filed and it wasn’t on my sprint, so nobody had assigned it. I identified the problem independently and decided to act because it impacted users. I collaborated with the team to bring a fix that reduced user errors by 30%, improving customer satisfaction and decreasing support tickets. Although the problem was initially found collectively, I took ownership of the resolution and ensured the system’s stability improved.

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

Candidate B

During a routine code review, I noticed a critical bug causing frequent user errors that wasn’t on my sprint and no ticket was filed. Nobody had asked me to investigate, but I decided to act because it impacted user experience. I independently analyzed the root cause, developed a fix, and collaborated with the QA team to deploy it. This reduced user errors by 30%, improving customer satisfaction and decreasing support tickets significantly.

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

📊

Score Comparison

Dimension

Weight

Candidate A

Candidate B

structure star

15%

13

14

ownership signal

30%

25

28

action specificity

25%

20

24

quantified impact

20%

18

19

self awareness

10%

9

13

Total

100 No Hire

98 Strong Hire

🚨

Auto-Fail Markers

Candidate A implies manager direction

"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.

Candidate A uses collective language hiding individual contribution

"we found a recurring issue"

Using 'we' hides individual ownership and contribution. Score 1 on ownership_signal (weight=30) = No Hire always.

📝

Bar Raiser Notes

Ownership weak - manager-directed; collective language; zero quantification; no clear individual initiative; No Hire.

🔧

Fix-It Challenge

Ownership initiation

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

→

After"I noticed a recurring issue causing user errors during my sprint work. No ticket was filed and it wasn’t on my sprint, so nobody had assigned it. I identified the problem independently and decided to act because it impacted users."

Shows self-initiation and ownership rather than manager assignment.

Individual contribution clarity

Before"we found a recurring issue"

→

After"I identified the problem independently"

Highlights personal ownership and responsibility.

Quantify impact

Before"improved the system’s stability"

→

After"reduced user errors by 30%, improving customer satisfaction and decreasing support tickets"

Adds measurable business impact to demonstrate effectiveness.

🎓

Coaching Notes

• At Google, Doing the Right Thing means proactively identifying issues beyond your immediate scope without waiting for direction; ownership is self-initiated, not manager-assigned.
• Avoid collective language like 'we found' that obscures your individual contribution; clearly state what you personally noticed and did.
• Quantify impact with metrics and explain the business or user benefit to demonstrate the significance of your actions.
• Demonstrate self-awareness by reflecting on what you learned or how this influenced your future approach.
• Google values candidates who act autonomously and prioritize user experience even when it’s not part of their sprint or assigned tasks.

⭐

Model Answer Guidance

A strong answer starts with 'I noticed' to show self-initiation, explains that 'no ticket was filed' and 'wasn't on my sprint' to highlight the problem was outside assigned work, then details 'I decided to act' and 'I brought a fix' with specific actions taken, and concludes with quantified impact like 'reduced user errors by 30%' plus business translation such as improved customer satisfaction or reduced support load.