This is already super weird. If someone is making decisions on who to interview based on the gender/culture of the name they see on the resume and not the qualifications and work history, having them "consider" some additional token candidates is not going to do much. On the flip side, an interviewer that's already trying to be impartial in this situation is going to have to admit candidates he normally would not have based on their qualifications to interview someone "diverse".
And then there's the definition of "white". In practice, a lot of these efforts consider asian immigrants "white" for some reason. Meanwhile a privileged black person from an Ivy League school is not "white" even though they're going to be "white" in every socioeconomic way that matters.
Statically Asians in America outperform "White" people when it comes to education and salaries, which shows the fallacy in the whole white privilege thing. Therefore DEI policies pretend Asians don't exist.
Palo Alto Networks & Arista, Microsoft, Google, Adobe, IBM, Netapp, Micron... Even World Bank has an Indian CEO.
eh, what? Why would US corporate culture give a shit about Hindu castes? Google and Microsoft boards appointed Sundar and Satya, but I don't think those boards could tell a Brahmin from a non-Brahmin.
What evidence do you have that Sundar or Satya used any power network to progress in their career?
Could it not be that being a Brahmin in India was not all that promising to an ambitious young Indian man and in response he decided to start fresh in another country where he had very little in the way of useful network connections?
The less charitable interpretation is that DEI programs aren't being pushed for by Asians and they're designed to help people who look like the people starting the programs.
If HR passes me a stack of resumes then that's who I interview; if all the people HR passes me are white, then I'm left to either assume that these were all the qualified candidates who applied (or at least, to operate under that assumption).
If the process gets bounced back because the stack that was passed to me was filtered by HR's unconscious (or conscious) biases, that forces them to give me more diverse candidates to choose from; the best candidate may still be the middle class white dude, but ensuring that the hiring manager is presented with a broad range of options and not just Chad, Biff, and Troy helps the whole pipeline.
Resumes need to be filtered to remove age, race, gender, name, even what school someone went to. Then ideally the first filtering round of an interview is also completely anonymous, a take home test or a video interview with camera off and a voice filter in place. Heck modern AI tools could even be used to remove accents.
HR has biases, those biases need to be removed.
It only takes a few moments of thinking to realize these techniques are a better way to hire all around. Nothing good can come from someone in HR looking at a resume and thinking "oh that isn't a college I recognize, next candidate."
Apparently, people like to discriminate. Where there are overt markers, there is still a chance that people fear the legality of their discrimination. And when you remove overt markers of discrimination, people look for subtle markers, and those exist, and then still end up discriminating.
End result, even fewer qualified members of the discriminated class gets hired.
Occams razor comes to mind.
If anonymization reduced the representation of certain demographics maybe it doesn't make discrimination worse, but rather you were wrong about which groups are discriminated against?
I honestly fail to how that could happen.
For example, if HR is throwing away all resumes that aren't from an Ivy League, then removing cities and schools from the resume can only help.
I am not even white by the way. I would feel extremely insulted if I found out I was hired to fill some diversity checkbox instead of being hired for being damn good at what I do. I am confident and proud of my skills, which I put a lot of effort to develop over decades. The color of my skin is as meaningless as the color of my shirts.
That's exactly what was happening, and you can imagine the quality of work that resulted in. Now that the tide is turning, that hopefully won't be the case anymore.
You must put up for dismissal 15% of your reports, of those 10% will be dismissed. You may not select any female, ethnic minority, lgbtq or disabled employees.
When the performative beating and meritocracy absolutism collides with the sensitivities of the modern workplace the results are strangely unpredictable.
The memos are tucked away somewhere with my NDA and the memories of crushing peoples hopes, dreams and aspirations.
This sounds like a terminally online Twitter user's idea of how people do hiring.
It's also funny to consider when 70%+ of H1Bs are Indian men. Tech companies just have subconscious bias for hiring both brown men and white men, but not black or yellow ones to complete the Blumenbach crayon set.
This kind of rhetoric is why we're seeing a pendulum swing in the other direction instead of a sane middle ground. But at least it's finally becoming trite to make these claims with a straight face.
Have never worked anywhere there was a shortage of Asian Male engineers.
Not as many Black engineers for sure — but I think that tends to be a society wide workforce problem. In an absolute sense there are less Black software engineers.
I think a lot of these imbalances come down to that. But people don’t want to acknowledge that the majority of software engineers are male, and largely white, Asian, or Indian. But they expect their individual company to somehow solve a society wide deficit.
The point the GP makes - why was the promo/hiring committee unable to find a breadth of candidates - is a troubling but real part of many of our daily lives.
Maybe there weren’t any. That’s usually the reason/excuse given. That should still be a cause for concern.
No department should be vetoing any hire in a different department. Having an engineer veto a hire in the DEI department is ludicrous on its face, but no more ludicrous than having a DEI department tell the engineering team they're not "allowed" to hire a qualified applicant because of their race or gender.
I get it. I don't think a 14 year old looks suitable for a senior role either, but looking past that is the point. You never know what someone can offer.
I normally wouldn’t consider a 14y/o for a senior position. I wouldn’t consider a child to run our armed forces either.
It is you who put women and other minorities into that group with this comment of yours. You are the one to compare being underage and in middle school to being on the same level of a woman.
Your original comment suggests you come from the software industry, in which case you know full well that there are programmers who have been at it for a few years who can program circles around those who have been doing it for 10. Not everyone progresses at the same rate. Years of experience across a wide population will provide positive correlation, but is not anywhere close to being an accurate measuring device and says nothing down at the individual level. To discount someone with less years of experience than your arbitrarily chosen number before you have even talked to them is the very same lack of inclusion being talked about.
Source?
The thing that was harder for me was working with the people hired to run the DEI recruiting programs. I never was able to establish a great working relationship with them even though I was able to do so with a good cross-section of the rest of the organization. Not really sure why tbh.
I was hiring manager at a "woke" (media) company during and after peak DEI.
The only policy of DEI that really affected me was that we had to have a "diverse slate of candidates" meaning, we had to interview at least one woman and (non asian) minority. This was actually a problem hiring engineers because we wouldn't be able to extend offers unless we'd satisfy the "diverse slate" meaning we'd miss out on candidates we wanted to hire while waiting for more people to interview. We could get exceptions but it'd be a fight with HR.
Asians didn't count as diverse because, in tech, they are not underrepresented. Basically "diverse" hires were women, AA, hispanic, etc.
Our company quietly walked back the "diverse slate" stuff years ago. In fact I think it was only in effect for like a year at the most.
The DEI stuff rolling out was highly performative. It wasn't in place for really long and quietly walked back. Now, the loud walking back of policies that probably haven't been enforced in years is also performative. In both instances it's companies responding to the political moment.
Ya, but... what is that impact? Why would a company want to pay another company to make it harder to do basic operations
We would frequently miss out on opportunities to hire qualified candidates because we couldn't make an offer until satisfying the interview quota. By the time we did, the candidate accepted another offer.
I think it's probably a net positive for underrepresented people (it's kind of hard to argue harm to white people when they just get other offers elsewhere that are good enough to accept without waiting), but I'm really not sure if it's a net positive for the company (pre-ipo, still trying to grow a lot).
I suppose this is true, if you believe that hitting the additional quota is entirely performative.
OTOH my company has better representation of women than anywhere else I've worked previously, so I don't think it is entirely performative.
My fringe belief is that giving an edge to buddies of current employees ought to be illegal (at least at large companies) for many of the same reasons why nepotism is frowned upon.
I don’t see why references have to come from current (or past) employees. Colleges don’t make you get referred by alumni, but they do require letters of reference (usually).
On a related note, it’s amusing to me when white men in tech on Reddit get mad about Indian men preferentially hiring other Indian men from their community. I assume that many of these same white men don’t see any problem when they preferentially hire their own friends using the rationale that you gave.
Hiring referrals is great for both problems. The person is already vetted by someone your organization trusts. This is great because a referral is more likely to be someone that knows their stuff and thus pass the interview process. You also have someone vouching that this person is a good employee and not just a good interviewer. The candidate is more likely to accept when they have a contact on the inside that can vouch for the the company and team.
This all assumes that the company is going to do their own independent evaluation of the referred candidate.
Here's what DEI programs actually do in practice, in my experience.
As a simple example, let's say there is an opening for a somewhat senior position, like a director. Your team does some interviews and wants to make an offer. DEI vetos it because every single candidate they interviewed was a white male. They don't tell you who to hire or not to hire, they just say that if you couldn't even find even a single woman or POC to interview, then you didn't look hard enough. Go back, consider more candidates who might not fit your preconceived notion of what you thought a person in that role should look like.
If after interviewing more people you still pick a white male, that's fine. DEI offices never force diversity and standards are not lowered. But they do have an impact - by considering more diverse candidates, that naturally leads to more diverse candidates being hired.
That's just one example of what they do.
You can argue the merits of the specific programs, but it's not true at all to say that those programs are just "puffery".