Stay or Leave: Manager Admitted I am on PIP because quota
teamblind.com
teamblind.com
That being said, these situations suck. Ask me how I know.
1) Is the quota for a number of people who need to be put on PIPs, or a number of people who need to be fired?
If it's the latter, the employee is effectively already fired; they're required to fire N people, and they're going to find a way to claim employee failed the PIP, no matter what. Obviously the employee will not be able to answer this question with any amount of certainty.
2) Are the goals that need to be achieved to pass the PIP unambiguous? That is, is it objectively obvious that the goal has been passed or failed?
If any of the goals are ambiguous, management could use that ambiguity to claim some goals haven't been achieved when the employee believes they have been, and use that to justify firing them.
Of course, the manager could also just by lying about why the employee is on a PIP. Maybe they do actually have a performance issue, but the manager is too much of a wuss to flat-out tell the employee this. I agree that it's suggestive that the manager seems to be setting the PIP's goals in such a way that they're relatively easy to achieve, but that might not be the whole story.
Either way, a company that has periodic PIP (or firing) quotas isn't a company I'd want to work at, so I'd start looking for a new job even if I'd still end up being retained after the PIP is over. Ideally I'd have a start date at a new place after the PIP is done, so I could explicitly give that reason for quitting, even though my job there would be (at least for the time being) secure.
A.E Housman had something to say about the belief that the world is generally fair: "He [Joe Public] believes that the text of ancient authors is generally sound, not because he has acquainted himself with the elements of the problem, but because he would feel uncomfortable if he did not believe it; just as he believes, on the same cogent evidence, that he is a fine fellow, and that he will rise again from the dead. "
But in this case it's not even a real PIP.
I'm never been PIP'd myself, but I've seen it happen to many -- and it's never resulted in anything good, nor has it ever seemed as if the purpose was actually to improve anyone's performance. It's usually seems like just a thing that has to be done before you can fire them. Even when the PIP'd employee isn't fired, the PIP remains a scarlet letter on them for the rest of their time at that company.
I'm glad there are companies where this isn't the case! I wonder how common those are.
I think most people put on PIPs think the same: I'm going to be fired anyway, so why bother doing anything about this?
That said, I am absolutely convinced that the reason for the PIP is that they were trying to get rid of a number of (expensive) senior engineers.
In one of the cases the person who got pip'd got promoted to Staff Eng from Senior within a year, it was mostly about his attitude, not about his technical skills, and he changed completely. I think that person was just not self aware how people didn't enjoy working with him, even if the manager gave feedback, he thought it was funny or something like that.
It was a real "Am I the bad one" moment when the PIP process started. Another one was about how they always went too deep into rabbit holes and never delivered any value, to change the way they approach problems, etc.
I feel feedback from managers is extra challenging in remote environments OR in places where a person has been for too long and is too used to the status quo, and PIPs can help there.
I count myself luck that I haven't worked in companies where PIPs were used as a tool to layoff or fire people, but I also take some of those reports with a grain of salt.
Pretty much this at least when I've used it. What was surprising was I had an employee do a complete 180 when put on a PIP. They had been given lots of feedback, clear guidance, and even a direct, "we've talked about this, and it's putting your job in jeopardy, if this continues you will be fired" conversation prior to the PIP. I honestly expected to fire them and the end and thought I was just crossing my Ts and dotting my 'i's with HR, but to my shock the PIP seemed to shake something loose that nothing else did. All I can think is that putting a clear deadline on it finally got through. When I left a couple years later we were starting to talk about promoting them. Don't know if it ever happened.
I can't assert how other companies and managers use them, but the only time I've ever deployed PIPs is as a "we've talked about this, and this is now your last chance" with the honest intent (even if I'm not expecting it) that if the issues are resolved they are put behind us.
I will see that as someone who mentors a number of engineers, some of the PIPs I see are ridiculous. Here's a verbatim quote from the PIP of an engineer at a decacorn: "Employee must not receive more than 3 pieces of corrective feedback on any single PR". That's _basically_ constructive dismissal.
I quit anyway, but that's a whole other story.
I don’t think him being chosen to receive the boot necessarily means his performance was poor. I mean, maybe it was, but from the outside I wouldn’t jump to that conclusion.
Perhaps, but the difference between the bottom of the pack and the top of the pack might be negligible. We don't know.
> My advice would be to be humble enough to admit that the performance can be improved and take ownership of that fact
Sure, that's fine, but I still think that the odds are he'd be better off if he quits as well.
The most frequent gripe I've seen were people late at a few meetings being marked as impacting the team. Like, sure that's not great and not polite, but would that be on par with generating 20k errors in production that need to be fixed a whole friday ?
Except, OP said that the boss chose him because he had the least amount of tenure (<1 year for OP versus > 3 years for everyone else).
My best guess is this person is underperforming and the manager is too focused on head count preservation to notice an underperformance issue. To them, their manager is forcing them in to this but not for the reasons they are sharing.
Either way, that's a bad manager, likely should be making plans to leave.
I’m shocked OP was told the truth.
The people that say "My hand was forced" are lying to you and lying to themselves and are frankly poor managers.
My alternative theory and one that is more common and I'm not sure why it didn't come to me first is OPs manager is conflict avoidant and wants to always be the "good guy". Firing people is no fun. PIPs are no fun. It's the cowards way out to pass the buck.
To put it another way, if OP asked their skip why they are in a PIP, what do you think their answer would be? It'd likely be something like "Go read the PIP document yourself" because they have confidence they have documented underperformance in the PIP tool.
You get onto a PIP because some external-to-the-team person, maybe a TPM, maybe a higher up manager, complained about you. They don't always explain why to your manager, in fact, it's probably generally a smart move for them NOT to say why (frankly, some people complain to your manager because you came to the office with untied shoelaces).
When that happens (maybe your manager gives you two or three "strikes"), your manager comes to you and writes a PIP. What that PIP will NEVER say is "make X not complain about you anymore". It will say "write more code", "take ownership of bugs", "take more feedback into account", because, as you point out, HR would freak if it said "do what X says". Plus, of course, if at all possible your manager will try to not have you work with that complaining person anymore. Which would make such a PIP redundant/impossible.
PIPs are always because someone asked for them. Maybe (hopefully) indirectly, and not always (one hopes never, but ...) for the reason "quota", but essentially always because someone asked for them. PIPs never say that, so they never give the real reason. The point is indeed to scare you into being "more cooperative".
HR kind-of tells the truth: the point of a PIP is to make you a better employee. It really is. All else equal, they want it to go away as much as you do. But if it doesn't go away, the point of a PIP is to fire you, safely, without getting sued afterwards, without HR having to do any work at all.
This kind of bullshit and “sorry nothing I can do” response from a line manager is unacceptable to just be ok with - especially when it’s purely driven by rent seeking.
For engineers, the only way to survive is play the game but stop caring about the company because they don't care about you.
No? How do you define the performance of a doctor? Nurse? Teacher? Developer? Tech Support?
Most of these roles have metrics that might seem like easy and foolproof ways to measure performance, but ask anyone that has actually worked any of these professions for more than 2 min, and you'll have endless tails of management fucking everything up by chasing a dumb number.
If your job matters in the slightest, it's not that rare for performance to be wildly elusive to measure.
It's interesting that you say that because it's exactly what I realized from being put on a PIP and it was a large part of why, after being removed from the PIP, I quit a few months later.
Assuming it works pretty consistently across the industry, a PIP basically means you are slated to be fired.
Circumstances may change, and by all means pay attention to and try to improve the metrics they ask you to improve, but don't hold any illusions. You are almost certainly leaving that job in the next year one way or another.
You should try to leave on your own terms, i.e. find another job and submit your resignation.
Once you are fired, you can apply for unemployment benefits which is paid for by the insurance of that company.
If they are not willing to treat employees humanely, it is fair game for employees to not be honest with them.
Do the bare minimum to last out the 6 months or whatever and spend the time interviewing and applying.
If not: in general, in the US, it's perfectly legal for a company to just arbitrarily decide they need to fire N people, and arbitrarily choose a particular person to fire meet that "quota". This is true regardless of how many layers of managers are involved, or what bullshit PIP hoops are jumped through.
There would only be a legal issue if the worker was subject to a bona-fife employment contract (quite rare) or if they were discriminated against on the basis of a legally protected characteristic. Just being the least senior member of a team is not legally protected.
It's funny -- I've never heard that these were rare except in comments on HN, and with every job I've had in the industry, I've had a real employment contract (along with all of the devs I personally know well enough to know that about them.)
Is this "employment contracts are rare" thing a SV norm, perhaps?
But others may legitimately have other priorities.
It's easy to stay where you're not wanted- don't go to the office, don't answer email, don't do any real work. It's basically garden leave.
In my experience, it makes a very large difference.
> It's easy to stay where you're not wanted
I think this depends on personality. It would be unbelievably difficult for me.
For example, all those folks fired by Twitter... it would be silly to think that they weren't doing a good job, it was just a petulant move by Musk.
being laid off is a totally different thing from being fired, though. I assume people who are laid off won't say "I got fired", but "I got laid off". The two things have very different implications.
At least in my case, saying you got fired has zero implications. I've been close to being fired before, and the reasons were bogus- but there's no way to communicate that without a hiring agent being biased (incorrectly) against you. And I don't know that there truly is a difference, legally speaking, in terms of "being fired" or "laid off". You got terminated either way.
> I am not advocating doing or saying anything unethical
I thought you were advocating being deceptive. My apologies.
I try to be honest for ethical reasons, but being scrupulously honest (at least the best I can be as a fallible human being) has also served me very, very well in my career. I am quite certain I wouldn't have succeeded nearly to the degree I have if I weren't. So I recommend it very much.
It has, at times, caused me some loss, but the gains I've got from the habit have more than offset those.
> And I don't know that there truly is a difference, legally speaking, in terms of "being fired" or "laid off".
I wasn't saying there's a legal difference, I was saying there's a difference in the impression it makes on people. If you've been laid off, it was probably because of business considerations outside of your control. If you were fired, it was probably because of some sort of misbehavior on your part.
But if you say you were laid off when you were fired for cause, that's lying.
Bonus points, use the time to make the manager's life miserable.
Generally speaking, it should be a hint that its time to find a new job.
Here the claim is that the manager was forced to put X number of people on PIP regardless, which would be under something like a stack ranking system where a manager isn't allowed to say all their employees are performing adequately, they have to choose some to put on the chopping block. Amazon is famous for doing this.