Your comment is a case in point. Anyone familiar with your story (at Google and, as you know, there are many of us who are) knows how totally skewed your perception is.
Many people (including me) tried to offer you constructive advice. Without getting into specifics I think it's fair to say that any problems you had were pretty much entirely of your own making.
Regarding a few specifics:
- You mischaracterize the slotting process, which is now largely gone anyway (and you should know this so I'm not sure why you're bring it up as if it were a present problem);
- I can't speak for how much time managers spend on Perf but managing their people and the careers of those people is kinda their job. As for engineers, it depends on how much feedback you need to do. One engineer I know how to do >20 feedbacks and this took him a couple of days. Generally speaking, the more you have to do it, the quicker you are (at each one);
The fact that performance is peer-driven is overall a good thing. It means your relationship with your peers matters and this isn't just an arbitrary managerial decision. I see you still don't get that.
Google isn't perfect. Then again, nothing is. But it's pretty great. Or, rather, it can be. You get as much out of it as you put in. See something that needs fixing? Then fix it. It's certainly not a place for those that simply like to sit back and complain.
Speak for yourself, would you? I'm myself a victim, unfortunately. I never even knew my Perf when I was with the company, only discovered it accidentally after I left. The process is very broken for me. Thanks @michaelochurch, I now know better about what had happened.
I agree that many cases are different but the HR process is broken at Google, and it happens to be broken in a way unique to how Google set things up, but the effect is the same at other companies where reviews are a beauty contest.
I'm sorry to hear that you feel your time at Google is the worst experience for you, but your story just doesn't make sense. How can you submit a ticket after you left? Were you in eng? Did you not see mchurch's delusional rants and all the people that came out trying to help him? If anything, the support, advice given to mchurch is exactly why Google is a pretty awesome place to work.
I submitted a ticket from outside as an alumnus. It is a fact. Credit to Google for setting this up. That being said, if there is anyone gets delusional, it is you.
I'm an engineer and used to work for Sun Microsystems. It was awesome. So I have pretty good idea about what it takes and what to expect working for a good silicon valley company in general, including Google. It just didn't apply to what happened to me in Google.
Saying you didn't explore your personal profile or look at the perf website and then complaining that you never knew your performance scores is like saying you never visited your calendar page and being upset about not knowing your meeting schedule.
It sounds like you may have had issues with poor management, but the fact that you didn't know your performance scores has nothing to do with mchurch's fictional manager retaliation, nor is it common for managers to blackmail their reports with poor perf scores over differences of opinion the way he alleges.
Please, at least read what you reply to.
"Please, at least read what you reply to."
Why isn't this guy getting down-voted? Personal attacks and a sorry attitude shouldn't be tolerated on HN.
How come? Your interpretation of what I said amuses me, sir. And the way you do it, quoting single sentence without context, seriously?
I'm familiar with michaelochurch's story (at least as much as your average Googler is, I assume) and I second what cletus is saying here.
I said that they got rid of it, but I think the fact that such an obviously bad idea could get in the door in the first place is symptomatic of out-of-touch managers, and the same people are still there-- just coming up with new bad ideas (like the 3 word mission statements) that will linger around for 5 years.
The fact that performance is peer-driven is overall a good thing. It means your relationship with your peers matters and this isn't just an arbitrary managerial decision.
In theory, this would be true. In practice at Google, manager-as-SPOF is as much in force as it is in any other company. Actually, I think it's more the case at Google than at most places, because managers can unilaterally block transfers and because HR does nothing about abuse-of-process issues.
What Perf does is that it gives more reasons to deny promotions, not more avenues toward success. Managers can block promotions, and so can influential peers. So, in some cases, can trigger-happy idiots who abuse the unsolicited feedback feature (which does nothing but breed distrust, especially with the "manager-only feedback" feature, which is, at best, a quarter-step up from "XXX is a slut" gossip in fraternity bathrooms).
See something that needs fixing? Then fix it.
If you try to fix managerial, cultural, or product problems you just make enemies of the people who are invested in bad ideas and stupid decisions. It's really not worth doing.
I'm glad that Perf at Google involves peer reviews, and that colleagues can volunteer to contribute to your review packet. I found the 3-word mission statement to be a fun thing. (For outsiders: this is just a text field on your intranet profile page where you can make up a slogan that concisely describes your goals.) It's about the same as being at liberty to make up your own job title for your business cards. People get very creative with it.
I came to Google as part of a medium-sized acquisition and I've seen HR solve complex problems (we brought some baggage with us that they had to deal with), and seen managers' managers overrule their attempts to block transfers. Problems were not solved overnight, but they were definitely solved. People worked hard and got promoted. Things work pretty well from my point of view. I've experienced my fair share of frustrations at Google, but I have also found that the company is full of people who are trying to make employees successful and happy.
The successful path requires that you employ patience, humility, and hard work in equal measure. If you can do that, you can thrive.
If you come in with a giant ego, pick fights with everyone you encounter, and ignore advice, obviously you're not going to succeed. When Yoda says "Your weapons, you will not need them", LEAVE THEM OUTSIDE. He is the Jedi master and you are the padawan; if you cannot recognize that, forever will the Dark Side control your destiny. :)
A lot of Googlers are reacting as if I attacked them. I didn't. Not in the least (unless they personally made some of the moronic decisions I listed). And Google is, despite the attempts of many influential and powerful people to destroy it, still a great company. I found most individual Googlers are really great people, but I think the danger of having the wrong people make decisions that affect thousands of people cannot be understated.
Wrong. The problem with Google started with the new CEO. The decision to focus on Facebook, the Motorola acquisition, Google+, integration across all Google products and services,etc. these are not mid-level management decisions. These are decisions made by Larry Page.
The problem is with the CEO.
Google sells YOUR personal information that you do NOT want to share to advertisers.
Big difference.
The privacy policy says: "We will ask for your consent before using information for a purpose other than those that are set out in this Privacy Policy," and selling your information is not listed there. Read it for yourself, it's pretty short!
According to Google, this is not true. https://www.google.com/search?q=Google+does+not+share+person...
There's probably ample evidence to support your claim, but linking to search results doesn't seem all that helpful. (If Google is still personalizing web searches or if someone has blocked a domain from their results we could be looking at different lists.)
You understand. The industrie washes your brain to only see the positive side effects and don't think about the negative ones.
Google+ is a new product. Don't make a judgement so early. It is getting better everyday.
Why did you get defensive in the end ("google isn't perfect..." = "water is wet", no, really)?
You were only there for 6 months in 2011. That hardly makes you an authority on what happened in 2009-2011, or about how the company is managed. Perhaps it's time to consider the possibility that the problem was more with yourself than with Google.
People absolutely do not "literally drop everything for 1-2 weeks" for perf. That's just ridiculous. People complain about it, but it's more like a few hours of work, not a week. Moreover, the Google perf system is hands down the most amazingly great employee performance review system I've ever seen. Okay, my worldly experience only goes so far, but I sat in on calibration meetings and promotion committee meetings and so on, and I was absolutely shocked at how fair and objective people were. I'm sure there are cases of abuse or where it goes wrong - there are in any such system - but your examples of eg. using low performance scores to prevent transfers ought to be hard to achieve; the system gives such high weight to peer reviews that a crazy manager should be shown as crazy in fairly short order. At least in the group where I sat in these meetings (Commerce) this was absolutely the case.
I have mixed feelings about Google. But your accusations here are mostly misguided IMHO.
The depressing part is that Google is so far ahead of everyone else that they can fuck up a lot of things and still be the best place to work by light years. (They even pay better than the investment banks now!)
I haven't done a Perf cycle yet, but the only problem I foresee is that nobody really knows what my job title is supposed to do. That hasn't stopped my coworkers from being promoted, though, so I can roll with it :)
I personally think "managerial approval" is just for 3 things:
1) If someone decides to do something wrong/illegal as 20% project, the manager should've caught this (so this 'approval' is really a 'we reserve the right to blame the manager if things go wrong') ;) 2) People probably want their 20% project (and progress therewith) to be factored into their perf, as such, their managers need to know about it. 3) So that people don't pick clearly fraudulent 20% projects (such as 'my 20% project is to stay at home and watch TV')
Google is developing Go precisely to improve engineer productivity, so this claim is rather suspect.
Java is unproductive when you are a startup with one developer, but it works rather well at Google. Each change has to be manually code reviewed before submission anyway, so you aren't saving much time by using Python instead of Java. Agreeing on one language means that it's easy to switch teams; if you did Haskell and another team used OCaml, it would be hard to switch. If you both use Java, though, the barrier to moving is smaller and that means you can switch projects without losing productivity. And that's a good thing.
(Remember: Java at Google is not the same as Java at Bank of America. The toolchain is better, the libraries are better, the culture is better, and the codebase is better. There's really very little I hate about Google-style Java, and that's after hating Java with a passion for about 10 years.)
That's 1. A trivial number, if not a trivial system.
Of course, I'm a mere contractor, I don't see the bigger picture, and all. But I _hope_ that on the language front things are not as grim.
Google's stance on Scala may have changed in the past few months as the language becomes more mature.
GOOG profits are still growing, and they still control online search which I think will remain a huge cash cow for a long time.
Honestly, I've worked both on Wall Street and at Google. Individual people at Google are nicer, but the careerism and mentality (among people who want to move up) are nearly identical.
Like cletus mentioned, many people reached out to offer you constructive advice. You ignored everyone, thought yourself superior to everyone.
I bet you were just waiting to be the first to comment, no? You did well...not only did you throw Google under the bus, you also threw California under the bus. Learn to have a little class.
Speaking purely as an outsider, you and cletus' comment prove his statement. You both clearly have an agenda, and the tone of your comments only lend credence to the stories.
As for the "California" thingy, he can't tell anything wrong about any state?
Furthermore, in general, it's a bad idea not to make yourself look like a total ass in public; it's a career limiting move in most companies, but in a company where it is truly the case that your peers have a lot more to do with your getting promoted than what your manager might have to say, it really, Really is a bad idea.
Hopefully everyone would agree that this is good advice....
And if you join a company and someone more senior than you with ACTUAL accomplishments and that is respected in and outside of the company tries to take you under his wings and guide you through the corporate landscape, don't dismiss their actual accomplishments as "irrelevant" at the same time boasting about your success in a product for a "niche market that doesn't exist"
And if you join a company, you should not claim expertise in something unless you are an ACTUAL expert and have the knowledge, experience, and accomplishments to back that up. Saying that you're a T7-9 visionary doesn't make you a T7-9 visionary!
And if you join a company, don't dismiss your fellow colleagues and make a fool of yourself because even if you don't work with them now at the current company, you may encounter them again in the future.
I'm not speaking to any specific incident. Just general advice that any new junior employee to any company should follow.
For people skeptical of the other replies here, the reputation of OP is pretty well known... it has almost become a shibboleth of the people that were around during his tenure.
I'm really disturbed by this. I'm not a stranger to being the smartest person in the room - it happens from time to time - but, while interviewing at Google (I did it a couple times), I was always amazed with my interviewers, who were, with no exceptions, exceedingly smart people.
Any rip on a state with 50 million people in it is somewhat in jest. Anyway, there are a lot of great things about "California culture". When applied to technology, an open-minded and experimental "Let's try it" mentality is great. Necessary, even. When applied to management without enough attention paid to the fact that some of the people posing ideas have bad intentions, some awful ideas get into implementation and it damages companies. It hurts people. So more conservatism in selecting what to implement is in order, and discussing ideas that might be harmful (with thousands of people) until they've been explored is a bad idea.
The problem with Google is that it's got the conservative New York culture technically (I mean, even Scala isn't allowed) and the California culture with respect to hare-brained managerial ideas like downslotting-- the exact opposite of how things should be.
Put it this way: technological and managerial innovation are utterly different. If you do a tech demo and it's slightly rough around the edges, that's fine. You're awesome for having the courage to put yourself out there. If you're putting forward suggestions that are going to affect the way thousands of people work, the traditionally sloppy (for tech, I mean "sloppy" in a positive sense) tech demo is not how you should be communicating.
If management was easy, we could all read a book about how to manage a company and then all do it optimally. Since that's not the case, experiments are necessary, and I admire the attitude that leaves them open to things that might not work. I disagree that it was "obvious" that the downslotting mechanism would not work - or rather, that it was obviously worse than any other alternative, because once you have the "not performing as expected" problem, all your options suck.
And BTW, I'm in New York :)
These levels are a convenient fiction. Performance is way too context-dependent to believe that there's some "platonic" level for each engineer. This (http://michaelochurch.wordpress.com/2012/01/26/the-trajector...) is the best model I could come up with for the software engineer trajectory, and even it has a 0.2 to 0.4 point (out of 3.0) swing for most individuals based on technology choices, interpersonal topologies, motivational flux, etc.
What you mean is "some people don't work out". Right. So there are people you "manage out" (that is, try to get them to find another job and fire them after ~6 months if they don't get the hint and you absolutely have to) and there are people you work with to bring them up to speed, or to figure out what's blocking them. Typical management stuff. What doesn't work is to keep people around but at a lower level than they were promised in the hiring process. That just creates a class of miserable, shafted people who hate their jobs and the company they work for.
By the way, a lot of the idiots on this subthread think I'm airing personal gripes. I joined after slotting. I'm just pointing out what kinds of ridiculous results come from an out-of-touch management culture. What drove me insane at Google was being at a company where the engineers were so good at their jobs and yet the people making important decisions were so epically bad. The disconnect was shocking. I was watching an awesome company self-destruct in front of me.
Also, on downslotting: careers are sensitive things and once you make one overt move so directly against an employee's interests, you've essentially lost that person. Loyalty is pretty much binary. Once you make a move like that on someone, you now have someone whose full-time interest is career repair, which usually involves getting the fuck out and lining up the next job. If this is what you want, then fine. (If someone really is a bad fit, for that person to begin full-time job searching is the best thing.) That category doesn't encompass most of the company. Downslotting only makes sense as a mechanism for managing people out, and (1) there are better ways of doing that, and (2) you shouldn't be managing out over 50% of new hires.
The real reason for slotting, I think, was to put a better job title in the offer letter than people were actually expected to get, since the upper title is what was used. This works only because of Google's brand: what keeps it from doing major damage is that downslotted people have the Google name on their resumes and can get the fuck out long before they become "problem employees".
I couldn't help but leave an (infographic of my reaction to the outrage re: 20% time.
Google has an immense amount of talent "under its roof". Unfortunately, there's a necrotic layer of useless and counterproductive middle management coming up with a series of "innovations" that each have made the company worse. For a few examples:
* 20% time is dead. It requires managerial approval. More on that later.
* Until recently, people were hired "between levels" on the engineering ladder (which is generally a disaster at Google; see this: http://piaw.blogspot.com/2010/04/promotion-systems.html) and then about 2/3 of them were "downslotted" to a lower level. It didn't affect their pay, but it blocked future raises, was a career kiss-of-death, and generally shat all over morale. What's amazing to me is that no one ever said, before this bit of syphilitic idiocy could reach implementation, "This is a terrible idea and you need to stop abusing cough syrup on the job." Fucking California culture, man. In New York, terrible ideas cause buildings to fall down kill people and so we refuse to tolerate them. Unfortunately, Google's executives seemed to lack the insight to recognize an obviously horrible idea as horrible. (Downslotting was abolished last year, but I'm astonished that such idiocy got in the door in the first place.)
* Engineers (not just managers) literally drop everything for 1-2 weeks each year to write "Perf" (for themselves and peers). The high-stakes performance review process is just that important.
* Google is resistant to any change that might improve engineer productivity beyond the rather plodding rate it has now. C++ and Java are the real house languages; Scala's not even on the table. Python is listed as a house language so Google can still hire people but it's rarely used and nearly deprecated in production.
* Managers have free rein to fuck over an employee in Perf if they believe him to be "distracted" or at risk of future distraction by 20% time, even if that employee's performance is otherwise strong. This doesn't make Google any worse or any different from more traditionally managed companies. It does deprive them of the right to market 20% time as a perk without being called out as liars.
* Last summer, it was announced that every employee had to have a 3-word "mission statement" that managers could change, and a 63-word quarterly summaries of their work. This was the infamous "7/20" all-hands in which the deprecation of 20%-time was announced.
* HR ignores severe ethical lapses by influential managers, including a person who was outright proven to be using low performance scores and PIPs (Performance Improvement Plans, which stop transfers) to block transfers.
To make it clear, Google still has some really great people and could turn itself around if it just fired most of the middle layers. The company still has an incredible number of immensely talented engineers of whom I think quite highly, but the company is so horribly managed that I see nothing but a cold, miserable twilight in its future.