Tech Expertise Not Important In Google Managers
Hugh Pickens writes "For much of its 13-year history, Google has taken a pretty simple approach to management: Leave people alone but if employees become stuck, they should ask their bosses, whose deep technical expertise propelled them into management in the first place. Now the Economic Times reports that statisticians at Google looking for characteristics that define good managers have gathered more than 10,000 observations about managers — across more than 100 variables, from various performance reviews, feedback surveys and other reports and found that technical expertise ranks dead last among Google's eight most important characteristics of good managers. What Google employees value most are even-keeled bosses who made time for one-on-one meetings, who helped people puzzle through problems by asking questions, not dictating answers, and who took an interest in employees' lives and careers."
Just like the maturation phase of every other technology focused corporation in history...
1. Founded by engineers
2. Rapid growth
3. Founding engineers become wealthy and retire early
4. Sales, marketing and management folks take over
5. Bureaucratic creativity sucking shithole
Posting as a coward since I've worked as a full time engineer for a few years. And I've had the worst manager of my career over there. I've had a few managers, some good, some bad but the incredibly horrible one was at Google.
I've seen managers with over 40 direct reports. I do not care how 'good' the manager is there is no way the manager can have a clue what his employees are doing or how much hard work they are putting. Every quarter the manager has to put them on a scale for an 'anonymous committee' to rate the employee (just 'meeting expectations' is quite an accomplishment), which is later used as a base for a potential promotion or raise. I think the average raise was probably less than 1% per year for the average employee. No wonder they had to do the +25% 3 months ago (10% + 15% of bonus converted to raise).
Moving from one team to an other is completely at the whim of your manager, they've even added a rule that you should not even dare to ask until you've spend 18 months in the team. Then you basically have to find your own replacement: you can't leave until you find an other engineer that is as good as you and willing to work in the team you are trying to run away from !!! Managers rarely get the boot because it is very hard to find a manager willing to manage indecent amounts of direct reports.
Complaining to HR is useless and will just antagonize your manager further. You will get managed to quit over a very long time, and once you do quit being honest about why you leave will put you on a black list (say an other team find your resume and wants you in, HR will stop the interviews). I've heard of experienced employees crying in the upper managers offices about how badly they were treated. I have seen several coworkers skipping on vacation and maxing out they vacation allowance and still not taking vacation since. HR does not see any problem with this, if you are sick and dare to take sick days your performance should be lowered because you performed less work. This situation of fear is not good and lead to many resignations for greener, better paid, pastures in the past few years. Add to that a founder (Sergey) saying that employees should pay for the privilege of working at Google, and not as a joke (there at least one internal video about it).
Note that the above is not the 'rule' and plenty of Software Engineers will have had much better experiences. Some have just a reputation of doing amazing work on a project years ago and only need to show up to work once in a while. The aura is not rubbing off and if you criticize them it is bad for your own reputation.
I am very happy where I work nowadays, if you get an offer from Google take it if the salary cut is not too bad, hang on for a year or two. It will be a big plus for your resume, you will learn a lot of technical good practices, but do not expect to have a long good career over there unless you are a very skilled politician.
And I can tell you that the general quality of Google managers is very poor in spite of supposed systems for filtering, training and guiding them. This is in fact the worst thing about working at Google: self important, self absorbed managers who only care about milking their own situation for everything they can get. Often nonexistent or weak technical skills just pours salt on this bleeding wound.
The few guidelines that Google puts in place tend to be unmonitored by anyone who matters and are widely and cynically ignored. Peer review is very much one of those. There are of course good managers at Google, I know a few. But they are badly outnumbered by facetimers and soulless climbers.
Have you got your LWN subscription yet?
Another thing: managers at Google widely believe that they are better than engineers simply because they are managers, in spite of a supposed explicit ban on this attitude. For that matter, so do the sysops, because they are in control of the facilities engineers need to do their work, and because they get first dibs on any shiny new equipment that arrives. I got the distinct impression that Google sysops think of themselves as managers, or at least, very important people, and in particular, more important than engineers. By the way, I was a Google sysop before I moved to engineering so I saw this from the inside.
Have you got your LWN subscription yet?
The US Navy, and the rest of the military, would disagree with you. Uncle Sam taught me that few, if any, people are "born leaders". More, I was taught that "born leaders" seldom fit into a cohesive unit, being more interested in their own goals, than the unit or corporate goals. Leadership and/or management are learned skills, and the military spends a great deal of effort teaching men and women to be effective leaders and managers. And, yes, you can test for leadership skills. Put a person into a real life complex stressful situation, and see how they perform. Oh, wait - you meant a test that you can sit down, and fill in the answers with a pencil? No, not really - but it might be a start if you bother to ask your victim or subject if he can even define leadership or management. I've often found that merely defining a problem or a goal gets me a long way toward solving the problem.
Freebie for you: My leadership training defined leadership as the art of motivating people to do what they should be doing anyway. Does that help you at all?
BTW - my training wasn't strictly military. The courses that I took were jointly developed by the US Navy and Princeton University. Everything that I learned is readily available to people in the corporate and industrial world, if they bother to look for it.
"Windows is like the faint smell of piss in a subway: it's there, and there's nothing you can do about it." - Charlie Br