Tell Me About a Time You Influenced a Decision Without Having Direct Authority - Google STAR Walkthrough

Scenario Overview

While working as an SDE2 at Google, I noticed a persistent 0.3% webhook drop rate in the Platform team's payment notification service. This service was not my team’s responsibility, no ticket existed, and nobody had asked me to investigate. The drop rate caused delayed payment confirmations, impacting customer experience and revenue recognition. I took the initiative to analyze and fix the issue without direct authority over the Platform team.

Transcript

In this story, the candidate demonstrates key Googleyness by self-initiating a fix outside their team, explicitly stating scope boundaries, and using 'I' statements to highlight individual ownership. They quantify impact with a drop rate reduction and revenue recovery, and reflect on organizational gaps in cross-team reliability. The candidate also shows how they built trust and overcame resistance, essential for influencing without authority. These elements together create a compelling narrative aligned with Google's collaboration values.

Target: 30s

S

Strong Example

While working as an SDE2 at Google, I noticed a persistent 0.3% webhook drop rate in the Platform team's payment notification service. This caused delayed payment confirmations, impacting customer experience and revenue recognition.

"I noticed""persistent 0.3% drop rate""payment notification service""impacting customer experience"

Coaching

Keep the situation concise and focused on the problem and its business impact. Avoid deep system architecture details that lose interviewer interest.

Common Mistake

Spending 90 seconds on system architecture before reaching the problem - interviewer loses interest.

Target: 20s

T

Strong Example

This service belonged to the Platform team - not my team. No ticket existed, and nobody had asked me to investigate the webhook drop rate.

"not my team""no ticket""nobody had asked me"

Coaching

Explicitly state the scope boundary to prove ownership was self-initiated and cross-team.

Common Mistake

Jumping to investigation without stating scope boundary; ownership proof is absent.

Target: 90s

A

Strong Example

I pulled the webhook delivery logs to analyze failure patterns. I traced the failures to a race condition in the retry logic. I reproduced the issue locally to confirm the root cause. I wrote a minimal fix to serialize retries properly. I added a dead letter queue alert to catch future drops. I presented my findings and fix to the Platform team, addressing their concerns and building trust. I submitted a ready-to-merge PR and collaborated on testing and rollout.

"I pulled""I traced""I reproduced""I wrote""I added""I presented""I submitted"

Coaching

Use 'I' for every sentence to highlight individual contribution. Avoid 'we' to prevent obscuring ownership.

Common Mistake

Using 'we' language like 'we figured out the root cause' makes individual contribution invisible.

Target: 20s

R

Strong Example

The webhook drop rate dropped from 0.3% to zero. This recovery translated to approximately $8,000 in weekly recovered revenue. The Platform team adopted my dead letter queue alert pattern as a standard for all webhook templates, improving overall system reliability.

"0.3% to zero""$8,000 weekly recovered revenue""adopted my alert pattern""improving system reliability"

Coaching

Include metric delta, business impact, and second-order effect to demonstrate full impact.

Common Mistake

Ending with 'things got better and team was happy' - no quantification or lasting impact.

Target: 15s

Strong Example

"building trust""presenting data""lack of shared SLO""organizational gap""cross-team visibility"

Coaching

Provide specific, story-related insights rather than generic lessons like 'communication is important.'

Common Mistake

Generic reflection such as 'I learned communication is important' that tells nothing specific.

SDE2 Reflection

I learned how to reproduce webhook failures locally to debug effectively and the importance of clear communication when working across teams without direct authority.

Senior Reflection

The root cause was the absence of a shared webhook reliability SLO across teams, revealing organizational gaps in payment health visibility. This insight helped me understand the need for systemic cross-team metrics to improve collaboration and reliability.

How did you ensure the Platform team accepted your fix without direct authority?

Probes: Ability to influence and build trust cross-team

▼

Weak

"I did escalate it - I sent them a Slack message and they handled it."

Sending Slack = routing responsibility, not ownership; confirms handoff rather than influence.

Strong

I flagged the issue to their tech lead for visibility but brought a complete fix and data-backed analysis. I addressed their concerns patiently, which built trust and led to acceptance without formal authority.

"I brought a complete fix, not just a problem."

What challenges did you face influencing a team without authority?

Probes: Handling resistance and interpersonal skills

▼

Weak

"They were busy, so I just waited until they fixed it."

Passive approach shows lack of initiative and influence.

Strong

I encountered initial resistance as the Platform team prioritized their sprint. I overcame this by presenting clear data on business impact and proposing a low-effort fix, which helped align priorities.

"I overcame resistance by presenting data and aligning priorities."

Why did you add a dead letter queue alert?

Probes: Forward-thinking and systemic improvement

▼

Weak

"Because I thought it might help catch errors."

Vague rationale lacks business or technical justification.

Strong

I added the dead letter queue alert to provide early detection of webhook failures, preventing silent drops and enabling faster response, which improved overall system reliability.

"Early detection prevents silent failures and improves reliability."

How would you handle this differently if you had formal authority?

Probes: Self-awareness and leadership mindset

▼

Weak

"I would just tell the team to fix it immediately."

Shows lack of collaboration and respect for team autonomy.

Strong

Even with authority, I would still prioritize building trust and presenting data to ensure sustainable collaboration and ownership rather than just issuing directives.

"Building trust and data-driven influence over directives."

Weak Answer

I noticed the webhook was dropping sometimes, so I told the Platform team about it. They fixed it after a while. I think it improved the system, but I did not follow up much or check the impact closely.

What's Wrong

• No explicit scope boundary or ownership proof
• Uses 'we' or passive language implicitly
• No quantification of impact
• No demonstration of influence or overcoming resistance
• Generic and vague result

