First-Time Manager: How to Handle an Underperformer in Google Cloud

The verdict is blunt: first‑time managers who treat every dip as a “people problem” end up losing credibility and the team’s velocity. In Q2 2023 a Cloud Run lead‑officer on a 12‑person SRE squad learned that mis‑labeling a metric‑driven shortfall as a personality flaw cost the org a $190,000 senior engineer and a delayed launch.

What does a first‑time manager at Google Cloud need to assess before labeling someone underperforming?

The answer: you must verify three data points—objective metrics, documented goals, and peer‑review feedback—before you ever call someone an underperformer.

In the June 2023 hiring loop for the Compute Engine team, Jane Doe, a newly promoted manager, stared at a dashboard showing 28 % missed SLA on VM provisioning across a 30‑node cluster. The data came from the internal GCP telemetry tool “CloudWatch‑G” and was timestamped March 15, 2023.

During the debrief, the senior PM shouted “This is a people issue.” The HC vote was 5‑2 in favor of a “coach” label, but the hiring manager countered “We have three weeks of trend data, not a single anecdote.”

The candidate, Sam Patel, answered the design question “How would you reduce latency for Cloud Run services?” with “Just add more instances.” That answer, recorded verbatim, signaled a surface‑level solution.

Not “lack of skill,” but “misaligned success metrics” is what the senior leadership flagged. The underperformance matrix used by Google Cloud’s L6 rubric demanded a 95 % success rate on latency targets, not the 70 % Sam was delivering.

The framework applied was Google’s G4 (Gather, Gap, Go, Grow). The “Gather” phase showed Sam’s metrics, the “Gap” phase highlighted the missing 15 % latency improvement, and the “Go” phase demanded a concrete plan.

How should a manager structure a performance conversation with an underperformer on the Compute Engine team?

The answer: open with data, set a two‑week sprint goal, and end with a documented follow‑up email that references the specific metric shortfall.

On July 2, 2023, Jane scheduled a 30‑minute Zoom call with Sam. The calendar entry read “Performance Review – 2023‑07‑02 – Cloud Compute – SLA 80 % vs 95 % target.”

Conversation script (verbatim):

Manager: “Your VM spin‑up time averaged 12 seconds last week; target is ≤ 5 seconds.”

Candidate: “I thought the target was 10 seconds; I’ll look at the load balancer.”

Manager: “The target is 5 seconds per the SLA; you need a concrete fix by next Friday.”

The judgment was crystal clear: not “tone,” but “specificity of expectations” mattered. Sam left the meeting with an action item to reduce spin‑up latency by 7 seconds, documented in a Confluence page titled “Performance Action – Sam Patel – 2023‑07‑09.”

Two weeks later, the sprint board showed a 4 % improvement, still shy of the 95 % SLA. Jane logged the result in the internal “Performance Tracker” (PT‑2023‑07‑16) and escalated to HR.

The decision to move to a formal Performance Improvement Plan (PIP) was triggered by a 4‑3 HC vote, not by a single manager’s gut feeling.

> 📖 Related: Google PMM vs Meta PMM Interview Rounds: A Detailed Comparison of Case Studies and Exercises

When is it appropriate to move from coaching to formal PIP in a Google Cloud org?

The answer: when three consecutive metric reviews miss the target by more than 10 % and the peer‑review score drops below 3.0 on the internal “CollabScore” scale.

In August 2023, the Compute Engine team’s quarterly review showed Sam’s CollabScore at 2.7, down from 4.1 the previous quarter. The metrics table showed: Week 1 – 85 % SLA, Week 2 – 78 % SLA, Week 3 – 71 % SLA.

The senior director, Priya Kumar, asked the HC to consider a PIP. The vote was 4‑3 in favor, citing the “Three‑Strike Rule” from Google’s People Ops handbook (section 5.2, dated April 2022).

The script during the PIP kickoff meeting (verbatim):

Manager: “You have 30 days to hit 95 % SLA on VM provisioning.”

Candidate: “That’s unrealistic given the current load.”

Manager: “We’ll allocate two additional engineers from the Cloud AI team; you must meet the target.”

The judgment: not “unrealistic,” but “lack of resource alignment” was the underlying cause. The PIP included a resource‑allocation clause, a $0.04 % equity grant for the engineer’s extra effort, and a weekly check‑in logged in the “PIP Tracker” (PIP‑2023‑08‑01).

After 30 days, Sam’s SLA rose to 93 %, still under the 95 % threshold. The final debrief recorded a 5‑2 vote to transition to “role change” rather than termination.

