Wouldn't that be a fully generalised argument against ever hiring anyone who ever worked at Google?

(Btw, some people also leave Google for other reasons.)

If you want people who know how to build stable large scale infrastructure it is hard to go wrong by hiring people from Google. Google rewrites all their products all the time, they shut down and launch new internal systems just as often as they do external, and it is still stable, so the people from there has probably been through a few rewrites of some infrastructure part and knows what are required for that to work.

For some definitions of 'stable'. As a user having to swap apps and lose functionality randomly makes it all feel very tenuous.

Google product decisions (and especially what to shut down) isn't really made by the same people who keep the infrastructure up and running.

> coast along and leverage their past experience to not be dared questioned.

This has not been my experience at all.