Bar Raiser ThinksSounds competent but fails on ownership and impact; leaning No Hire for this LP.

Which phrase best demonstrates ownership in a cross-team influence story?

Ownership is demonstrated by self-initiated action and presenting a solution, not by delegation or vague 'we' language.

What is the most critical element to include in the Task step for this competency?

Stating scope boundary proves self-initiated ownership and cross-team influence.

Which of the following is a disqualifying phrase in a Collaboration and Influence Without Authority story at Google?

This phrase shows lack of initiative and ownership, a key disqualifier.

Collaboration

Lead with how I built trust and aligned cross-team priorities to deliver impact.

Emphasize

Interpersonal skills, overcoming resistance, and partnership.

Downplay

Technical details of the fix.

Bias for Action

Focus on self-initiated investigation and rapid prototyping of the fix.

Emphasize

Proactive ownership and speed of execution.

Downplay

Lengthy negotiation or approval processes.

Customer Obsession

Highlight how the fix improved payment confirmation reliability and customer experience.

Emphasize

Business impact and customer benefit.

Downplay

Internal team dynamics.

SDE 1

Focus on technical steps taken to identify and fix the issue. Mention that it was not my team and no ticket existed. Keep reflection technical, e.g., learning to reproduce failures locally.

Reflection: I learned how to reproduce webhook failures locally to debug effectively and the importance of clear communication when working across teams without direct authority.

Bar Clear individual contribution and basic cross-team communication.

Keep to 2 minutes.

Senior SDE

Add organizational thinking about cross-team SLO gaps and trade-offs in proposing fixes. Articulate how I balanced technical and interpersonal challenges.

Reflection: The root cause was no shared webhook reliability SLO across teams, revealing organizational gaps in payment health visibility. This insight helped me understand the need for systemic cross-team metrics to improve collaboration and reliability.

Bar Demonstrates systemic insight and leadership in influencing without authority.

2.5-3 minutes.

Practice

1. You collaborated with a cross-functional team to implement a new feature, persuading stakeholders by presenting data-driven benefits despite lacking formal authority over them. Which LP does this primarily demonstrate?

easy

A. Bias for Action

B. Ownership

C. Deliver Results

D. Collaboration and Influence Without Authority

Solution

1. Step 1: Identify the core behavior -- influencing without formal authority.
2. Step 2: Recognize that presenting data to persuade cross-functional stakeholders aligns with Collaboration and Influence Without Authority.
3. Step 3: Differentiate from Bias for Action (focuses on speed), Deliver Results (focuses on outcomes), and Ownership (focuses on responsibility scope).

Hint: Influencing without authority = Collaboration and Influence LP

Common Mistakes:

2. I was asked by my manager to coordinate with another team to improve our product's performance. We worked together, and the team was happy with the results. I learned that communication is key and will continue to improve it in future projects. What is the PRIMARY weakness in this answer?

easy

A. Manager-assigned initiation -- no self-driven ownership

B. Weak reflection on lessons learned

C. No second-order impact described

D. Vague action steps without specifics

Solution

1. Step 1: Identify who initiated the action -- the candidate states 'I was asked by my manager,' indicating manager-assigned initiation.
2. Step 2: Recognize that this is a fatal flaw for Collaboration and Influence Without Authority, as it destroys ownership signal.
3. Step 3: Secondary issues like weak reflection or vague actions are less critical than the primary failure.

Hint: Manager asked = no ownership, fatal flaw

Common Mistakes:

3. In my project, I proactively reached out to multiple teams to align our goals and secured their buy-in without formal authority. Which LP/signal does this sentence primarily demonstrate?

medium

A. Collaboration and Influence Without Authority

B. Bias for Action

C. Customer Obsession

D. Deliver Results

Solution

1. Step 1: Identify the key behavior -- proactively securing buy-in without formal authority.
2. Step 2: This directly signals Collaboration and Influence Without Authority.
3. Step 3: Bias for Action involves speed, Customer Obsession focuses on customer needs, Deliver Results focuses on outcomes, none capture the influence without authority aspect.

Hint: Securing buy-in without authority = Collaboration and Influence

Common Mistakes:

4. What does the phrase 'My manager asked me to coordinate with the other team' signal to the interviewer?

medium

A. Demonstrates proactive leadership

B. Shows good communication skills

C. Indicates task assignment -- ownership signal destroyed

D. Reflects strong collaboration

Solution

1. Step 1: Identify who initiated the action -- the phrase shows manager-directed assignment.
2. Step 2: This destroys the ownership and initiative signal critical for Collaboration and Influence Without Authority.
3. Step 3: While it may show communication, the critical interpretation is loss of ownership.

Hint: "Manager asked" = ownership lost, task assigned

Common Mistakes:

5. In a recent project, I identified a misalignment between our team and the product team regarding priorities. I initiated discussions with key stakeholders, presented data to support our approach, and we collectively decided to adjust the roadmap. As a result, we improved delivery speed by 15% and increased customer satisfaction scores. I learned that early alignment is critical and plan to implement regular cross-team syncs. Which element is the disqualifier in this answer?

hard

A. I initiated discussions with key stakeholders

B. We collectively decided to adjust the roadmap

C. Improved delivery speed by 15% and increased customer satisfaction

D. I plan to implement regular cross-team syncs

Solution

1. Step 1: Identify who initiated the key action -- candidate states 'I initiated discussions,' showing ownership.
2. Step 2: Recognize that 'we collectively decided' subtly dilutes individual ownership and influence signal.
3. Step 3: Metrics and future plans are strong signals; the subtle disqualifier is the shared decision phrase.

Hint: "We collectively decided" dilutes ownership subtly

Common Mistakes: