Can you get PIPed twice at Google?

Multiple verified Googlers on Team Blind report that you cannot receive a second formal PIP at Google. If your performance declines again after surviving a PIP, the outcome is automatic termination without another improvement period. This means surviving a PIP does not reset the clock to a clean slate. The scrutiny continues, and any regression is treated as final.

Does being on a PIP at Google affect your ability to get hired at other companies?

Standard background checks verify employment dates and title only. Google does not disclose PIP details to future employers. However, some companies are now asking candidates directly whether they have been on a PIP, so be prepared for the question. The bigger risk is waiting too long to start your search. Beginning the job search on day one gives you a pipeline regardless of how the PIP ends.

Can you get unemployment benefits if fired from Google after a PIP?

Yes. In most US states, termination for performance reasons after a PIP qualifies you for unemployment benefits. You are also eligible for COBRA health insurance continuation. This is one of the primary reasons not to resign during a PIP: resignation eliminates unemployment eligibility and removes your leverage to negotiate any remaining severance or benefits.

What happens to your Google RSUs if you are terminated during a PIP?

Any RSUs that have already vested are yours. Unvested RSUs are forfeited upon termination. If you are close to a vesting date, the timing of your separation matters. When evaluating whether to take severance at the PIP kickoff or fight the PIP, factor in how much equity vests during the PIP period. Deciding whether to fight or take the severance covers the full financial calculation.

Google

PIP

Performance Improvement Plan

Big Tech

Career

May 6, 202610 min read

How to Survive a Google PIP: What the Process Actually Looks Like

Tamba Monrose

CareerClimb

Facing a Google PIP?

Get a week-by-week plan built for Google's actual process.

You got the document. Formal Performance Improvement Plan, your name at the top, specific goals with a deadline, HR cc'd. Maybe severance was offered in the same meeting. You're trying to figure out whether passing this thing is actually possible, or whether the decision has already been made.

The answer depends on details most people don't know to look for. Google changed how it handles underperformance in 2023, and the current process works differently than what you'll find in most online advice.

How Google's PIP process changed in 2023

Google used to run a two-stage system. Before a formal PIP, engineers went through a Support Check-In (SCI), an informal but documented period where your manager flagged concerns and gave you time to course-correct. The SCI was a genuine warning shot. Many engineers who improved during SCI never saw a formal PIP.

Google discontinued the SCI program in August 2023.

The pipeline now runs through GRAD's (Google Reviews and Development) regular feedback mechanisms: semi-annual reviews and monthly check-ins. If your manager identifies a sustained performance issue, the next formal step is the PIP itself. There is no intermediate stage with its own name and process.

The result: you get less warning before a PIP than you used to. The monthly check-in where your manager mentioned concerns about your impact might have felt routine. Then a few weeks later, HR is on the call and there's a document.

If you got a Not Enough Impact (NE) rating in your most recent GRAD cycle, that's the primary trigger. Persistent Moderate Impact (MI) ratings across multiple cycles can also move you into the formal process. CNBC reported in late 2022 that Google tripled the percentage of employees expected to land in the lowest rating categories when it rolled out GRAD, from roughly 2% to 6%.

The week-by-week timeline

Google PIPs usually run 30 to 60 days, shorter than the industry standard of 60 to 90 days. The exact duration varies by team and manager, but the structure follows a consistent pattern.

Week 1: The kickoff. You sit down with your manager and an HR representative. You receive the PIP document, which lists specific performance deficiencies and the goals you need to meet. In many cases, Google presents a severance package in this same meeting. The message: take the package and leave clean, or attempt the PIP knowing that failure means separation with nothing.

The goals in your PIP document are the only things that matter for the next month. Read them multiple times. Identify which goals are measurable ("ship feature X by date Y," "achieve 80% of quarterly OKRs") and which are evaluative ("demonstrate improved strategic judgment"). Measurable goals are survivable. Evaluative goals are harder to prove you've met, because the person evaluating is the same person who put you on the PIP.

Weeks 2 through 4: Weekly check-ins. You meet with your manager weekly, sometimes with HR present. Each meeting reviews your progress against the stated goals. Your manager documents notes after every session. You should be documenting too.

These check-ins are not coaching sessions. They are evaluation sessions with a paper trail. Your manager is building a record, and so should you. After every check-in, send a follow-up email summarizing what was discussed, what progress was acknowledged, and what you plan to deliver next. Copy HR.

Final week: The evaluation. Your manager and HR assess whether you met the PIP goals. Three outcomes are possible: the PIP is lifted (you stay), the PIP is extended (rare, and usually just delays the same ending), or your employment ends.

What Google actually measures during a PIP

Under GRAD, PIP goals tie back to your job level expectations and your team's OKRs. The specifics depend on why you were put on the PIP, but the categories are consistent.

Impact metrics. GRAD is built around impact. If your NE rating stemmed from low output, your PIP goals will likely include concrete deliverables: ship a specific project, close a set of bugs, deliver a design document by a deadline. These are the most survivable PIP goals because you can point to artifacts that prove completion.

Behavioral expectations. Some PIPs include goals around collaboration, communication, or what Google calls "Googleyness." These are harder to satisfy with proof. "Demonstrate improved cross-functional collaboration" is a goal your manager can grade subjectively. If your PIP is heavy on behavioral goals and light on measurable deliverables, that's a signal about intent.

Peer feedback. In some cases, PIP evaluations incorporate feedback from teammates or cross-functional partners. If you've been told peers will weigh in, treat every interaction during the PIP period as data they'll collect. This is not the time to be heads-down and invisible.

When survival is realistic

Be honest about your situation before committing to fight. Surviving a Google PIP is possible. It is not common at the formal PIP stage.

A Fishbowl poll found 41% of employees placed on PIPs across all companies and industries passed. Google-specific numbers are harder to pin down, but verified Googlers on Team Blind describe the formal PIP as ending in separation for most people. The SCI stage (when it existed) had better odds. The formal PIP is different.

Survival is more realistic when:

Your PIP goals are specific and measurable, not evaluative
The performance issue is recent and bounded (a single bad quarter, a project that went sideways) rather than a multi-cycle pattern of NE ratings
Your manager still engages with you as a person, not just as a process to complete
No severance was offered in the kickoff meeting
You have a track record of strong performance before the period that triggered the PIP

Survival is unlikely when:

Severance was offered alongside the PIP document
The goals are vague or evaluative ("demonstrate improved judgment")
HR is present and documenting every check-in, not just the kickoff
Your manager has already redistributed your projects to other engineers
You received NE ratings in multiple consecutive cycles

If most of the second list applies to you, the PIP is paperwork for a decision that's already been made. That doesn't mean you should quit. It means you should be planning your exit on your own terms while going through the motions.

The survival playbook: what to do if you fight

You've read the signals and decided the PIP is worth attempting. The engineers who have passed Google PIPs describe a common set of moves.

Treat the PIP document as a legal contract

Every word in that document matters. If it says "complete code reviews within 48 hours with a 90% rate," then 89% is a failure and 91% is a pass. Do not interpret goals loosely. Do not assume your manager will give you credit for "close enough." Meet the letter of every requirement and document that you met it.

Build a parallel paper trail

Your manager and HR are documenting your performance. You need to document it too.

After every weekly check-in, send a summary email within 24 hours. Include what was discussed, what progress was acknowledged, and your plan for the next week
Save copies of everything you ship: code reviews, design documents, launch announcements, metrics dashboards
If a teammate gives you positive feedback, ask them to put it in writing (email or Slack message you can reference)
Keep a personal log with dates, deliverables, and any verbal feedback from your manager

This documentation serves two purposes. If the PIP is genuine, it proves you met the requirements. If the PIP is a managed exit, it protects you legally if you ever need to demonstrate the process was unfair.

