Google to Slow Hiring for Rest of 2020
So years ago this came up with Eric Schmidt, who was CEO of Google through the GFC. After 2007, Google had selective layoffs (probably not in engineering) and slowed hiring. They also paused construction projects in Mountain View and probably elsewhere.<p>Eric said when asked about it that it was a mistake. He said that if Google was healthy there was no need to have a kneejerk reaction to the slowdown. And this caused significant growing pains later.<p>Is the situation the same now? I&#x27;m not so sure. I think this economic shock is potentially far more serious and could last much longer. But also, I don&#x27;t think Google really knows what Google is anymore. We&#x27;re long passed the mission statement of making the world&#x27;s information accessible and useful. And certainly my impression from working there (now &gt;3 years ago) was that even then there were a ton of teams and orgs that didn&#x27;t really have a reason to exist.<p>Have people sitting around and they will find things that &quot;need&quot; doing. I saw many a project that was simply rewriting something where I at least had questions as to the real need for that. The bureaucracy is expanding to meet the needs of the expanding bureaucracy as they say.<p>And there was (and I imagine still is) too many layers of middle management. The ideal is (IMHO) CEO -&gt; SVP (PA level) -&gt; VP -&gt; Eng Director -&gt; Manager (of managers) -&gt; Manager (of ICs) -&gt; IC. That&#x27;s 7 levels. I don&#x27;t know what Google&#x27;s mean org depth is in engineering but my guess is it&#x27;s closer to 11, maybe even 12.<p>In fact this would be a good metric:<p>Management overhead = Mean org depth &#x2F; log(# of employees)<p>where<p>Mean org depth = Mean of how many layers each IC has above them