August 17th, 2024

Postmortem of my 9 year journey at Google

The author reflects on a nine-year journey at Google, noting initial excitement, subsequent challenges, and a desire for new opportunities, leading to plans for a six-month sabbatical.

Read original articleLink Icon
FrustrationEnvyNostalgia
Postmortem of my 9 year journey at Google

The author reflects on their nine-year journey at Google, starting as an intern and progressing to a senior engineering role. Initially excited by the sophisticated technology and the opportunity to learn, the author experienced significant personal and professional growth, acquiring technical and leadership skills. However, over time, the allure of Google diminished due to factors such as reaching financial goals, a shift in interests, and a less stimulating work environment. The author faced challenges including high cognitive load, a lack of growth opportunities, and a disconnect from the company's culture, particularly being outside the U.S. Despite these struggles, the author achieved rapid promotions and enjoyed various perks, including a healthy lifestyle and strong community ties. Ultimately, the decision to leave was influenced by a desire for new challenges and the aspiration to start their own company. The author plans to take a six-month sabbatical to explore new opportunities and reflect on their next steps.

- The author spent nine years at Google, progressing from intern to senior engineer.

- Initial excitement about Google's technology and culture waned over time.

- Challenges included high cognitive load, limited growth opportunities, and cultural disconnect.

- The author achieved rapid promotions and enjoyed various lifestyle perks.

- Plans to take a sabbatical for exploration and reflection on future career paths.

AI: What people are saying
The comments reflect a range of opinions on the author's experience at Google and the tech industry in general.
  • Many commenters express nostalgia for the "old days" of Google, suggesting that the company has lost its innovative edge and is now similar to other large tech firms.
  • There is a divide in opinions about the work culture at Google, with some praising the engineering quality and compensation, while others criticize the stress and challenges of specific roles like SRE.
  • Concerns about Google's impact on society, including sustainability and privacy, are raised, with some commenters expressing strong negative feelings towards the company.
  • Several users share personal experiences of career paths within tech, comparing the benefits of working at large companies versus startups.
  • Comments highlight a sense of envy towards those who work at Google, reflecting on the perceived prestige and financial rewards associated with such positions.
Link Icon 34 comments
By @danpalmer - 8 months
There are a bunch of comments saying that Google is just like any other big tech company and that the exciting engineering bit has gone. My experience is only from the last 2.5 years, but I've got a slightly different take.

Engineering from >10 years ago seems like it was a wild west. Some truly stunning pieces of technology, strung together with duct tape. Everything had its own configuration language, workflow engine, monitoring solution, etc. Deployments were infrequent, unreliable, and sometimes even done from a dev's machine. I don't want to disparage engineers who worked there during that time, the systems were amazing, but everything around the edge seemed pretty disparate, and I suspect gave rise to the "promo project" style development meme.

Nowadays we've got Boq/Pod, the P2020 suite, Rollouts, the automated job sizing technologies, even BCID. None of these are perfect by any means, but the convergence is a really good thing. I switched team, PA, and discipline 6 months ago, and it was dead easy to get up and running because I already knew the majority of the tech, and most of that tech is pretty mature and capable.

Maybe Google has become more like other tech companies (although I doubt they have this level of convergence), but I think people glorify the old days at Google and miss that a lot of bad engineering was done. Just one example, but I suspect Google has some of the best internal security of any software company on the planet, and that's a very good thing, but it most certainly didn't have that back in the day.

By @rr808 - 8 months
I've done the path from SWE to SRE and back to SWE. I was always happy to do production support and diagnose and fix production problems, so I naturally moved to SRE which is always looking for people.

It was a real mistake, SRE is hugely stressful and really unrewarding compared to SWE. Yes you learn some skills and get some occasional glory, but year after year of fighting fires really didn't build any long lasting career.

After switching back to SWE I've finally got promotions and pay rises again, as well as good night sleep and much less stress.

By @p4bl0 - 8 months
I've always wondered if privacy conscious engineers who work at Google do actually use Google's services for their personal lives (Google Drive, Google Photos, Gmail, Google Calendar, Google Keep, Google Docs, etc.)? And if so, do they continue to use them when after leaving the company?

I ask this question here because there seem to be quite some (ex-)Google employees in this thread.

By @atleastoptimal - 8 months
All these things make me envious of people who get to work at Google or any other FAANG company, where they are both paid well and validated for their intelligence.
By @dave333 - 8 months
The traditional view is that young engineers should join startups in hope of a massive payoff if one goes big, but working for 10 years at BigCo with good salary and stock plans can set you up for life without any risk. One path to avoid is the one I took which was to work at a big tech co as a contractor. Good rates but nothing to show for it after 10 years other than the experience and whatever I had put in my 401K.
By @commandersaki - 8 months
I try not to be jaded having never cleared the dreaded google interview multiple times, but I'm very envious of the high compensation, amenities (which their recruiters argue is compensation), and probably getting paid doing very technically challenging work. For me in Australia, it seems to be a case of choose one.
By @incognito124 - 8 months
L3 to L4 in 9months is crazy fast, kudos
By @lysace - 8 months
> USA centric culture, if you are not in USA at Google and don’t have a big presence in a location it’s a bit like swimming upstream, it’s easy to feel isolated, sidelined or on the flipside overwhelmed with late meetings

It's like the fourth time I read/hear this. I understand that it's a tricky one to adress.

