Which to me is more of a sign that the GPL actually works than anything else.
Employees should push for copyleft. Whoever owns the code obviously wants the choice to keep it proprietary, but the vast majority of devs do not own their code.
The only downside I can perhaps think of is a strategic one: endorsing the use of GPL in general and contributing to a healthy copyleft ecosystem, which may be disadvantageous to a giant corporate like Google.
For-profit companies don't like sharing and making the community better if it doesn't make them 10x richer, so they don't like GPL.
Not true at all. You cannot alter license of a library at all if you are not the author. You can select or change license for your own code only.
Of course if you're using a library you're not an author of, the library must already be compatible otherwise you just can't use it.
The only obligations come if a company (or individual) accepts GPL contributions from outside, because they don't own the full copyright any more and have to obide by the licence of the code they accepted from outside.