Ex-Googler here. I'm not sure there is one answer to your question.
The culture of your org is 100% dependent on where you are, and primarily flows from your Director. This is both good and bad.
The good: You can have islands of positive culture inside otherwise problematic organizations, provided the Director sets that positive culture and makes sure their managers and leaders help enforce it.
The bad: You can be one re-org away from that positive culture going away. That said, I experienced many higher-level re-orgs that people basically considered no-ops because our Director didn't change, and I know of orgs that have had good culture for over 10 years.
If you are considering a role in some part of Google (either as a new hire or an internal transfer), you should ask probing questions about the organization itself to try and understand its specific culture and how that culture is embraced by the people inside it.
> If you are considering a role in some part of Google (either as a new hire or an internal transfer), you should ask probing questions about the organization itself to try and understand its specific culture and how that culture is embraced by the people inside it.
A bit easier said than done, when there's a bad director no one is going to tell you in the interview. On the other hand they are unlikely to praise them either, so you can pay attention to the omission if your questions are specific enough.
You can find out the information you want without asking "How do you like the Director?"
For example, you can ask:
How does the Director support the organization? How do they support their reports? Have you seen them "go to bat" for the org (or someone in the org)? What did they do?
How long has the Director been leading the organization? How long have the senior leads been in the organization?
Are longer tenured people sticking around, or are they moving on to somewhere else? Etc.
Don't ask if the Director is good. Look for the artifacts of having a good Director.
Kinda sad that LLM's let me build little projects that would take a week in an hour, yet Google still isn't releasing much new or different, or even fixing bugs faster.
Mr boss man needs to uncork Google's 'labs' culture.
I completely disagree. If you do the architecture and review the work, they can do bulletproof production work.
I have them review each other’s work before I review it, and they also do security audits of the entire codebase on a regular schedule.
For frontend work especially, the productivity boost is insane. Claude built me a replacement for a complex UI that took a human developer 6 months to build poorly, and Claude did it in two hours.
I’ve been building websites for 30 years and have been architect- or CTO-level at web startups for 15 years. I’ve done all of this painstakingly myself many, many times. I know whether Claude is good at it or not.
> For frontend work especially, the productivity boost is insane. Claude built me a replacement for a complex UI that took a human developer 6 months to build poorly, and Claude did it in two hours.
It sounds incredible if the UI already existed in some shape, and it took a developer 6 months. With Qtcreator one could build UI full UI in 2 days if the wireframes or a UI already exists.
>"We just let the LLMs rip and spend most of our time in the sleeping pods or the buffet. Six figures for days of relaxation. It truly is the good life."
There was a sweet spot in mid-2025 where this was actually the case; Claude Code early adopters could complete sprint work in their sleep while the rest of the world (management) hadn't caught on yet.
Now it's just "oh, this should take you guys a day, right?"
You go there every day, and they give you money. It's not great but it's just a job after all. It's quite weird because they expect you to do something for at least 20 hours every week, sometimes even more. It's not easy to keep up.
They made me come in on a Wednesday last week, and I was like "Whaaat?", I'm not doing that for 250K/month, like are you kidding
The culture of your org is 100% dependent on where you are, and primarily flows from your Director. This is both good and bad.
The good: You can have islands of positive culture inside otherwise problematic organizations, provided the Director sets that positive culture and makes sure their managers and leaders help enforce it.
The bad: You can be one re-org away from that positive culture going away. That said, I experienced many higher-level re-orgs that people basically considered no-ops because our Director didn't change, and I know of orgs that have had good culture for over 10 years.
If you are considering a role in some part of Google (either as a new hire or an internal transfer), you should ask probing questions about the organization itself to try and understand its specific culture and how that culture is embraced by the people inside it.
A bit easier said than done, when there's a bad director no one is going to tell you in the interview. On the other hand they are unlikely to praise them either, so you can pay attention to the omission if your questions are specific enough.
For example, you can ask:
How does the Director support the organization? How do they support their reports? Have you seen them "go to bat" for the org (or someone in the org)? What did they do?
How long has the Director been leading the organization? How long have the senior leads been in the organization?
Are longer tenured people sticking around, or are they moving on to somewhere else? Etc.
Don't ask if the Director is good. Look for the artifacts of having a good Director.
Although I have also heard that morale overall has tanked across departments especially after multiple round of layoffs.
Mr boss man needs to uncork Google's 'labs' culture.
They are useful! Just not the 1000x return you get on a tiny thing or the 100x return you get on a small thing.
I have them review each other’s work before I review it, and they also do security audits of the entire codebase on a regular schedule.
For frontend work especially, the productivity boost is insane. Claude built me a replacement for a complex UI that took a human developer 6 months to build poorly, and Claude did it in two hours.
A replacement for a complex UI that would take a human developer 6 months to do is indeed something I would consider a small project at this point.
It sounds incredible if the UI already existed in some shape, and it took a developer 6 months. With Qtcreator one could build UI full UI in 2 days if the wireframes or a UI already exists.
Gee thanks, AI dude.
There was a sweet spot in mid-2025 where this was actually the case; Claude Code early adopters could complete sprint work in their sleep while the rest of the world (management) hadn't caught on yet.
Now it's just "oh, this should take you guys a day, right?"
They made me come in on a Wednesday last week, and I was like "Whaaat?", I'm not doing that for 250K/month, like are you kidding