Live data from Hacker News

We ran the numbers, and there really is a pipeline problem in engineering hiring

blog.interviewing.io

191–200 of 668 posts

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#191
post #128

Honestly for young children I wouldn't want any of the girls to become software engineers. Most Software Engineers including myself are friendly but also grumpy, nerdy and annoying, with poor communication skills and an unhealthy lifestyle. For some reason for men its OK because all they do is work, but for women I'd rather my daughters have more human contact and nicer environment - esp one without developers in it.…

One of the most effective ways to make devs less “grumpy nerdy and annoying” is to inject the dev community with voices that are different. There must be bottom-up pressure for there to be positive change.

I like it being needy and “annoying” (I actually enjoy awkward jokes and general asociality).

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#192

Earlier quoted context omitted.

I've always said women are too smart to become programmers. I'm pretty sure it is better for the soul to have a job with more people interactions. (Yeah I know there are meetings and you have to communicate with clients - still, you end up staring into a glowing screen most of the time. The general work environment often isn't great either. Why would Software Engineers need a nice environment, they only stare at thei…

I get the sentiment, but reread your first sentence. "Women are too ___ to become ___." Doesn't that read as super condescending and prescriptive? I understand it's coming from ostensibly a good place, but it's the same thing as saying "all Asians are smart and good at math." It doesn't matter if the stereotype/prejudice/whatever you call it is "positive", it's still generalization, speaking for a group instead of le…

Women (or any other group) can't speak for themselves about properties of the group. Everybody is just an individual. Statements about groups can only be made by using statistics or at least observance of several members of the group.

If that sentence offends people, I don't know. It is obviously a joke (not implying the opposite, but of course smart people go into programming).

Also, I am sorry, but I am entitled to have an opinion on that matter. You are welcome to challenge my opinion, debate me, present alternate facts, whatever. But you (or anybody else) don't get to tell me that I am not allowed to have an opinion. That's a ground rule I am not willing to budge on. Nobody gets to tell me what to think, or to like.

The second reason (apart from being smart) is that women have more choices/options than men. This is actually well documented, but the article chooses to ignore it because it would spoil their pitch.

All these discussions, by the way, imply that women are stupid for not choosing engineering, and need to be convinced to choose it against their own judgement. Is that really better than my quip about them being too smart to choose it?

Edit: I seem to have overlooked the second part of your statement , or you added it later.

As I said, there are studies showing women have more options - they tend to have talent in multiple fields, and many men only in one. (That's for the studies). Women are also shown in studies to be perceived as more agreeable than men. Another reason they have options is that they have less need to make a good income. And the ultimate option is to have kids and drop out of work that is not entirely pleasant. I personally like Math, but even I find it difficult to voluntarily do Math. So I am not surprised if many people don't keep doing it, when they don't have to.

Also I think drawing cartoons is very different from being an engineer in a Software Company. You can work in cafes. You can stroll the city and draw sketches. You can do such things as a programmer, but it is not the norm - actually you can only make cartoons if you can afford that lifestyle, anyway.

And the bias is different. Employers have tried to put me into ugly rooms several times in my career (basements, windowless rooms, open plan offices). I think for creative work like drawing cartoons, people would be more ready to acknowledge that the artists need a nice environment to get inspiration.

Also, there is the prestige. Being an artist vs being a programmer. Or being a doctor vs being a programmer (70% of medicine graduates are women, but conveniently it doesn't count as STEM for some reason). There are glamor TV shows about being a doctor or a lawyer. How many shows are there glamorizing programming? It has only gained some prestige because some people famously got rich doing it.

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#193
post #108

Earlier quoted context omitted.

Sorry, how are these two arguments equivalent in your mind: 1. There are few women engineers at Google because there are few candidates in the pipeline. 2. women generally having a stronger interest in people rather than things, and tending to be more social, artistic, and prone to neuroticism I don't see that at all. The only way you get there is to assume a common causality. But that assumption (that some people ar…

The argument is: because of 2), less women enter the pipeline that leads to a job that's less social and more about things, relative to other occupations, therefore 1). 2) is presented here as a plausible explanation of 1). The connection is very clear, so the validity of that view depends entirely on the validity of point 2) itself. Damore presented a boatload of links to research supporting that point, and plenty o…

> The concept that men and women may have different interests is considered sexist

The concept that men and women may have different interests due to biological differences is extremely sexist, yes. For all the sources Damore cited, there's an entire body of academic work (and an entire cultural revolution in the United States spanning upwards of a century) to the contrary on that topic specifically. A large chunk of the feminist movement was and is women and men actively working to prove that biology is not a limiting factor in what women can choose to do with themselves.

Had he kept his comments to a realm of "men and women might have different representation in computer engineering because they have different interests on average," he would have been treading on thin ice with people disinclined to assume good faith but could have probably kept his job. Attempting to hang the causality on biology really did him in (and when his memo became public, it put Google in a situation where they ran serious risk of tolerating a hostile work environment if they kept him).

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#194

I'll preface this with the usual "my views are my own" but I do think that diversity in the workplace is a very deep and interesting problem and that we do a major disservice to it by creating ridiculous metrics. I think the most damning metric I see constantly touted is percentage gender; "We aim to have 50% women in the workplace" is a prime example of this. If this is by sexual assignment then even if the value is…

This is a strawman argument.

The goal is not to have 50% women, sharp. The goal is to fix the problem that in the US, where there are 5 men for every woman working in top major software corporations, and those are the ones that supposedly try to improve things.

It's 2019, and yet a company with all-male board was the norm until this year (arguably still is). We are so, so far from any form of reasonable balance that I am not sure which universe your comment applies to.

And yes, what you said matters, as does race, country of origin, and economic background. Intersectionality is a fancy word, but it's useful, and the article mentions it.

So that said, 50% is a useful number. It's useful to say that if the actual hiring rate is at 15%, we still have a problem.

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#196

Earlier quoted context omitted.

How does this level the playing field? Why would this not reduce the overall rate of learning for everyone to suit the needs of the slowest students?

It's a matter of perspective taking. If a "Never saw a line of code until I took this class" sits between two "Coding since 11" students, they're going to watch their neighbors effortlessly breeze through the curriculum. If they don't know those student's background, it's not unreasonable if they come to the (false) conclusion that they're not cut out to be a developer because it's just so much easier for "everyone e…

Even if you do have a "fast" track and a "slow" track, the only ways I can think of to get travelers on either of these paths to the same place at the same time is to either slow down those on the "fast" track, or speed up those on the "slow" track. What I seem to be witnessing is a willingness of people to slow down those on the "fast" track instead of expecting people on the "slow" track to work harder to catch up.

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#197

Earlier quoted context omitted.

The concept that men and women may have different interests is considered sexist I would posit that men and women have different realities, thus different needs. This shapes interests. It's not wholly unassailable, but needs to be approached differently than goals like "achieve x percentage of women in tech" are typically approached.

I'd agree with your observation about different realities, and I think it's woefully underappreciated. I think it only truly clicked with me once I entered a stable, long-term relationship with my now wife - which made me immersed in the daily minutiae of a woman's life, the stories, the perspectives, the concerns, the emotions. It's something that's hard to learn from just brief, casual interactions, no matter how o…

There's also history to consider. Computing was a woman-dominated field until relatively recently in history, which strongly suggests that the root causes of the shift in male/female ratios in technical fields isn't biological (unless there was a massive biological upheaval in the human species in the past 50 years).

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#198
post #132

Earlier quoted context omitted.

And the point of criticizing the criticism of "it's a pipeline problem" is that, wherever you try to improve the pipeline, you cannot expect to make things better than they are at the input of your pipe segment. Working near the end of the pipe, you'll quickly hit diminishing returns. If the input at your segment is biased 4:1, then you can't improve past it. Sure, if your output is 8:1 then it's bad, but you won't g…

> wherever you try to improve the pipeline, you cannot expect to make things better than they are at the input of your pipe segment. But that's basically just complaining that there's no quick and easy fix to your hiring problem. Well, too bad, maybe it actually is a really hard problem that you're going to have to work really hard at for a long time. If there was some relatively trivial solution like "have all hirin…

I don't understand what you mean.

Are you saying that the people who are receiving a biased mix should introduce an opposite bias to counteract it before sending on to the next step, or not?

Possibly I am misunderstanding what a "pipeline problem" refers to.

Wow, I'm experiencing some deja vu. I feel like I already (like, a year or more ago) sent this comment and got a reply, but I don't remember what the reply was.

... Ok, I think this is the thing that doesn't make sense to me: >> wherever you try to improve the pipeline, you cannot expect to make things better than they are at the input of your pipe segment.

> But that's basically just complaining that there's no quick and easy fix to your hiring problem.

I don't understand this response. Saying "It is impossible to do x without doing y or z", saying "That's just complaining that it is hard to do x without doing y or z. Tough, that's what you have to do." doesn't make sense.

Responses that could make sense include "It actually is possible to do x without doing y or z, and that is what you have to do." or "You have to do x, even if it means doing y or z, even though doing y or z is hard".

Were one of these forms what you were saying? (Note : it is very possible that I simply misunderstood what you meant. This is the thing that I think I will probably conclude if you respond.)

The options that I can see for hiring people are: Introduce an opposite bias when hiring in order to counter-act a bias in the input Don't do that, simply work to not introduce any additional bias, and accept a biased result in the output Somehow(?) act in a way that works to make it so that the input received is not biased (or options worse than any of these)

If you are counting "the input" as meaning "the set of people who apply" then I suppose you might be able to influence "the input" by changing where you advertise the position, or things like that, but that seems to me like "potential applicant -> applicant" is just another step in the pipeline, and if the inputs there are also biased, then the same trilemma applies.

If one removes all the bias potentially introduced from each step which one can directly control, then one can no longer directly remove introducers of bias.

And I don't think smalltime company TUV's role is to work to change educational outcomes and the like, and therefore if this and its predecessors are the only remaining sources of bias, I don't see how it is their problem.

That's not to say that those are usually the only remaining sources of bias. I wouldn't be surprised if many such companies do introduce bias which they can and should address, but if the claim is that they should produce an unbiased output despite having a biased input which they cannot influence, then the only thing that can follow is that they should introduce a bias in the opposite direction.

Re: We ran the numbers, and there really is a pipeline problem in engineering hiring

#200

Earlier quoted context omitted.

You're misreporting the very link you quoted. Indeed, the Wikipedia description is pretty fair. I'll quote the relevant paragraph directly: "James Damore was spurred to write the memo when a Google diversity program he attended solicited feedback.[2] The memo was written on a flight to China.[12][13] Calling the culture at Google an "ideological echo chamber", the memo states that while discrimination exists, it is e…

Damore wasn't fired because he argued that the pipeline shortages largely explain gender disparity, he was fired because he made women felt excluded and othered. He wasn't fired because he argued against diversity, he was fired because he threatened inclusivity. To quote: "I’m simply stating that the distribution of preferences and abilities of men and women differ in part due to biological causes and that these diff…

> "Abilities" is the operative word there, as in women, on average, aren't as able

Except that quote doesn't imply that women are less able. You could read it that way if you wanted to be uncharitable of course, but strictly speaking, that sentence simply says that women have different abilities, not lesser abilities. One way that sexism presents itself is an underappreciation of valuable skills, where traits that are typical of the dominant group are recognized as valuable and marked for advancement instead.

This is a standard feminist claim about work place sexism, and so a charitable reading of your quote is basically agreement with the prevailing wisdom.

> Pointing that averages don't imply individual ability doesn't make it better.

Sure it does. If you've made it, then you clearly have the skills required to be where you are.

"6 foot tall basketball players are at a serious disadvantage in the NBA". This is a clear fact. However, height doesn't determine individual ability. This too is a clear fact. Therefore, 6 foot tall players that make it into the NBA should feel reassured that they earned their place.

> he was fired because he made women felt excluded and othered

There was nothing exclusionary about the memo, and "othered" is a meaningless term. He was fired because his memo caused a PR nightmare, and through no fault of his own.

> See also Sundar's quote: "to suggest a group of our colleagues have traits that make them less biologically suited to that work is offensive and not OK

Also not something that Damore claimed. This whole debacle has been a grand exercise in strawmanning.

Post reply on HN