4 ms·
Note that this was written by someone who spent three months at Google as an intern, so it's probably not very representative of what it's really like to work t
by greenyoda 13y ago
Note that this was written by someone who spent three months at Google as an intern, so it's probably not very representative of what it's really like to work there. After three months you can't really understand much about a complex corporate culture or become familiar with more than a tiny corner of a huge company. And interns aren't involved in corporate politics, performance reviews, etc.
- dewitt 13y agoI found it fairly accurate, and I've worked there seven years. For most engineers most of the time, the job isn't politics or performance reviews. It's writing interesting software with talented teammates. (Counterexamples of course exist, and a handful of vocal ones certainly like to chime in on threads like this. But if it weren't still mostly good for engineers at Google, Google wouldn't still employ the great engineers it does. But it does have great engineers to this day, so something is still going mostly right.)
- asdfprou 13y agoThanks Dewitt! I had a feeling that my lack of tenure was going to be a point of contention, so having someone with as much experience as you backing the story certainly helps!
- varelse 13y agoAs one of the vocal ones(tm), even I would say Google is fantastic if you get allocated onto the right team. This obviously occurs most of the time or the place would be out of business. What led to me becoming one of the vocal ones is what happens when allocation fails and there's really no resort other than trying to fit in doing something completely uninteresting or leaving. Google seemingly does not acknowledge that the allocation process is in any way flawed. My mistake was I should have insisted on an allocation upfront as a condition of accepting the offer made to me. After acing the interview, all the power was in my hands and I failed to make use of it.
- dewitt 13y agoI'm sincerely sorry things didn't work out in your case, varelse. I don't know your backstory, and it wouldn't be my story to tell even if I did. But I do know it makes me sad whenever I hear that we have any attrition, regretted or otherwise. And I know as an eng manager I try to put myself out there for /any/ engineer who wants a hand, or even just a sympathetic ear. Some cases are just unfixable, but I like to believe we still can repair a good number of them. I hope things worked out better for you wherever you landed next.
- seanmcdirmid 13y agoGoogle has to get someone to work on the boring but necessary projects! Google appears to hire high-end passionate talent; these are the people who aren't going to be satisfied doing something they aren't interested in and/or don't involve many hard problems, just lots of necessary grunt work (all projects require grinding, but some more than others). They care too much and are not in it just for the money. I would be surprised if Google did not know what projects are problematic, but finding solutions would be another matter.
- varelse 13y agoAnd that's exactly what happened to me. I was senior level talent at the preceding employer with a fantastic track record. When I started at Google, I was effectively told to start over from scratch. I'm not just in it for the money. The money can briefly distract me, but if I don't feel passionate about what I'm doing, I tune out, and ultimately leave.
- seanmcdirmid 13y agoMicrosoft (my employer) at least doesn't really have this problem. First, we hire from a broader talent base so we usually have talent for teams that aren't as sexy as others. Second, you interview to the team you will be working with, even if it is an internal transfer. This is bi-directional: they aren't just interviewing you, you are interviewing them. Perhaps Google simply needs to make the interviewing more bi-directional at the project/team level to fix the problem. From what I understand, right now allocation works only in one directly: teams bid for the new employee, but the employee doesn't get to bid on the teams!
- asdfprou 13y agoHey Greenyoda, Certainly correct, although I have worked at a number of other companies (an investment bank, Microsoft, a startup, and in management consulting) so I was using those as benchmarks. Thanks for reading!
- guyzero 13y agoYes, you certainly can't form an opinion in three months. Sorry OP, your opinion is almost certainly wrong.
- asdfprou 13y agoYou formed an opinion about my post and my experience in around 5 minutes. Does this mean your opinion about my opinion is almost certainly wrong as well? Snide comments aside, thanks for reading!
- Helianthus 13y agoYou're getting kinda ugly about this. Are you really that disingenuous? In this parent, you just fought almost as dirty as it is possible to fight within proper, polite terms, and you made a point of doing it. And then you want to discard that with "Snide comments aside, thanks for reading!"
- guyzero 13y agoMy sarcasm was actually intended to indicate that opinions can never be "wrong" in some objective sense as they represent subjective experience. The notion that your opinion can't be valid because you worked for "only" three months is nonsensical. People who worked for Google for a day have opinions as valid as anyone else's.