By @foobarbaz569 - 8 months
Thanks for writing this! I work on AppEngine / Serverless as a SWE. Nice to see that you worked on it as an SRE and I can totally relate to the cognitive complexity of the systems! :)
By @st3fan - 8 months
You forgot the action items to be moved into the next sprint.
By @markus_zhang - 8 months
The money alone is good enough. I can probably just retire with all those money and stocks. Let alone tons of techs and a shiny CV. Kudos for starting from a height most people can't reach for life. I guess you are going to start another company eventually?
By @KorematsuFredt - 8 months
Having spent some time with Google as SWE, I think Google was by far the best engineering company I have worked with. Even Amazon, Microsoft were terrible when it comes to software engineering.

I am one of those engineers who do not care about culture as long as I am getting paid for the efforts I put in. Google in that sense beat others by HUGE margin.

The engineering work was however very different. We focused on right engineering solutions instead of just business aspect. While that kind of attitude hurts us in short term, it pays big in long term.

By @dvfjsdhgfv - 8 months
> working 60% or 80% were fantastic for my lifestyle and building relationships outside of work

Whoah, it seems fantastic! That alone seems like a good reason to work for Google. Unfortunately, none of the companies I worked for was interested in less than 100%. I told them many times, you can keep your money, I just want to spend 20% or 30% less time at work, but they always insisted on 100%. I have a feeling they would go for 120% if legally allowed.

By @Aardwolf - 8 months
> drastically improved my soft skills

I'd love to know how in a fast paced office environment you can improve those, none of the trainings or anything are about this (even the leadership like ones feel like just standardized template stuff rather than actually have an environment where you can practice social skills and get the correct timely feedback to improve it)

By @cat_plus_plus - 8 months
If you don't enjoy waking up at 4am, work on mobile. Once a new app release is on the phone, nothing is going to make it suddenly break and there is no hurry to send the new release to all users advance, go through internal employee testing and then roll out slowly so that any breakage doesn't affect a lot of users.
By @keepamovin - 8 months
Reading this healed me of my need to work at Google or a megacorp. Cool story, cool journey! Good luck in your next step
By @luckyone15 - 8 months
What in God's Holy Name Are You Blathering About! - my reaction to most of the ideas coming from SRE like 'class SRE implements interface DevOps'
By @georgeburdell - 8 months
Perhaps a condescending take but I think the author got a bit of a big head from getting promoted quickly, and the subtext is that it was due to their amazing technical competence. It’s a noteworthy feat to get recruited out of school, but SRE is a godawful position with high attrition, so it’s easier than SWE to get promoted. That they regret not moving to SWE sooner ignores that SRE is a talent sink and considered a separate ladder by most companies. At this point, the ship has sailed. Eat humble pie, embrace your skillset, and move onward and upward
By @dr_dshiv - 8 months
“earn more money that I could have imagined”

How much, do you think?

By @meiraleal - 8 months
One of the funniest things in HN that I love to "lose" some karma points is to join discussions about/with frustrated ex- Googlers. Google is shit, completely enshitiffied and the engineers there are responsible for that but still when you get to this kind of thread the only thing you see is them praising each other, patting back. Google is gone, my friends. Men in suits destroyed it. Gone is the time that people working there were considered smart, now only the greedy remained.
By @Balinares - 8 months
Holy crap hi! :) Hello from another PD SRE of 9 years. It's been great working with you. Stay awesome!
By @rabbits77 - 8 months
I recently left a job at a very different large company with a similar timeframe (a little under ten years). Pretty much everything this author states is related to my experience.

There is nothing all that special about Google. Maybe there was twenty years ago, but that ship has long since sailed. It’s just another large US tech company. Like Microsoft and IBM before it.

By @usr1106 - 8 months
Some 20 - 10 years ago I was seriously interested in joining Google for many of the reasons he lists. In the end I never applied because at the time they had no development in any country I would have been interested to relocate to.

However, during recent years I have turned into a Google hater. He does not mention any of those aspects. Google is an evil business IMHO. They are an advertising company. The challenges for this planet are sustainability. The goal of advertising is to waste resources. I can type this on a low end phone that soon turns 10. It works perfectly, except that no recent Android version is supported. Google is in the business that cores and memory have been doubled several times since then, for no benefit to mankind. And phones are far from the only category, advertisement is about selling a lot of stuff that does not bring any true improvement in quality of life. Video is one of the worst energy wasters in computing. 90% of Youtube is useless crap, not worth destroying the planet. Nobody would pay a realistic price for it. They are an ugly oligopolist. The list could go on and on...

By @stonethrowaway - 8 months
Light on details and mostly seems to revolve around money.
By @xyst - 8 months
Working at the modern Google seems so overrated. Wonder what it was like in early 2000s when Larry and Sergei were not C-level douches
By @tiffanyh - 8 months
Since this post is about SRE…

Slight OT: what do people recommended for simple server & db monitoring (for a small saas business)?

monit, nagios, victoria metrics, etc?

By @typeofhuman - 8 months
> Tons of money

Lots maybe. But if it's under 8 figures before the dot, it's not tons.

By @cperciva - 8 months
L6 ICs are pretty rare - it already is a top tier of seniority in engineering

Is Google really different from other companies? I talk to a lot of Amazonians (AWS Hero, FreeBSD/EC2 maintainer) and my general impression is that developers below L7 ought to be classified as "Junior" -- my mapping is basically L4-L6 = Junior Developer, L7/L8 = Developer, and L10 = Senior Developer. Anything which doesn't have L7+ involvement gives me major "these kids need adult supervision" vibes for all the newbie mistakes they make.