It seems like you’re making a couple of key assumptions about what the work environment looks like for the core Golang dev team, and then extrapolating from there to exclude them from your definition of Google’s “ethos”.

Separately, the idea that a manager having influence on a good engineer’s work is “broken” is one I don’t understand.

But I think, based on this comment thread, it’s unlikely we’re going to reach a consensus.