Watch the full debrief

Two voices. One question. The insider reaction you don't usually see.

Also on YouTube 5–7 min 2026

Question decoded

"Tell me about a time you had to influence a team to adopt a technical approach they were resistant to."

Competency tested

Googleyness — Influencing Without Authority

Who asks it

HC Member · HM · Peer

What they're really asking

Did their thinking change — or just the team's?

Answers compared

The answer that fails — and why

Candidate answer No hire — Googleyness — Influencing Without Authority

We were migrating a critical data pipeline to a new streaming architecture, and the engineering team wanted to stay with the existing batch system. I put together a detailed technical doc comparing latency, throughput, and operational overhead, and I presented it in their weekly sync. A few engineers were skeptical, so I set up a separate working session and walked through the trade-offs again. Ultimately the team agreed to move forward with the streaming approach. The migration shipped on schedule and reduced end-to-end latency by about forty percent.

HC evaluation

⚑ Objection treated as an obstacle to overcome, not a signal to investigate.

⚑ No evidence candidate engaged with the specific technical concern raised.

⚑ Influence framed as repeated presentation — not collaborative problem-solving.

⚑ Candidate's own position never evolved — asymmetric intellectual humility.

Prefer to hear it? Watch the video for the two-voice delivery with live reaction commentary.

Google debrief · TPM loop · HC evaluation No Hire

Google Attribute: Googleyness — Influencing Without Authority

Does not demonstrate Googleyness — Influencing Without Authority.

✗ Candidate re-presented their position — no evidence of genuine inquiry into the engineering objection.

✗ Resistance framed as a communication problem, not a substantive technical signal worth investigating.

✗ No moment where candidate's own approach or assumptions were revised based on team input.

✗ Outcome shows compliance, not alignment — team agreed; unclear if they were actually convinced.

interview101.com · Googleyness — Influencing Without Authority · Google TPM · Hiring Committee member debrief reference

→ Now here's what a strong answer actually sounds like

The answer that works — in full

Strong answer Strong hire — Googleyness — Influencing Without Authority

We were migrating a critical data pipeline to a streaming architecture. The engineering team pushed back — they were concerned that our downstream consumers weren't designed to handle out-of-order event delivery, which would introduce correctness bugs we couldn't easily test for. That was a real concern I hadn't fully worked through. I paused the decision, spent two days with two of their senior engineers mapping the consumer contracts, and we identified three downstream systems that genuinely couldn't tolerate the change without a buffering layer. I revised the proposal to stage the migration: streaming for latency-tolerant consumers first, with a resequencing buffer added before we touched the correctness-sensitive ones. The team moved forward because the plan actually addressed their objection. We shipped in two phases over eleven weeks — end-to-end latency dropped forty percent on phase one, and we had zero correctness incidents in phase two. More importantly, I came out of that with a different understanding of how to scope a migration safely.

HC evaluation

✓ Candidate restated the engineering objection with technical precision — signals genuine understanding.

✓ Explicitly paused their own position to investigate the concern — strong intellectual humility signal.

✓ Revised the technical approach based on what they learned — own thinking changed, not just the team's.

✓ Outcome attributed to alignment on substance, not repeated persuasion — this is Googleyness.

Google debrief · TPM loop · HC evaluation Strong Hire

Google Attribute: Googleyness — Influencing Without Authority

Strong signal. Strong hire.

✓ Candidate articulated the engineering objection with technical specificity — out-of-order event delivery and consumer correctness.

✓ Paused their own recommendation to investigate — demonstrated intellectual humility under program pressure.

✓ Revised the technical approach based on findings — own thinking evolved, not just the team's behavior.

✓ Alignment was earned on the merits of the revised plan — influence without authority, executed correctly.

interview101.com · Googleyness — Influencing Without Authority · Google TPM · Hiring Committee member debrief reference

Fix your answer before your loop

Run your story through these three questions

1

Can you state the engineering team's objection in their own technical terms?

If you can't, your story shows you overrode the objection — you didn't engage it.

2

Did your technical approach actually change as a result of what you learned?

If the plan is identical to your original proposal, the Hiring Committee member sees compliance, not alignment.

3

Is there a specific moment where you decided to stop and investigate before proceeding?

Without that pause, your story reads as repeated persuasion — not influencing without authority.

Get your personalized report

How do your real stories score?

Get a personalized report scored against the interview rubric Google uses for your role.

Get your Google Technical Program Manager report →

More Google Technical Program Manager debriefs