... On this specific case, the sourcer who contacted this Apple employee should not have and will be terminated within the hour. We are scrubbing the sourcer’s records to ensure she did not contact anyone else. ...
From: Shona Brown (Google VP of Human Resources)
Appropriate response. Please make a public example of this termination within the group. Please also make it a very strong part of new hire training for the group. I want it clear that we have a zero-tolerance policy for violating our policies. This should (hopefully) prevent future occurrences.
From Eric Schmidt:
Steve, as a followup we investigated the recruiter’s actions and she violated our policies. Apologies again on this and I’m including a portion of the email I received from our head of recruiting [Arnnon Geshuri—M.A.]. Should this ever happen again please let me know immediately and we will handle. Thanks !! Eric
From Steve Jobs:
:)
From Sergei Brin:
Wow, Steve used a smiley. God, I never got one of those.
Source: https://pando.com/2014/03/25/newly-unsealed-documents-show-s...
Edit: Fixed the Shona Brown email. She's on the board of Atlassian now so I guess avoid those people too.
But at middle manager levels (hundreds of people, not a handful, in very large companies) they're not directly responsible to the CEO. Nor are they directly responsible to the customer/market. They're in 'middle management limbo' where all they have to work with, is local incentives. Usually financial - optimize the budget for results.
Sadly, this usually ends with middle managers trying to maximize their budget and minimize their required output, to increase their chances of success. Which means, the most expensive product possible.
That's what I mean by 'locally optimize'.
That email exchange is totally lacking any empathy (which is very typical of psychopathy [IANAD]) toward the ones affected, ie. the sourcer who is being fired and the employees whose livelihoods are being illegally depressed.
So already in 2007 a group of people at Google (all the hiring staff) knew about this policy. How much time did it take before someone complained?
My first eng manager at Google was really mistreated by people higher up in the org and as a result didn't have much freedom to make things right for our team (or our project, which generally struggled a lot as a result). This is not extrapolation or speculation: He confirmed it to me.
If anything, I think engineers at Google probably have more independence and freedom than managers do, because they're really only accountable for their own work and personal results. Managers have to corral all those independent engineers into a group they can get away with taking responsibility for, and the upper levels of the chain don't always act in a way that acknowledges how hard management can be. The disconnect also means that "best for a manager's career" is not automatically going to be compatible with the career health of their reports.
The gap between "labor" and "management" in this scenario is also a great example of why unions for labor are important - it's very difficult to represent the needs of both labor and management collectively, so a good method is for them to each bargain collectively based on their own needs and interests.
If the managers actually had more freedom, you'd get something closer to a bunch of small groups optimizing locally and producing (ideally, with the right incentive) collectively good results.
Here's a really easy example from my career (not Google, though): A manager needs to deliver on schedule. He has a set number of people on his team. One of those people is going to quit because he has a baby on the way, and the company's salary is not good enough.
If the manager had enough freedom, they'd have options available. The company is going to cut some of those off, but I'll enumerate some of the ones we potentially had at our fingertips (I was one of the team's managers in this situation):
* Give him a raise so he stays
* Promote someone qualified from the team, hire a junior employee to replace them
* Hire a senior employee to replace him and train them up ASAP to fill the gap
* Adjust the schedule to make up for the loss of his contribution
* Adjust the scope of the project to same as the above
In the end the studio head basically told us to go fuck ourselves, and the report ended up quitting. The project came in late, as I expected. This happened multiple times and in multiple cases it was direct interference from higher nodes in the chain - neither us in management or the labor below us were able to optimize at all. The product as a whole ended up shipping multiple years late due to lots of smaller-scale interference like that.
This is a typical example of local optimization?
Do we believe upper management said "screw with your workers until they stop being effective"? That's trivially false.
Giant companies are not just a CEO and some managers. There are typically half a dozen layers between the CEO and the footsoldier. And its the middle layer folks that create the true behavior of the beast.
Note that this isn't directly relevant to the case under discussion, which was coordinated at the CEO level