3 ms·
This is the most important sentence: > Performance reviews are riddled with bias. Let me describe the apocryphal big tech company performance review process.
by jmyeet 4y ago
This is the most important sentence:
> Performance reviews are riddled with bias.
Let me describe the apocryphal big tech company performance review process.
Once or twice a year you ask colleagues for feedback. Hopefully they do. They can also choose not to. You generally need 2-8 people to provide feedback. Less for a "standard" cycle. More for a promotion cycle. The specifics of this process vary from company to company (eg some reviewers might see your self-review, some processes just give textual feedback while others require reviewers to rate you in addition to supporting text).
Your manager may then distill all this feedback into a single page. Some processes have the full packet. Others do not.
Your manager will, based on this total packet, come up with a provisional rating and then go into calibration to argue your case. This provisional rating tends to be reasonably accurate. It may get argued down. It less often gets argued up (but it can happen). In this process you're essentially being stack ranked by similar employees (ie same job ladder and level).
To avoid ratings inflation across orgs (typically 100-150+ people), you are graded on a curve. Only a few people can get Greatly Exceeds Expectations. Some will require a percentage to get subpar ratings (eg Meets Most Expectations). This is the tech company equivalent of cutting the bottom 5-10% every year. These people may end up on PIPs or may be effectively forced out of the company because people with subpar ratings can't transfer or new teams just don't want to gamble on them.
Promotion decisions may be made by your org. They be made by committees of higher level individuals on your ladder (eg L5->L6 promotions decided by committees of L7/L8s).
Promotion candidates are also effectively or actually stack ranked. As a cost-saving measure there are promotion targets. Only the top X% will get promoted.
So how does this go wrong?
1. The number 1 most important thing is for your management team to like you. If they do, your failures will be viewed in a positive light (eg "we learned a lot from this failed project that we will take into future projects") as opposed to a negative light (eg same facts leading to "failed to ship project").
2. If the influential people in your org don't like you, it's going to be an uphill battle to do well;
3. Managers are subject to the same forces so may curry favor by supporting certain candidates for pomotion and higher ratings over others. There is an awful lot of horse trading that goes on behind the scenes. You will see none of this;
4. To curve fit the org, after all calibration is done people will have their ratings changed (generally down). This is more likely to happen if the org doesn't like you or simply likes you less than someone else;
5. Promotion target percentages are a key cost control measure. Reducing it saves significant costs (eg Ruth Porat did this in a leaked memo when she became CFO at Google). This creates a backlog for pomotion. Standards go up. You have to "wait your turn" and this may take years. This limbo will often keep people around who don't want to leave to get more opportunities.
6. Meeting goals, a key issue in defining "impact", is highly subjective too. You may get an impossible task dumped on you, fail and get dinged for it while someone else gets some way easier goal.
The whole process is honestly the worst part of working in big tech.
- nickd2001 4y agoI worked for a company that did these kind of performance reviews and it was exactly as you describe. I found it basically "unworkable" because you end up with 2 jobs- (1) the actual technical job you were hired to do and (2) trying to not be screwed by the performance process. So you have to play politics, constantly watch what others do, try to advertise and sell the work you've done to managers. What if you're only interested in writing good code, not bragging about it? Especially if you're in tech because your skills are technical, not the schmoozing stuff. Some of the best developers are either introverted (which is fine :) ) or simply more interested in elegant technical solutions to real actual problems, than political BS. This performance process also makes people become rivals. They have to show they're better than their peers. Which is 100% destructive to teamwork. Then there's the unpredictability. In a good workplace, someone can work hard, deliver, forge relationships and as time goes on they become very trusted. What you don't want is that person constantly distracted by having to prove themselves. You don't want the situation where years of good work suddenly for no apparent reason comes up against something in performance management and get marked down. Another case, I saw 2 colleagues have misunderstandings due to geographical distance, culture, possible mental health issues by 1 of them. It all got worked out and fixed amicably, no lingering grudges, but one of them still I believe got a sub-par end of year, thus blocking a way to leave that situation behind. That cannot be helpful. Also such performance systems promote those more skilled at gaming the system than those who would do best in the more senior role. Thus you end up with incompetent managers, and technical staff that are good at stealing ideas and flogging them as their own, but can't really code well. I'm glad I got the ** out of there, into a workplace that values friendship and collaboration instead !! Is this the norm in big tech these days? If so.. well to me it just adds a big random element to everything. You can try to work hard, gain skills, deliver, but other factors can mean you aren't recognised. This was always true to some extent, you need a decent boss , company needs to be doing well etc, but my feeling is the "good old days" were more predictable. I wonder if this performance cr*p ultimately drives away good engineers, and it'll all come full circle when companies realise its a a bad idea. But then, I thought that happened years ago at Microsoft when they ditched "stack ranking"? Maybe this keeps bubbling up? I mean , some daft managers think its a good idea, it looks like its working for a while, then anyone decent gets hacked off and leaves to competitors, then they abandon it, till later some so-called bright spark re-invents it?