You have good points. I wanted to highlight a couple bits:
> Google is no better if [...]
Google has significant differences from Amazon, from everything I've heard. And in some ways a better cultural fit for me.
Two Google problems are the forward-facing frat pledging and egos during hiring, and then misaligned careerism by many on the job, with both problems supported from the top. (Well, and the adtech ethics, with a veneer of "California nice" and rationalizing "we're the good guys, so it's OK to do this"; partly mitigated by the veneer being self-fulfilling to some degree.)
I know less about Amazon, but my impression is that the problems are more like (let's call it) "corporate roughness", and the gradual effects of who survives or thrives in that vs. who leaves. But complicated, because not all teams seem to feel that rough side of corporate culture as much as others. On the good side, the company often does great work, and they have some good earlier ideas about engineering and product culture (but maybe coasting or backsliding in parts).
I haven't seriously considered most of the other big tech companies, and I think many of them have much worse problems.
> Having AWS on your resume as a developer doesn’t set you apart from [...]
That's not much of a goal for me. Resume prestige (and also resume-driven-development keywords) are goals for most developers today, though. Too much so. Which I think is a sign of a serious culture problem across our field, and I think it shows in our field's output.
My opinion of Google is great technology, but no product focus with the attention span of a crack addled flea.
My personal “blind man feeling on the elephant” perspective in my corner of the world - cloud consulting - is that when I was an employee of the consulting division at AWS, was that we never saw GCP as a serious competitor. It wasn’t because of the technology. But they had no clue organizational how to talk to the “enterprise” and meet them where they are.
I had a more than even odds in 2023 to work for GCP doing the same thing I did at AWS - making more money - but I was kind of over the big company thing and from talking to people at Google, the same political pro mo culture was there too. Besides they had a return to office mandate for their former “field by design” roles before AWS and working in an office was a non starter for me.
But to your other point, at now 51 years old and on my 10th job, I always have my eye on my next job and keep my resume updated. I love my current job. But facts on the ground can always change.
> Google is no better if [...]
Google has significant differences from Amazon, from everything I've heard. And in some ways a better cultural fit for me.
Two Google problems are the forward-facing frat pledging and egos during hiring, and then misaligned careerism by many on the job, with both problems supported from the top. (Well, and the adtech ethics, with a veneer of "California nice" and rationalizing "we're the good guys, so it's OK to do this"; partly mitigated by the veneer being self-fulfilling to some degree.)
I know less about Amazon, but my impression is that the problems are more like (let's call it) "corporate roughness", and the gradual effects of who survives or thrives in that vs. who leaves. But complicated, because not all teams seem to feel that rough side of corporate culture as much as others. On the good side, the company often does great work, and they have some good earlier ideas about engineering and product culture (but maybe coasting or backsliding in parts).
I haven't seriously considered most of the other big tech companies, and I think many of them have much worse problems.
> Having AWS on your resume as a developer doesn’t set you apart from [...]
That's not much of a goal for me. Resume prestige (and also resume-driven-development keywords) are goals for most developers today, though. Too much so. Which I think is a sign of a serious culture problem across our field, and I think it shows in our field's output.