Many big tech companies have inclusion training calling this question out as inappropriate on the grounds it provides an opportunity to introduce bias.
Sure, that's advised in interviews, where you're about to make a decision on someone's livelihood, hence the importance of reducing bias. That's a completely different context than in casual conversation at a social event.
In the same lines, don't ask anything. Everything is a bias. ie, What do they do? - Also a bias as they are engineer, or product, or sales, or whatever.
The signage claims the _image_, i.e. the pixels, is deleted but makes no claims about embeddings, biometric measurements, etc that are generated from the image.
> eventually people who have worked at google are going to have more trouble getting jobs elsewhere when all the tools they've worked with are things that nobody outside of google has heard of
This has already happened. Many companies offer dictionaries to translate the names of Google tools to their tools. Open source ones exist as well: https://github.com/jhuangtw/xg2xg
An issue I’ve ran into is startups being very hesitant of hiring Googlers because of a perception that they can’t engineer without other teams of developers supporting all of their tooling. One startup specifically asked how to create a dashboard without using Plx - a wild question given the vast OSS dashboarding ecosystem - but it was still a concern to them.
Referrals are vetted by global teams who are just checking boxes - it's very common to have to reach out to the recruiter for the role directly to resurrect a rejected referral.
Many big tech companies have inclusion training calling this question out as inappropriate on the grounds it provides an opportunity to introduce bias.
reply