9 ms·
Tips for Noogler Engineers (Noogler = New at Google)
- unshift 16y agoso basically it's the same as any large megacorp?
- deleted 16y ago[deleted]
- wan23 16y agoAny large megacorp with distracting fun mailing lists and talks to avoid (tip #2). Also 20% time and mentoring (tip #1). Definitely the part about performance reviews (tip #3) and having a good manager (tip #4) is applicable to any company, though the part where you should make sure you choose a good manager might not be.
- philwelch 16y agoI like how the advice to succeed at Google involves ignoring (tips 1 and 2) the distracting and fun things that distinguish Google from other companies.
- jrockway 16y agoIf you are willing to spend more than 8 hours a day on "work", then you can do well and read mailing lists. If you were at a company other than Google, then your 9th hour wouldn't get you much more than a headache, but at Google, you can learn about cool stuff and get to know your coworkers better. (I think 8 hours is way too long to spend working in a single day anyway, so company-sponsored mailing lists seem like a nice distraction. I would rather just go home and read Internet mailing lists though.)
- neutronicus 16y agoI momentarily misread "Noogler" as "Nuclear". Alas. I had hoped for another nuclear engineer HN reader.
- fs111 16y agoWhen I read yours, I had Homer's voice in my head, somehow :-D
- dochtman 16y agoLooks like a nice list of things for Google management to improve about their promotion process.
- lkozma 16y agoThat must be the most depressing thing I read in quite a while.
- Tamerlin 16y agoAgreed... it's supposedly one of the few remaining companies that actually respect engineers, but this post pretty much comes out and says otherwise in bold, flashing letters. "(Exception: War-room firefighting. Google loves those, and loves heroic performances from people in war-rooms)" The whole "war room" concept in IT has always bothered me -- it's what managers do when they have a crisis that they don't know how to deal with. It's usually a crisis that they could have avoided if they'd actually done their own job in the first place. War rooms are also invariably where the worst of the developers end up -- at Disney the war room period was one of our most product weeks as a result. Of course, the folks who got rewarded were the ones in the war room, even though their primary contribution was to strut around in front of a bunch of executives while the rest of the team got project work done and the operations team had already figured out what went wrong.
- brown9-2 16y agoGiven Google's attitude towards perpetual betas, I'm curious if their "war rooms" are more to solve immediate problems (show-stopping bugs, security issues, etc) rather than attempts to "fix" late projects.
- nostrademons 16y agoGoogle's attitude toward perpetual betas extends to perpetual war rooms. Almost every feature that you'd recognize from the last three years was developed in a war room. The visual redesign was a war room (well, war cubicle). Real-time search was a war room. The search options panel was a war room. SearchWiki was a war room. The bar across the top was a war room. Pac Man wasn't a war room, but almost all the folks involved were in war rooms and avoiding the war at the time. Basically, it's just putting all the developers involved on a project in a room together and giving them a clear goal (launching). Other firms might call this "Agile" or even just "development". Heck, still others would call this a "startup". "We've always been at war with Eurasia..."
- jacquesm 16y agoI love the ending line: > Finally, if you get fed up of working for a big company, consider joining a startup. This one posting probably did more damage to google hiring from the HN ranks than all the others that I've seen to date. With friends like that who needs enemies.
- brown9-2 16y agoTo be fair, Piaw sells a book all about how to get a job at a startup (http://books.piaw.net/guide/index.html http://books.piaw.net/guide/index.html). The progression he describes in the article ("fed up working for a big company" -> startup) is probably his own as well.
- neurotech1 16y agoI know several established engineers at Google. One recently invited me to tour the GooglePlex. My host did express some frustrations, but I don't believe that the blog post presents an unbiased view of life at Google.
- helmut_hed 16y agoYes. However the poster is just describing, honestly, what life in the trenches at a big company is like. It shouldn't be a surprise that Google is this way now. Large organizations behave in certain ways because of human nature, and GOOG is no exception. Actually I found myself thinking "that's not so bad..."
- aarghh 16y agoThis is good advice for any large company, not just Google. Tips #3 and #4 are key - I would prioritize those higher than #1 and #2. In short - make sure your manager/leader is capable of pushing you; make sure you get to work on visible projects; and optimize your time to make contributions to the more visible projects. One of the things I wish someone had told me a long time ago.
- mikeryan 16y agoYeah but I think most people see working at Google as all unicorns and rainbows. Its a bit disheartening to find out that in someways its not.
- alain94040 16y agoI was expecting one more "google is great" love-post. It was anything but. If you are dreaming of joining Google, this is the article to read. Really.
- Husafan 16y agohttp://xkcd.com/192/ http://xkcd.com/192/ http://youarenotsosmart.com/2010/06/23/confirmation-bias/ http://youarenotsosmart.com/2010/06/23/confirmation-bias/ For people that already have misgivings about interviewing for a position at Google, I'm sure this post was a god send. I mean, after reading all those "google is great" love-posts, you read one that points out flaws, and all of the sudden that's the one to read? All the others go out the window? How does that work?
- Confusion 16y agoAll the others are repetitions of the same positive points. This is one of the first one to list many negative points. This is an awesome reality check for anyone considering to apply at Google: they are just like any other large company, in that you need to be weary of managers, because their goals often don't coincide with yours.
- piaw 16y agoGoogle is still the best big publicly held company in the valley to work for. I wrote this to guide the thousands of Googlers they'll add this year. Having said that, I've been at well functioning startups, and I've been at Google. Google when I joined was better than many many startups. Google when I left was not so.
- moultano 16y agoWhat I've noticed at Google is that there's really no comparison between teams. Different parts of the company might as well be entirely different companies, aside from a few common cultural attributes (flat hierarchy, data driven decision, and of course all the perks.) The best piece of advice in there (I think) is to pick your team carefully, and more importantly, don't feel shy about switching if you aren't making headway.
- mcknz 16y agoIt's official: performance review sucks everywhere.
- arvinb 16y agoYes, one would immediately think that the items he listed are somehow all true at large companies.
- deleted 16y ago[deleted]
- moultano 16y agoAutomate as much of the maintenance as you can.
- brown9-2 16y agoAre there any of these tips that stop being true if you substitute "Google" for any other large tech organization?
- bajsejohannes 16y agoSo what is the effect of promotions? The article hints at one thing: Higher salary cap. Are there other things? So far in my own career, I have recognized a few situations where I could choose to climb the career ladder. In all of those situations, I have chosen not to. The new responsibilities did not seem to be worth it. I believe I have a much more interesting job as a consequence, and as far as I can tell, my salary has not been hurt noticeably (I do fight for my pay rise). Do you really have to add "flare" to your title in google to be successful? Makes me not want to work there.
- jeebusroxors 16y agoHad to look up "SRE": SRE: Site reliability engineer SWE: Software engineer
- ciupicri 16y agoIt seems that I should have answered acronyms to the "Ask HN: What annoys you?" question[1]. [1] http://news.ycombinator.com/item?id=1560796 http://news.ycombinator.com/item?id=1560796
- anr 16y agoYes, we should complain to the AAAA. The tried and true American Association for Acronym Abuse can help there.
- wan23 16y agoThough remember, this post was aimed at Google employees, who should know what these are.
- illumin8 16y agoThis confirms my suspicions - SRE are looked at as inferior or "second class citizens" compared to SWE. It also confirms some of the interviewer bias I experienced (I interviewed for an SRE position).
- dpritchett 16y agoIt's a measurement issue rather than a value judgement. Reliability is "sales we didn't lose due to downtime" while software is "new sales we couldn't have made without THIS GUY RIGHT HERE!".
- btilly 16y agoIt is worth noting that Piaw quit Google, and so is biased by that, and the experiences leading up to that. And internally lots of people have found lots of things to disagree with about specific items on his list. There are others that there have been pushes to improve on since. So take all of it with a grain of salt. That said, he does have a lot of experience, so you shouldn't lightly disregard what he says either. But, more fundamentally, ask yourself what your goal is. If your goal is to move up the ladder as efficiently as possible, his advice is probably pretty good. If your goal is to enjoy your job, everyone will like you better if you feel free to disregard whatever doesn't fit who you are.
- neurotech1 16y agoMy host at Google for my recent tour did say that engineers have limited say with HR and external hiring - which was one of her frustrations. I think this post skips a big part of the experience at Google. One important use of the 20% time is to check out other areas and projects within Google. If you like the project, consider requesting a transfer to that project.
- piaw 16y agoYes. The advice was given to help people move up the ladder, grab the brass ring, and get the big payout. If you want quality of life, that advice is not for you. Then again, if you want quality of life, and money is not that important, I think that a good startup is hard to beat.
- nostrademons 16y agoIf your goal is to get the big payout, what the hell are you working at Google for? Most of the people that got the big payout from Google joined...right around when you did, or a few years before. Your odds of becoming an executive at Google are far lower than they are at succeeding with your own startup and getting bought out for big sums. If you want a big payout, you're much better off working for Google for a couple years to build experience and a reputation, quitting and founding a startup, and then getting reacquired by Google in a $5-20M talent acquisition. Most people I know at Google are there because they want to work on interesting technical problems without dealing with all the bullshit that comes from running your own business. Google is still very, very effective at that - quite possibly the best place in the world for an engineer that wants to do cool stuff, launch to millions of people, and not push their way through lots of hassles.
- moonhorse 16y agoThis is very similar to the big company that I work for - we use "visibility" instead of "high profile" though. :) So I suppose when company grows larger, it is inevitable. You just need to adapt to that or leave if you can not stand it. Also, the team and manager you have has big impact on your experiences. I do not believe there is a perfect environment.
- fs111 16y agoWhen reading this I feel like a 1950ies rocket engineer reading about how bad a warp-drive really is...
- kenjackson 16y agoI thought at Google most people, regardless of salary or rep, were just "Software Engineers". If so, how do people know you got a promotion?
- frognibble 16y agoSoftware engineer is the generic title for a number of levels: software engineer II, software engineer III, senior software engineer, staff software engineer, senior staff software engineer, and so on. I heard that the job titles for engineers above a certain level are shared publicly with in the company.
- deleted 16y ago[deleted]
- piaw 16y agoGoogle has a software engineering ladder. It was introduced in 2002-2003. Many old-timers considered it Google's biggest mistake. Past a certain point in the ladder, promotions were a big deal and those who got promoted to that point got it publicly announced. Past another point, the CEO himself announced it in a company-wide e-mail.
- vsiva68 16y agoThis post has to be taken in context of everything else that Piaw has been saying for a while: Google is an excellent place to work. It may not be as nimble as it used to be, but it is still better than most other big companies and most other startups as well. Sure, it is not _the_ best place, but it is right there at the top. Once you keep that as the background for the article, then you realize that the article is meant for Nooglers interested in a certain career path. It is not for everyone, but it is certainly the most common expected path for the majority of their engineers. It is odd to see HN jumping to conclusion reading one article without any background. I think thats part of the reason why bloggers stop blogging because whatever they say is taken to mean something else.
- piaw 16y agoThanks!
- known 16y agoEverywhere mid-management strategy is Heads I Win. Tails You Lose.
- taloft 16y agoMost of this advice is (unfortunately) true in large companies. It's sad that the idealism of our youth is corrupted by the reality of survival/prosperity in the workplace.
- sabj 16y agoThere is a lot of helpful context that could theoretically be added to an article like this, which would obviate a lot of the "wow, so depressing" or "Google has succumbed to the times" comments here. Alas, for confidentiality reasons, such cannot be shared :| Suffice is to say, do be sure to take this as but one data point of many :)
- aaronkaplan 16y agoHas anyone read Piaw's book (linked to in the last sentence of the blog post)? Do you recommend it?
- shalmanese 16y agoI have and it's excellent. Short, to the point and contains a ton of invaluable information I never found anywhere else.
- escape 16y agoFormer Googler here. I left a few months ago after four years. I have nothing but great things to say about Google. I loved my job, the environment, the people, the perks, the feeling of being privy to the most closely held secrets in Silicon Valley. Most of all, Larry and Sergey, who have always - always - kept their employees at the top of their priority list, even after the company went public. These guys really mean "Don't be evil", but you need to work at Google to really understand what this means. Why I left? Career, mostly. I had reached a point where it was hard for me to get promoted. I could have settled for an easy job that is very well paid but without much hope of going much higher. A lot of people are okay with this and I was for a while, but then I realized I wanted more. If things don't work out at my new gig, I'll try another gig. And if this doesn't work out either, I'll go back to Google in a heartbeat. Keep an open mind, if you get a chance to interview, take it. If you get a job offer, take it, even if it's just for a few months. At the end of the day, the only person who knows what's best for you is yourself, not a blogger, nor an anonymous Hacker News commenter.
- elblanco 16y agoSounds like any other big corporate organ grind -- self promotion and working on high profile, corp important tasks gets you up the ladder, keeping the engine running just keeps you on the ladder. The sexy just wore off for me. Meh.