Tell Me About a Time You Built Consensus Around an Unpopular but Correct Approach - Google Evaluate

Evaluate These Two Answers

"Tell me about a time you collaborated with stakeholders outside your team to solve a problem without having formal authority."

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 rubric weights.

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 cross-team project, my manager suggested I look into this since I had bandwidth. We found some integration issues causing delays, so I worked with the other team to gather requirements and proposed fixes. After implementing changes, we saw improved coordination. Although it was a team effort, I contributed by facilitating communication and tracking progress.

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

Candidate B

I noticed a recurring delay in our feature rollout that wasn’t directly in my team’s scope and no ticket had been filed. I engaged stakeholders from the product and QA teams to understand their blockers and shared data highlighting the impact on customer satisfaction. I adapted my approach based on their feedback, proposing a joint task force to address the root causes. As a result, we reduced rollout delays by 30%, improving customer experience and enabling faster revenue recognition.

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

📊

Score Comparison

Dimension

Weight

Candidate A

Candidate B

structure star

15%

12

14

ownership signal

30%

1

28

action specificity

25%

10

24

quantified impact

20%

2

19

self awareness

10%

0

10

Total

25 No Hire

95 Strong Hire

🚨

Auto-Fail Markers

manager-directed task

"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 some integration issues"

Using 'we' without clarifying individual role obscures ownership and impact, reducing ownership_signal score to 1, which is fatal.

📝

Bar Raiser Notes

Ownership weak - manager-directed; collective language obscures individual role; minimal quantification; lacks self-awareness; No Hire.

🔧

Fix-It Challenge

Ownership initiation

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

→

After"I noticed the gap during a routine review. No ticket existed. Nobody had asked me to investigate. I decided to act because..."

Demonstrates self-initiation and ownership rather than manager assignment.

Individual contribution clarity

Before"we found some integration issues"

→

After"I identified integration issues impacting timelines and took the lead to coordinate with the other team."

Clarifies personal ownership and influence rather than vague collective language.

Quantify impact

Before"we saw improved coordination"

→

After"This led to a 15% reduction in delays, improving delivery predictability and customer satisfaction."

Adds measurable impact to demonstrate effectiveness.

🎓

Coaching Notes

• At Google, Collaboration and Influence Without Authority requires clear demonstration of self-initiated ownership rather than manager-directed tasks; avoid phrases like 'my manager suggested' which signal lack of ownership.
• Use precise individual language instead of collective 'we' to highlight your unique contributions and influence.
• Quantify impact with metrics tied to business outcomes to show the value of your collaboration.
• Show adaptability by describing how you incorporated stakeholder feedback to refine your approach.
• Demonstrate self-awareness by reflecting on what you learned or how you improved your collaboration skills.

⭐

Model Answer Guidance

Strong answers start with noticing a problem outside your direct responsibility and taking initiative without prompting. They include engaging multiple stakeholders, adapting based on their input, and driving measurable impact. Use first-person singular to clarify your role and quantify results to translate technical fixes into business value. Avoid manager-directed language and vague collective terms that obscure ownership.