Googler... ex-Googler

It doesn't matter how good my evals are or how big my contributions. It doesn't matter that there are multiple multi-million-dollar revenue streams which exist in large part due to my contributions. It doesn't matter that I have been told I am good enough that I should be promoted to the next level. Raises barely exist, let alone promotions. Because theoretically some other engineer could have done the same work I actually did, the fact that I'm the one who did it doesn't matter and I deserve no reward for doing it beyond the minimum money necessary to secure my labor.

Under those conditions, why should I - or anyone - do any more than the minimum necessary to not get fired for cause? If the company doesn't see me as more than X dollars for X revenue, why should I?

Usually there is a hidden variable that you don't know. It is your salary. That is why it sometimes looks surprising when senior roles are cut that look extremely valuable to the company from the outset. Maybe they were that valuable but still deemed to expensive.

This is frequently the case. I've worked at big employers (comparable in level of corporate-ness to Google if not absolute size) where the layoff process, roughly was:

1. Aggregate layoff target gets set and apportioned amongst functional leaders, then targets cascaded down to the line manager level.

2. Managers fill out a stack ranking spreadsheet for their team across a few metrics including a boolean "diversity" field[0]. There were many rumors about the "diversity field", most notably that anyone so flagged would not be fired, but so far as I could tell these were false (see point #4)

3. People to be fired are developed based on these lists (I.e., if a manager has to fire two people, then the two lowest-ranked employees per the spreadsheet are selected.)

4. HR does a meta-analysis of all to-be-fired employees, ensuring that a disproportionate number of employees from protected classes are not impacted. If too many are, then some of the next-lowest-ranked employees are selected to be fired in their stead.

As far as I could tell, the only part of the process where any sort of individual, human consideration was occurring was maybe at the line manager level if they decided to tweak the stack rankings based on who they felt deserved to be protected. And then, to the extent that happens, you have all the problems with bias and favoritism that come into play.

0 - I realize this is probably controversial, but I saw it with my own eyes.

- layoff plans must be communicated ahead of time. Minimum 30 days notice, usually much more

- Needs to be negotiated with worker representatives (works council, syndicate if there is one)

- LIFO principle for layoffs, newest employees are let go first. Stack ranking not possible

- Any kind of discrimination is forbidden

- At a minimum, you get 2 months pay + accrued holidays

It's baffling to imagine that you could learn about your job disappearing from one day to the next, and be immediately left out in the cold.

In the United States, employers with more than 100 full-time, non-probationary employees must provide 60 days notice of most planned layoffs[0]

> - LIFO principle for layoffs, newest employees are let go first. Stack ranking not possible

This is functionally equivalent to a stack ranking in that it is a forced-distribution scheme. It is just based on a single factor that is outside of the employee's control. Say what you want about stack ranking, but people do have a large degree of control over their job performance.

> Any kind of discrimination is forbidden

In the United States any kind of job discrimination against members of protected classes[1] in illegal. Even inadvertently disparately impacting[2] members of a protected group is illegal.

0 - https://www.dol.gov/general/topic/termination/plantclosings

1 - https://www.eeoc.gov/employers/small-business/3-who-protecte...

2 - https://www.law.cornell.edu/wex/disparate_impact