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

Some of the reasoning in this post is very weak.

It's not very long, and its kernel is an anecdote about how her son is interested in programming and her daughter in photoshop. My daughter is also more interested in art than my son (who is more interested in video games). Both would make exceptional programmers, and both have a latent interest. Both are setting a course for STEM careers, but, like all 18 and 16 year olds --- let alone 9 and 7 year olds --- neither has any clue what they're really going to end up doing.

The piece culminates in a recommendation that we focus our diversity efforts on college admissions and earlier stages in the pipeline. But that's a cop-out. We should work on all stages of the pipeline. It's unsurprising that a Google engineer would believe that gender balance can't be addressed without fixing the college pipeline, but the fact is that virtually none of the software engineering we do in the industry --- very much including most of the work done at Google --- requires a college degree in the first place.

Most importantly, though, the only contribution this post makes to the discussion is to add "I'm a woman and I agree with one side of the debate" to the mix. Everything in it is a restatement of an argument that has been made, forcefully and loudly, already. Frankly: who cares?

Edit: I added "some of the" to the beginning of the comment, not because I believe that, but because I concede that there are arguments in the post that can't be dispatched with a single paragraph in a message board comment (through clearly there are some that can.)

I don't see where the author's reasoning is weak. A female tech lead / founder tried the standard way to get better representation of women at Google: try to hire more women, and found out there weren't enough highly qualified candidates to significantly move the numbers in the desired direction. Then as a founder herself, she tried to hire a higher percentage of women, and found there weren't enough candidates. She compared two approaches to fixing that: lowering standards (with negative effects she outlined), and generating more candidates from colleges. She recommends the later approach. The argument isn't novel, but it's also not made in a vacuum or from an ivory tower as she tried the "try harder" approach down in the trenches more than once, and so suggests "try different" instead.

Again: everyone knows the candidate pool is overwhelmingly comprised of men. There's no real dispute anywhere about this fact. It's not part of the debate; there is no debate about it. Nobody can reasonably believe it's realistic to expect parity in hiring in the immediacy, and all the available evidence suggests --- like you'd expect! --- that Google doesn't expect that either.

That makes that part of the argument in her post a kind of straw man.

Doesn't that kind of point to an alternate solution, that the entire interview by interrogation coding process is the problem (if the input pool is 98% men of course they are going to get 98% men out) and they should be doing the mentor approach/internship for all junior programmers instead of the rigid pass/fail requirement. One of the problems with their current approach is similar to the college hazing ritual, all the upperclassmen went through it, so they're going to make everyone else suffer through it as well.

> if the input pool is 98% men of course they are going to get 98% men out

Will they? What if women stay in their roles longer than men? Then, you would less often be replacing women.

If men more often apply to new jobs, that could explain why the candidate ratio is more skewed than the ratio of actual workers.