News for hackers. Stuff that matters.
Re:Design Docs at Google by JustLurking2022 on Tuesday May 07, 2024 @09:11AM (#40285023)
At some point, the cargo cult are the promo reviewers and then the two become the same thing.
Re:Design Docs at Google by Arainach on Tuesday May 07, 2024 @09:36AM (#40285271)
The reviewers presumable have access to the true metrics.
Re:Design Docs at Google by trelane on Tuesday May 07, 2024 @09:48AM (#40285413)
What if I told you these are their "true metrics?"
Re:Design Docs at Google by Arainach on Tuesday May 07, 2024 @09:54AM (#40285492)
If a company doesn't have consistent metrics for performance reviews uniformly across teams, get out of that company yesterday. That's just a hotbed of nepotism.
Re:Design Docs at Google by lupire on Tuesday May 07, 2024 @11:01AM (#40286425)
Please give an example of a metric for performance review for software engineering.
Re:Design Docs at Google by Arainach on Tuesday May 07, 2024 @12:26PM (#40287805)
Conceptual examples (not looking to argue about the specific bar):

Senior engineers will:

* Design a significant project which lands with measurable customer impact

* Demonstrate expertise in at least one core skill outside of coding (test infrastructure, SRE, security, accessibility, etc.)

* Demonstrate leadership by either being a TL, owning and leading team pillar efforts (security review, etc.), etc.

* etc.

Mid-level engineers will:

* Own either a small feature end to end or a significant piece of a larger design

* Contribute to at least one non-coding pillar

* etc.

These generally have more areas and can be further granular such as "low-performing midlevel is X, satisfactory is Y, exceeding is Z"

Re:Design Docs at Google by dpe82 on Tuesday May 07, 2024 @01:36PM (#40288916)
Those are requirements, not metrics.
Re:Design Docs at Google by Arainach on Tuesday May 07, 2024 @04:42PM (#40291212)
With sufficient granularity there is no difference. I can't give exact quotes without violating NDAs but variations on these have been the performance review standard at every major company I've worked at or known people who work at.
Re:Design Docs at Google by tra3 on Tuesday May 07, 2024 @10:47PM (#40293865)
Agreed.

Just proves the point, this person just cargo culted what makes google so famous in recent years. If you only metric is to launch new projects, you’re only gonna launch new projects. Who’s gonna get promoted for maintenance.

Re:Design Docs at Google by Arainach on Wednesday May 08, 2024 @05:48AM (#40296095)
>Conceptual examples (not looking to argue about the specific bar)

Again, not trying to debate what the specific bar should be, just giving examples of the kind of metrics you can use. What's your preferred alternative? Lines of code? Whenever your boss feels like it? Stuff like that is why no one believes a "senior staff superstar" from the hot startup of the week is any good and requires them to do whiteboarding.

Re:Design Docs at Google by mewpmewp2 on Tuesday May 07, 2024 @10:24AM (#40285851)
What do you mean by "true metrics"?
Re:Design Docs at Google by Arainach on Tuesday May 07, 2024 @10:45AM (#40286149)
The metrics which determine if someone gets promoted. Those decisions are being made by some group, presumably with guidelines. If the process for getting promoted is "this group does whatever they feel like" that company is a disaster and you need to get out.

Thus, there are rules, and they are written down. If they're not visible to normal employees, they guess the rules based on who they see get promoted (cargo cult) while the committee uses the true metrics.

It's not like becoming a manager is a secret cult where you're dropped in and you suddenly have carte blanche to do anything. At established companies there are rules and procedures, and while you will likely have access to more information than individual contributors, you won't just be promoting whoever you feel like without having to go through others.