5 ms·
By the end of my employment at Google I was not working very hard. Probably a few hours a day, mostly doing whatever I felt like doing. My managers consistent
by dekhn 4y ago
By the end of my employment at Google I was not working very hard. Probably a few hours a day, mostly doing whatever I felt like doing. My managers consistently gave me "meets expectations" regardless of how much I achieved or how hard I worked. However, any time there was an emergency related to my function, I had everything required to jump in, fix serious problems, and then get out of the way during the cleanup then contributing my bit to the postmortem.
I could tell there were very few (fewer all the time) people who truly understand google prod, and in that sense, the company seems to be OK with paying top salaries to people who can prevent the company losing lots of money, or other critical prod issues.
- ipsum2 4y agoWere you an SRE? What you described sounds very similar to what I experienced.
- dekhn 4y agoI started as a test engineer on an SRE team (ads database, which I think no longer exists), did a mission control rotation, and then sort of found a way to be a software engineer (non-SRE, which pissed off the SRE leadership) and run my own projects in prod without any real oversight (that was exacycle- using all the idle cycles in prod). I used my knowledge of SRE and my good connections with SRE to run my service with minimal impacts on the $MONEY$ services. Later I did stuff that involved working closely with SRE and hwops but always SRE-adjacent, not part of SRE. I had a standing offer to join multiple SRE groups but chose not to because I can't do oncalls while my kids are still at home.
- EddySchauHai 4y agoWhat are test engineer roles like at Google? I’ve basically only spent my time in startups on critical systems (defense, finance) so have no idea what it’d be like at a larger company or team.
- dekhn 4y agoThis was a long time ago and it was a "bespoke" position created by the SRE team. I set up a continuous build and then fixed bugs until it went green. Test engineers at Google at the time (~2008) were expected to build test infrastructure, rather than writing unit tests (SWEs were expected to write unit tests and integration tests), or to build complex system tests.
- EddySchauHai 4y agoYeah that sounds pretty familiar to my experience! Right now I'm in an infra team and work on the CI pipelines, testing frameworks for devs, testing infra, etc... So more time dealing with docker/k8s than a unit testing framework that's for sure!
- jrockway 4y agoIt's varied. Some posts below describe the standard software test engineering. Test engineers on Google Fiber would buy every microwave and 2.4GHz cordless phone and baby monitor, and see if our changes to interference mitigation algorithms improved or regressed between releases. So you're basically in a lab trying to break Wifi algorithms, probably not writing much code. (Also things like "does our change to move iPhone 6 to 5GHz when it's closer to the 5GHz access point also work with and iPhone 5?")
- outworlder 4y ago> which pissed off the SRE leadership Really? I thought Googlers could move internally with little friction and yada yada. Is that just propaganda?
- izacus 4y agoNo, you can move easily, which is why he could piss off his current leadership without consequence. Being able to move doesn't mean your current manager will be happy about you moving. The "easy" part of the process means that they just can't do much to sabotage you or your future.
- dekhn 4y agoAt the time (2009 or so) it was hard to leave SRE and be a SWE because SRE had a hard time keeping employees given the oncall and nature of the role. My mistake was to tell people it was easy to leave SRE, which the head of SRE didn't like. He called my new manager and chewed him out. To his credit, my new manager told me I wasn't in trouble, but to be more circumspect when dealing with predatory leadership.
- dom96 4y agoI wonder if it's still that way. At Meta it is not, you need to go through an interview loop to move from Production Engineering to SWE (even though the culture at Meta makes PE far more similar to SWE than SRE is to SWE). I bet the reasoning is the same: they don't want to make it easy for folks to move from PE to SWE.
- pram 4y agoI’ve had someone unironically tell me SREs are just people who are too dumb to be SWE so there’s probably more to the gatekeeping than just on-call lol
- carom 4y agoOften times the interesting teams knew who they wanted to fill headcount with. They would say "stop by for an informal chat", then in that chat they would interview you on (e.g.) very niche terminology. After that they would tell you it is not a good fit. Tried to go to 3 different teams on my way out of Google and none of them were interested. I think it is a bit of a status game, like they are looking for a PhD or to justify a visa. Specific examples, an Android static analysis team and Fuchsia security both passed after informal chats (unprepared interviews). I've spent a ton of time in reverse engineering frameworks, malware, and building automated code analysis solutions (with tons of bugs found to my name). When you have that experience, and they bring you on to do front end dev on some internal tool, like there is just such a disconnect.
- aliasxneo 4y agoI have a feeling this extends to several areas in Google. I come from the GDC side of things and have the exact same experience. To keep my job requires very minimal effort on my part. In fact, nowadays I'm punishing myself by trying to do anything "above and beyond." This is mostly due to the rapid growth of committees and the struggle for power that has come out of it (i.e., I'm more likely to be denied by a change control board over political reasons). Regardless, I'm on my way out despite people's shock that I would leave such a "cushy" job. The fact of the matter is that the lack of challenge has actually caused me to spiral into a deep depression and the best decision for me personally is to move on.
- tfandango 4y agoYou post strikes a chord with me. I have found over time that I personally require some mental challenge and some physical challenge to remain mentally healthy. Some days, work provides the mental challenge, the feeling you get by solving difficult problems. If we get too far into the weeds and end up in a constant state of talking about work instead of doing it, things begin to turn depressing until I need to supplement on the side by learning something new or whatever. Same goes physically for me, I keep pretty regular on working out but if I take a week or two off I start feeling sort of sad. Best of luck to you wherever you land!
- hluska 4y agoI hope you’re okay pal. But good on you for recognizing a problem and working hard for a solution!
- olau 4y agoI don't know if you're familiar with the book but "Bullshit Jobs" by David Graeber examined this phenomenon. He found that many people with bullshit jobs are struggling with deep unhappiness. Quit as soon as possible.
- curiousgal 4y agoWhy do you look to your job for challenges. Why not simply look at it as a way to put food on the table and use the rest of your time and resources to seek out other challenges?
- rrrrrrrrrrrryan 4y agoThat's how I think of it. You pay firemen for their ability to solve a problem quickly and efficiently, and for being able to execute when called upon. Giant companies making money hand over fist pay a lot of "don't fuck this up" salaries. The primary goal for everyone is to keep the money printer running smoothly; everything else is secondary.
- z3t4 4y agoFirefighting used to be very lucrative as people was willing to pay a lot to "solve the problem" when their house was on fire. Also one house on fire could possibly mean the whole city could burn down.
- commandlinefan 4y agoIt's worth noting that the beginning, the end and the middle of Scrum and what most companies laughably call "Agile" is to prevent exactly this: the entire structure is there to force every developer to interview for their job every morning and prove they're making "contributions" (it doesn't matter if they're good contributions, they just have to be completed by the deadlines).
- djkivi 4y agoSuch a beautiful metaphor for the daily standup!
- bombcar 4y agoThe key difference is people understand you’re paying the firemen for the emergencies- but a lot of SREs are actually firemen but paid like developers. When everyone is quietly pretending you’re not a fireman but you are it leads do a disconnect where everyone is playing charades.
- trombone5000 4y agoThe people handling the emergencies should get paid considerably more than developers - when they system is down, the real, actual, company-sustaining money stops coming in.
- russellbeattie 4y ago> My managers consistently gave me "meets expectations" That's because his bonus was probably tied to your performance. By making sure all his subordinates receive meets or exceeds expectations, then he looks good. His manager does the same, all the way up the chain. They played the same game when I worked at Amazon. What's more, it became automated. They introduced non-optional surveys that popped up on your computer daily. At first I assume it was a well intentioned system to gauge general employee sentiment. It was annoying and stupid HR bullshit, so of course I immediately went in and disabled it. After a year or so, my manager finally notices and orders me to enable it again. I soon guessed why. Within a few months, we start having quarterly group meetings going over graphs of the answers. And of course, the surveys aren't anonymous, so he would call out the people who gave bad answers and start grilling them about their issue in front of everyone, if they didn't immediately recant, then they would "schedule a meeting". I assume his performance bonus had become tied to the results and everyone needed to tow the line. It was amusing to me how many of the younger employees didn't understand the game they were playing and would continue to answer honestly. I just glanced at the options, picked whatever made my manager look good and went on with my day. You'd think those idiots in charge at the upper management levels would have heard of Goodhart's Law: "When a measure becomes a target, it ceases to be a good measure." But apparently not.
- debug-desperado 4y agoSeems like the feedback would need to be reviewable in a "skip level" fashion for that to work.
- deleted 4y ago[deleted]
- casey_lang 4y ago> That's because his bonus was probably tied to your performance Or they just don't want to take on the burden of getting you to improve. PIPs are a pain for everyone involved. If a manger hands out anything lower than "Meets Expectations", their next step is to help you get there, or gather enough data points for HR to safely see you out the door
- nr2x 4y agoI think it’s actually a good thing to just have a pool of people who know how stuff actually works. Otherwise there could be very key infra that only one or two people fully understand since the code is “mature”, doesn’t need modifications, and nobody wants to work on it. In theory of course, I’m sure in reality the digital world isn’t at the mercy of <200 SWEs who gave up on promo and live in the basement.
- zmgsabst 4y agoThis is an interesting question to me — do software engineers follow a Pareto distribution on their impact? That would imply that around 1,000 SDEs are delivering 38% of the impact in the field. A change in culture which drove out that 0.1% would potentially noticeably drop the UX of “tech”, across the US.
- chaosbutters314 4y agochrome is still buggy, the search bar moves my plugins a little after loading and I end up favoriting an empty page by clicking the star on the search bar. I think Google engineers are highly overrated for such a simple problem to still exist
- jsemrau 4y agoI have never worked for Google and likely never will. Stories like these make me wonder why we put X-Googlers on such a high pedestal. I don't mean that personally in an offence to anyone. It's just a general observation.
- Aperocky 4y agoI did not come away with anything from the story that would make me have a negative opinion on author's technical capability.
- jsemrau 4y agoI didn't see it as negative as well. Rather, it's not special. Not exceptional. It's just a job. It sounds like all the other jobs out there.
- dasil003 4y agoIf you were early at Google it means more as going through that hypergrowth was very difficult and there was less dead weight. But for the last 10 years Google means essentially two things from a hiring manager's perspective: 1) you have decent floor of basic technical ability as no one stupid or a complete faker makes it through the technical interviews (but note it's a low floor as anybody with 100 IQ and reasonably technical mind can probably brute force their way to passing if they want it bad enough) and 2) if you were successful there you can deal well with large-scale system complexity and (likely) the politics of working with many partner teams and stakeholders. It's not foolproof as any given individual, role or team could get lucky in terms of having relatively high agency and fewer dependencies, but on balance anyone L5+ is going to have to deal with a fair amount of that. Given the 15 years of essentially unconstrained growth and moats from any real competition, I think your assessment is largely correct though. The name brand reputation of Google far outweighs the likely strength of any given candidate, especially if you expect execution without limitless resources and industry-leading technical mentors/gatekeepers at every critical juncture.
- origin_path 4y agoThe reputation of ex Googlers was established in the early days when they were tremendously productive, the bar was genuinely very high and turnover was tiny so there were very xooglers to begin with and they were mostly founding startups. Over time Google grew an enormous amount. Productivity dropped through the floor due to endless headcount expansion, the bar did get lower and "I was at Google for two years" became a much more common thing to hear. But first impressions stick so Google still had done of that early day mystique. Source: was at Google 8 years, early days, still have friends who work there. Saw the changes with my own eyes.