[ksenzee]

If you're in the (to me, enviable) position of never building a user-facing feature in a piece of software -- if you purely get to think algorithms all day, and you never draw on any knowledge or experience you've gained outside a classroom or a book -- then who knows. Maybe it doesn't matter what life experiences you've had. I personally have never had a job like that. My interests, personality, experience, and wisdom gained outside of work have always made a difference to what I do.

[yummyfajitas]

I think about user facing features all the time. For example, should we display midpoint estimates, or just stick to credible intervals? Can we give an empirical conversion rate %, or will customers misunderstand and make a bad decision based on it?

But ok, lets say I'm a typical software engineer, building a CRUD app used by banks to set up a new customer with an HSA. What's my unique non-Indian perspective on that?

I can understand how there might be a useful purpose for token diversity on the UX teams for some consumer products. That's an exceedingly small part of the tech world.

[theuttick]

A very, very good answer. However, in this case the diversity the man at twitter should be looking for has everything to do with a person by person case and nothing to do with race.