Every time I hear stuff like this, I think of that Office Space thing... you don't want the Engineers talking directly to the customers.. well it sounds like the Engineers are also handling all releases and business decisions willy nilly.
Because I have worked with responsible engineers, but it seems like Google is overrun by them there's a lot of really bad business stuff going on. It's like when I think of AWS, nothing on there is named for business people, its all really bad names that IT / Devs come up with.
AWS as a whole is sold to businesspeople, sure, but the individual AWS products are definitely being sold to engineers. S3 and EC2 don't need to have layperson-friendly names, since laypeople don't understand what they are or why one would or wouldn't use them - those are CTO/tech lead decisions.
I still have simpler conversations when talking about Azure services and naming them, they have reasonable names. I never did anything with GCP so I cannot compare, but I assume their naming scheme is also reasonable. It feels to me like AWS was basically they decided to offer some of their internal things externally, nobody renamed anything, and then they just ran with it.