Occasionally I'd see memes or posts from other teams that described business practices I couldn't believe (like, "I have to stay at the office until my manager leaves or I'll be fired, and he doesn't leave until 8PM so I dont' see my family much") which didn't make sense until I learned that entire teams were H1-B visas reporting to managers who applied caste in their jobs in the US.
Absolutely nothing I've seen compares to borg or a full TPUv4 cluster.
There was definitely a decline over the years, I was probably lucky in that the teams I joined (Infra, Gmail, AI) were run mostly by engineers and pretty cool people.
The upsides are that the business has grown mightily and Cloud is now almost exclusively market driven, at least on core products/services. The downside is that he broke the culture and alienated thousands of googlers whose advancement opportunities were essentially eliminated. Because of the hiring needs, the bar is much lower now, cronyism is prevalent, and politics+bureaucracy get in the way of progress.
During my years at Google, I sat in The Quad, Tech Corners, Moffett Park, and then back at Tech Corners, and spent time in many of the rest of the bay area offices. I will state with confidence that the Cloud offices do not feel "googley" when you walk around the cube spaces. There are few decorations, no buzz, not many people who appear to be enjoying themselves, very few tech talks, guest speakers or events, etc. Just taking a walk around the MP, Matilda or TC campuses and then visiting YT in San Bruno or one of the Android teams in MTV is a stark difference.
Cloud is not googley. Let's see if the consumer-oriented PAs can keep that alive.
At IBM and Oracle, I'd regularly be in meetings with shouting matches. People were tear down others. There was excessive territorialism. Googley culture, although it changed over time, did promote cooperation and constructive criticism. Post-Mortems emphasized what went wrong and what could be done better, not who went wrong. Other teams were often, if not always, eager to partner or share their work.
Work location flexibility, the cafes, all of it was very good.
Now, I did perceive a cultural decline, I think it was sometime around the launch of Google Hangouts, I started sensing a more bean-counting approach, I think because the Seattle office brought in a bunch of MS managers in too short a period of time for them to absorb Googley culture. At one point, the initial launch of Hangouts didn't have presence indicators, and when employees brought it up, one response was "You are not the audience". As if presence indicators are something only elite engineers want, and not regular folks. This was totally antithetical to way products like Gmail were built, out of personal desire and need.
I didn't work in Cloud, but I suspect Thomas Kurian brought a more Oracle "Sales Engineer" driven approach, and that too can change culture. Might be bad for culture, but good for external customers.
One of the issues over the years that I feel an acute sense of now that I'm looking for a job again, is that Google invented a lot of technology early internally, from Borg to Map/Reduce/etc. Eventually, the outside world cloned these, and when they became on-par and standardized, at that point I really think Google should have switched their internal stack to the OSS equivalents. For example, Google still builds products on the internal Borg system, rather than using GCP/Kubernetes/Terraform/etc. If GCP/Kube is missing functionality to run say, Maps or Gmail, then perfect, that indicates a good driver for improving the external facing product. Working on some of Google's tech stack feels like an alien world compared to working on stuff outside.
In ML at least, there's synergy, as Tensorflow and JAX are used internally and externally. But in terms of major systems, there needs to be a lot more of this. Blaze was opened as Bazel way too late for example, should have been done years ago.