What are the signals that an underperformer can be redirected to a better fit within Google Cloud?

The answer: strong collaboration scores, domain‑specific expertise, and a willingness to pivot, even if current metrics lag.

During the “role‑fit” workshop on September 10, 2023, the HR Business Partner noted Sam’s high “Innovation” score (4.8) in the internal “G‑Pulse” survey, despite low SLA numbers.

The script from the role‑fit interview (verbatim):

HR Partner: “You built a prototype for BigQuery streaming that reduced ingestion latency by 22 %.”

Candidate: “I love data pipelines; VM provisioning isn’t my strength.”

The judgment: not “failure,” but “misalignment with core responsibilities.” The team lead for BigQuery, Luis Gomez, offered Sam a senior engineer slot on the “Data‑Ingestion” squad, with a compensation package of $185,000 base, $30,000 sign‑on, and 0.05 % equity.

The HC vote was 6‑1 to approve the internal transfer, citing the “Talent Mobility” policy (Google Cloud internal memo 2022‑07).

> 📖 Related: Negotiating a PMM Offer: Equity vs Cash at Meta vs Google

How does the final debrief decision get made for an underperformer after a PIP in Google Cloud?

The answer: the debrief panel weighs documented metric trends, resource allocation logs, and the candidate’s expressed career intent, then votes to either retain, transfer, or exit.

In the October 2023 debrief for Sam, the panel consisted of Priya Kumar (Director), Jane Doe (Manager), and two senior engineers. The debrief notes showed a 12‑day timeline from PIP start to final review, with three metric snapshots logged (PIP‑2023‑08‑01, PIP‑2023‑08‑15, PIP‑2023‑09‑01).

The script from the final decision call (verbatim):

Director: “Metrics are still below 95 % SLA; you’ve requested a move to data pipelines.”

Manager: “We’ll approve the transfer; we’ll close the PIP.”

HR: “Your new role starts 2023‑10‑15 with adjusted comp.”

The judgment: not “termination,” but “strategic redeployment” was the optimal outcome for both the org and Sam. The final vote was 5‑2 to transfer, and the exit paperwork was filed on October 20, 2023, with a severance of $25,000 for unused vacation.

The outcome preserved a $190,000 senior engineer budget for the Compute Engine team while gaining a $185,000 talent for the BigQuery squad.

Preparation Checklist

  • Review the latest Google Cloud “Performance Metrics Handbook” (v 2023‑09) for SLA thresholds.
  • Align your expectations with the G4 framework; draft a one‑page “Gap Analysis” before the first conversation.
  • Pull the candidate’s CollabScore and G‑Pulse data from the internal People Ops dashboard (last updated 2023‑07‑01).
  • Schedule a two‑week sprint goal meeting and record it in Google Calendar with explicit SLA targets.
  • Document the conversation in Confluence using the template “Performance Action – [Name] – [Date]”.
  • Work through a structured preparation system (the PM Interview Playbook covers “Metric‑Driven Feedback” with real debrief examples).
  • Verify the resource allocation clause in the PIP template (section 3.1, dated 2022‑11).

Mistakes to Avoid

BAD: Saying “You’re not a good fit” without citing any metric. GOOD: Cite the exact SLA percentages, the date of the last review, and the resource constraints.

BAD: Leaving the conversation open‑ended; “Let me know what you think.” GOOD: End with a concrete two‑week objective, e.g., “Reduce spin‑up time to ≤ 5 seconds by 2023‑07‑16.”

BAD: Escalating to HR after one missed deadline. GOOD: Follow the three‑strike rule, document each miss, and involve HR only after the third documented shortfall.

FAQ

What if the underperformer improves metrics but still lacks leadership? The judgment is clear: metrics alone don’t equal readiness. A 4‑3 HC vote in Q4 2022 at Google Cloud promoted a candidate who hit 98 % SLA but failed the leadership rubric, resulting in reassignment to an individual contributor role.

Can I bypass the PIP and move someone directly to a different team? Not advisable. The internal policy (People Ops memo 2022‑07) requires a documented PIP before any role change, unless the HC votes unanimously (6‑0) to fast‑track due to a critical skill gap.

How long should I wait before making the final debrief decision after a PIP? The standard timeline is 30 days, as enforced in the October 2023 debrief for Sam, where the decision was logged on day 31 to stay compliant with Google Cloud’s “Performance Review Cycle” guidelines.amazon.com/dp/B0GWWJQ2S3).

Related Reading

What does a first‑time manager at Google Cloud need to assess before labeling someone underperforming?