Even for the monolingual Google employees it's not uncommon for them to travel to other locales, even as part of their job, so they would be on the receiving end of this "experience" too. We've had 2 decades of experience with this being an issue. One would think that they'd incorporate this "edge case" into their design process matrix by now.

I wouldn't be surprised at all if they one day decided that to have an experience of having no user content automatically translated, you have to pay for the privilege. Call it a multilinguality tax.