Over-deliver on the measurable goals

You cannot control how your manager evaluates subjective criteria. You can control whether you hit every measurable target. If the PIP says "ship three features," ship four. If it says "reduce bug count by 20%," reduce it by 30%. Over-delivery on concrete metrics makes it harder for anyone to argue you failed.

Do not go silent

Engineers under PIP stress often retreat. They put their heads down, stop attending optional meetings, and minimize interaction with their team. This is the wrong move. Your manager and peers need to see you engaged, visible, and contributing. Attend team meetings. Participate in code reviews. Ask clarifying questions in channels where your contributions are visible.

Going silent looks like someone who has given up. Even if you're exhausted, maintain presence.

Get outside support early

You need people in your corner who are not inside Google.

An employment attorney. If anything about the timing feels off (PIP arrived after an HR complaint, after medical leave, after a team transfer), consult a lawyer before you sign anything. Many offer free initial consultations. District Employment Law has written specifically about PIP legal options.
A mentor or former colleague. Someone who can review your PIP goals objectively and tell you whether they look achievable or designed to fail
Your own support system. Fighting a PIP while maintaining performance output is psychologically corrosive. You need people outside work who know what you're going through

What not to do

Do not resign. This is the single most common piece of advice from engineers who have been through Google PIPs, and it applies whether you're fighting or leaving. Resignation eliminates your eligibility for unemployment benefits in most US states. It removes your leverage to negotiate severance. It lets Google avoid the documentation burden of a termination. If they want you gone, make them complete the process.

Do not tell colleagues you're on a PIP. The instinct to confide is strong. Resist it during the PIP period. Colleagues talk. Managers hear things. The information can change how people interact with you and can undermine your position. Confide in people outside the company.

Do not send emotional emails. Every written communication during a PIP is part of the record. If you're frustrated after a check-in, write the email you want to send. Then delete it and write the professional version. Send that one.

Do not skip the job search. Even if you're fully committed to fighting the PIP, start interviewing externally on day one. The downside of searching while fighting is almost zero. The downside of not searching and then failing the PIP is enormous. How to job search while on a PIP covers the logistics.

The aftermath: what happens if you survive

Some engineers do pass their Google PIP. The aftermath is often different from what they expected.

Your manager documents that you met the goals. The PIP is lifted. You stay employed. That part is real.

But you carry the marks. Your relationship with your manager will not go back to what it was before the PIP. Some managers move on. Others keep scrutinizing your work more closely than your peers'. That trust deficit can persist even when the formal process is over.

Your promotion timeline resets, even if no policy says so. Getting promoted within 12 months of surviving a PIP is rare. The PIP becomes part of your internal narrative, and the engineers who evaluate your promotion case in calibration may know about it.

Many engineers who survive a PIP leave Google within a year anyway. Not because they were pushed, but because going through it made clear that the environment, the team, or the role was wrong. Survival is worth pursuing if you want to stay and believe the situation was fixable. It is not worth pursuing just to prove a point.

The honest assessment

Google's PIP process got more abrupt after the SCI program ended in 2023. Engineers now move from regular feedback channels to a formal PIP with less buffer. The process runs 30 to 60 days, shorter than most companies. Severance is often offered at the start.

Most formal Google PIPs end in separation. The engineers who survive tend to have specific, measurable goals, a recent and bounded performance dip rather than a multi-cycle pattern, and a manager who hasn't already checked out. If that describes your situation, the playbook above gives you the best odds.

If it doesn't describe your situation, surviving the PIP may not be the right goal. Deciding whether to fight or take severance is a different question, and the answer depends on your specific signals. Either way, do not resign. Document everything. And start your external search today, not after the PIP period ends.

CareerClimb helps engineers facing PIPs build a clear response plan based on their actual situation. The AI career coach walks you through your options, helps you document your case, and gives you a framework for deciding what to do next. Download CareerClimb for free.