Opinions are my own.
Either way, at this point I think I've seen enough. I think I should minimize time working and maximize pay. Working remotely for G was pretty great. The work sucked but there was so little of it. If it weren't for mandatory RTO I'd still be there. I'm gonna see how FB compares.
.eq. Return To Office # For anyone else chilling somewhere in the world that doesn’t know that TLA
And I think you just justified mandatory RTO!
I know plenty of people that have left google for greener pastures but also many that stayed. Since my previous team mostly went to other teams within Google we did a lot of talking about leaving and the consensus was that everyone would be fine whether they stayed with Google or decided to leave. "Happy" is a subjective term but everyone I talk to is comfortable and is fine with staying or leaving.
> Everyone was either coasting and depressed/disengaged, or overworked and stressed (I would say 80% were the former).
In a realist sense this one is almost tautological. Either you are trying to rank up or you're not trying to rank up. If you're not trying to rank up you get a LOT of leeway at Google, and you can coast if you want, or you can continue to do good work, as I think a lot of people do. If you're trying to rank up you're going to be busting ass, but I think this is not different than other companies. If you have people delivering impact and people who are not, are you really going to make the case that you should be promoting the less hardworking people? Or that everyone should rank up equally?
> People were frustrated about the bureaucracy, the promo process,
This is constantly brought up on memegen but there are also comments on memegen saying something to the effect of: "Despite our complaints Google is still a great place to work" and I don't think I've ever seen any pushback on this. Compare this to for example Reddit memes where there are zero people saying things are still good despite complaints. Promo by the way is being revamped due to complaints (I think this is public enough that I can mention this) and we'll see how the new process is.
> the slow pace, the meaninglessness of the work an individual IC does,
Despite my past projects falling flat, I personally find my current work important. In general I both agree and disagree with this point. It's 100% true that some people may not be personally invested in the success of the specific projects that they are working on, and I have indicated my agreement with this in a later comment. Where I disagree with this comment though is that people are very invested in project delivery in general, as your are extremely well rewarded for delivering projects. Above the L5-L6 level you will find people are working extremely hard to be impactful. This is maybe where the perception of "overworked and stressed" comes from. I will tell you these people are generally doing an amazing job and are being compensated for this overwork with amazing pay. And when they are getting pay commensurate to the work they are doing, I personally feel that the use of the label "overworked and stressed" needs to be heavily caveated.
> the stress for managers. Even on a super sexy project dealing with cutting edge AI that got tons of press coverage, everyone was frustrated.
I personally have not seen this but I don't dispute it. I have heard other teams have a lot of frustration.
> This company has a serious cultural issue.
This one is entirely subjective, but again I don't dispute this in terms the feeling of ennui at work. Sometimes leadership doesn't seem to have a coherent strategy and work is done for no reason. I can't really define what is "an issue" or "not an issue" culturally. What I can do is make comparative judgements: In my previous startups the culture was much worse, and there was much more of a sense of "what is leadership even doing?". I haven't worked in any places where I've had the sense that things are done better at Google. Others will have to speak to this.
> In a realist sense this one is almost tautological.
While you're trying to say google's not that bad, that you see depressed-disengaged and overworked-stressed s literally tautologically the only possibilities for a work experience does not say good things about google to me. It sounds like stockholm syndrome.
Because it's definitely possible. Just apparently, in your experience, not at Google. Which you've internalized to incorrectly believe this is universal.
The "stockholm syndrome" metaphor is overwrought, you're right, sorry.
I've seen coasting people getting promoted, and hard working people not getting promoted. But you could be hard working and not stressed is my point. I know because I've been there. I've even been there at Google for a short while. I ran a cool project, people were nice, work was interesting, it wasn t stressful at all but it was challenging. Sadly it didn't last long.
Your team and the specific work you're doing matters a lot for your happiness at Google (and presumably any big company). Work with your manager to craft a job description that's better suited for you, or transfer if you can't. You have to actively manage your career - and your happiness - in any job.
Truth.
Think about it this way, everyone who was early at Microsoft/Apple/Google/Facebook/etc has awesome stories of being on the first team in the world to ever try solving some really difficult problems. Exploring unknown new fields of computing, designing new UIs for never before imagined devices. You did super cool things.
It is comparatively recent that FAANG jobs have become sort of lame.
Remember how cool Google maps was when it first came out? Or how awesome Gmail was? Those were ground breaking projects!
Heck we take distributed databases for granted now days, but Facebook pioneered a lot of amazing technology, so did Google, Amazon, and Twitter.
Microsoft actually may have had the right model way back when, back when they had teams and job roles in charge of making new products, and another org just devoted to maintaining current versions of software. Of course that division was easy to make back when software came on CDs. Now days everything is cloud based and evergreen.
Maybe companies need to have a career path that is just "maintain stuff" and your promos are based on how well stuff keeps working and any cost savings/perf improvements you can squeeze out of the existing code w/o doing a massive rewrite.
Mapquest and hotmail were the true trail blazers in that respect.
Back then Google was doing this kind of groundbreaking stuff. Other people had all the technology pieces but Google was kind of the only company doing these things at scale and letting their engineers cook it up and ship it quickly, and in the early/mid-2000s it seemed like they were dropping a new "wow, nifty" type of thing every few months.
From the people I know who were there at the time (I joined later, end of 2011 time frame, right as "the social wars" and the G+ era was happening) it sounds to me like a serious empowered-nerd culture where people just got out of your way so you could do stuff with all the neat tools that were available to you.
That era at Google has ended some years ago now. It's too big, too political (and no, I don't mean "woke" politics, but corporate / promo / perf politics) and if you had a "neat idea" like how, say, Gmail started, you'd have a hell of a time making it happen past the layers of product managers etc.
... And if you work in a codebase like, say, Chromium, you're buried under 50,000 layers of abstraction and the product of very complicated decisions and a massive build that will bog down a machine with a couple dozen cores and 128GB of RAM, and bring any IDE to its knees. A far cry from the breath of fresh air of lightness and speed that original beta Chrome version felt like, with its graphic novel / comic introduction [1] and raw "hey isn't this neat check this out" vibe...
As a webdev a few years ago, the Chromium team was oodles better than anyone else at delivering a reliable browser, and wayyyy better at fixing bugs than any other software team I have ever dealt with in my career (I just submitted bug reports to them, no direct or formal interaction). No idea what they are like now, but hotdamn that team was superlative. I hope it is enjoyable to work there, because the work output was phenomenal.
The codebase is huge. The code quality is on the whole excellent, but learning its ins and outs takes time.
The Model-T was the true trail blazer in that respect.
But I have to say, as a counterpoint, I met many people inside Google who loved it there and were living their best career lives there, and getting treated really well to do it.
It wasn't me, but, there's a personality type that thrives in those environments. It's not all awful. You get to play with some really fancy big tools. Deploy your stuff across thousands of servers or ship a product to millions of people. Sit on the shoulders of other really smart engineers and use the pretty amazing stuff they build (like, seriously, stuff like F1 etc. is pretty amazing).
And if you can play the game there well, and you really want to succeed there, there's lots of room to climb.
Wasn't my game, but let's be honest, there's actually a lot there to go with.
I think this is true of most careers in the US. At the end of the day it's a job, help you provide for yourself and family. It would be amazing if you were in love with every minute of it, but it a means to the end. You hear many NFL players say the same thing, they dont care if they win or lose, it's just their job. They show up, play, get a pay check and go on with their life.