I’m an Ex-Google Woman Tech Leader and I’m Sick of Our Approach to Diversity

"In the name of diversity, when we fill quotas to check boxes, we fuck it up for the genuinely amazing women in tech."

Precisely. This goes directly to the core of the issue and what I had brought up on the thread recently about the Google employee who got fired. Specifically, if companies were truly interested in fairness, the only mandate for the interview process would be to hire the best person, no exceptions. By doing this you treat both sexes fairly and give everyone an equal chance. Otherwise, you end up with "reverse sexism", which the author does not explicitly say, however she does essentially admit to in her description of the hiring loop:

"After some rounds of low to no success, we start to compromise and hire women just because we have to"

The only logical conclusion that can be drawn from that is she hired at least a few women over men which she thought were better candidates simply because "we have to". That's a problem.

Overall, though, I thought her piece was well written and she seems to get at the real issue and even has a possible solution that doesn't involve just hiring women for purposes of optics only - fighting the battle far earlier and getting girls interested young so that they choose to enter these fields at a higher rate than they currently are doing.

I hear you when you say,"the only mandate for the interview process would be to hire the best person, no exceptions". It just sounds like an HR platitude.

If you know how to do that, I actually think you have a multi-$B idea! Unless you mean "cultural fit", or "went to the same school I did" as the best person, I'm doubtful you have one though. I've done enough interviewing and worked with enough people to know that even the best hiring managers turn away good candidates and get a few duds.

Once you're into real hiring statistics you have to be very careful of confirmation bias and "I just like this guy"ism even after the fact... they look and act like your successful hires. It's hard to even say, unless you're personally looking at their work on a regular basis and know what direction they're being given.

> I hear you when you say,"the only mandate for the interview process would be to hire the best person, no exceptions". It just sounds like an HR platitude. If you know how to do that, I actually think you have a multi-$B idea! Unless you mean "cultural fit", or "went to the same school I did" as the best person, I'm doubtful you have one though. I've done enough interviewing and worked with enough people to know that even the best hiring managers turn away good candidates and get a few duds.

Well, make me a multi-billionaire, I now present to you:

BLIND SOURCING AND HIRING

I should only share the details in private, you say it's a multi-billion dollar idea and I'd hate to tip off the competitors.

In all seriousness, though, I know this is challenging. Especially at Google, there's still an opportunity for trouble after you've been hired but not yet assigned; though I doubt it would be enough of a problem to trash the whole system.

The only reason not to do blind hiring is if it produces results which are indistinguishable from standard hiring.

> The only reason not to do blind hiring is if it produces results which are indistinguishable from standard hiring.

Or the fact that it's not really possible. Right now, most software engineering jobs are pretty communication heavy. Almost all company cultures contain a non-trivial amount of verbal communication, so with that premise, it's reasonable to have candidates verbally describe technical things or even make technical arguments.

Once you're listening to real voices, it's difficult to pretend that the hiring is blind.

The famous study involving auditions for positions in an orchestra worked really well because you could hide the person behind a screen and judge an entire work product without knowing anything about the instrumentalist.

Now, if most software jobs include a heavy remote work component some day, it might be more reasonable to throw a somewhat detailed spec at a candidate, have them code up a solution, then show the code (and only the code) to people evaluating the work product. But most devs don't have a day-to-day that looks like implementing textual programming problems for strangers.

> Once you're listening to real voices,

Use a voice scrambler.

thats what i was thinking. Everyone should be made to sound like darth vader and now we've an interview process to die for :P