Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Facebook Programming Businesses Technology

Facebook Rejects Female Engineers' Code More Often Than Male Counterparts, Analysis Finds (theverge.com) 450

According to The Wall Street Journal, female engineers who work at Facebook may face gender bias that prevents their code from being accepted at the same rate as male counterparts. "For Facebook, these revelations call into question the company's ongoing diversity efforts and its goal to build overarching online systems for people around the globe," reports The Verge. "The company's workforce is just 33 percent female, with women holding just 17 percent of technical roles and 27 percent of leadership positions." From the report: The findings come in two parts. An initial study by a former employee found that code written by female engineers was less likely to make it through Facebook's internal peer review system. This seemed to suggest that a female engineer's work was more heavily scrutinized. Facebook, alarmed by this data, commissioned a second study by Jay Parikh, its head of infrastructure, to investigate any potential issues. Parikh's findings suggested that the code rejections were due to engineering rank, not gender. However, Facebook employees now speculate that Parikh's findings mean female engineers might not be rising in the ranks as fast as male counterparts who joined the company at the same time, or perhaps that female engineers are leaving the company more often before being promoted. Either possibility could result in the 35 percent higher code rejection rate for female engineers. When contacted by The Wall Street Journal, Facebook called the initial study "incomplete and inaccurate" and based on "incomplete data," but did not shy away from confirming Parikh's separate findings.
This discussion has been archived. No new comments can be posted.

Facebook Rejects Female Engineers' Code More Often Than Male Counterparts, Analysis Finds

Comments Filter:
  • Maybe (Score:5, Insightful)

    by JustAnotherOldGuy ( 4145623 ) on Tuesday May 02, 2017 @05:44PM (#54344475) Journal

    "Facebook Rejects Female Engineers' Code More Often Than Male Counterparts, Analysis Finds"

    Maybe it's just not as good, unless every female programmer signs it with "Coded by a Female Programmer!" That, and the little hearts above every lower-case "i".

    • by Anonymous Coward on Tuesday May 02, 2017 @05:57PM (#54344587)

      Bias and discrimination exist.

      What also exists is people who do shitty work.

      Unfortunately, in the world of the feminist SJW, only white males are capable of doing shitty work. In the alternate universe of the feminist SJW, women and minorities are incapable of doing shitty work, and to claim any differently makes you a racist, sexist misogynist pig .

    • by ghoul ( 157158 ) on Tuesday May 02, 2017 @06:11PM (#54344671)

      Facebook has a manadate to hire more Female Engineers. As far fewer Female Engineers graduate than other Engineers one way to get the Quantity desired is to lower the Quality. Once you are letting in lesser Quality Engineers and then vetting their checkins at the existing standards its expected that more of the checkins will be rejected.
      I just hope code review standards are not lowered in order to avoid emotional trauma.
      What's next? 50% of surgeries have to be done by female surgeons?
      The President needs to be Female 50% of the time?
      50% of combat casualties need to be female?

      • Re: (Score:3, Interesting)

        by vux984 ( 928602 )

        I just hope code review standards are not lowered in order to avoid emotional trauma

        On the other hand, I'm sure you'd agree that raising the standards for men until the reject rate is equal for both genders will result in even better code quality overall right? See... we can frame it either way.

        The more important issue is whether the review standards are currently being applied equally or not. They should be.

        It -might- be that the pool of women isn't as good at coding as the pool of men... especially if they have been 'stuffing' the ranks with diversity hires. In which case the best soluti

      • by rtb61 ( 674572 )

        Now factor out the failure rate of retaining lower quality programmers to maintain gender numbers ie people who would normally be let go and then you get more code check in failures. Think more bad male coders fired and no bad female coders fired to maintain gender numbers and code rejection numbers blow out big over time. Not that bad coders were retained long term, just likely that bad coders where given much much longer trial periods based upon a gender bias.

    • by Anonymous Coward

      Have to concur here. Maybe, just maybe, the women hired by Facebook as coders just can't code as well as the men. 33% female workforce in a male dominant industry is actually a lot. So maybe some of the women were hired just to add to the diversity roles instead of actually being good programmers.

    • Re:Maybe (Score:4, Insightful)

      by msauve ( 701917 ) on Tuesday May 02, 2017 @06:44PM (#54344879)

      unless every female programmer signs it with "Coded by a Female Programmer!"

      Exactly how does a code reviewer know the sex of the code submitter, which would be a prerequisite to any claim of bias? I'd guess the only way would be a real name was attached to the submission. But why should that be the case? Why not anonymize submissions? If it's felt there is a need for reviewers to know the past quality of submissions for a each submitter (but why, isn't the review supposed to judge the current submission?), have the system show a quality metric (% of submissions accepted?).

      Is there any real need for submitters to be personally identifiable to others, besides perhaps via a back-end system only available to management?

      • by Dog-Cow ( 21281 )

        Have you ever programmed in a professional environment? Have you never used source control? The name is attached because that's important metadata for any changes to the code.

    • Re: (Score:3, Informative)

      by PopeRatzo ( 965947 )

      Maybe it's just not as good

      Back when having women in orchestras was rare, there was a similar belief as to why they weren't given jobs after auditioning. "Maybe they're just not as good as their male counterparts." or, "Women probably just don't have the strength to (blow a trumpet, hold a cello, play percussion)". You would hear, "It takes a lot of stamina and commitment to be a great musician, and women just don't have it."

      That was the prevalent belief in the professional music world until orchestras st

      • Re:Maybe (Score:5, Insightful)

        by Imrik ( 148191 ) on Tuesday May 02, 2017 @10:28PM (#54345793) Homepage

        So maybe instead of going public about how Facebook is biased against women they should instead get them to start doing blind submissions, and only go public about it if they refuse or the data holds true.

      • Maybe it's just not as good

        Back when having women in orchestras was rare, there was a similar belief as to why they weren't given jobs after auditioning. "Maybe they're just not as good as their male counterparts." or, "Women probably just don't have the strength to (blow a trumpet, hold a cello, play percussion)". You would hear, "It takes a lot of stamina and commitment to be a great musician, and women just don't have it."

        That was the prevalent belief in the professional music world until orchestras started holding blind auditions. Now women make up more than 50% of professional orchestras.

        Occams razor applies. Rather than invent an elaborate reason for why the code is getting rejected, the simplest explanation encompassing all facts is that the code is crap.

        Maybe... just *maybe*... the simpler "diversity hires didn't work out too well" explains the situation better than "patriarchy conspiracy theory"

        Remember that each "diversity hire" replaced someone who would have been hired solely on merit. It's not unreasonable to expect this outcome, and yes it was even predicted multiple times, on /.

    • Re:Maybe (Score:5, Funny)

      by poity ( 465672 ) on Tuesday May 02, 2017 @09:30PM (#54345563)

      A: This code works, let's add it to the proj...
      B: WAIT WAIT WAIT, did you check the genitals?
      A: Not yet
      B: *disapproving look*
      A: Okay, give me a minute *runs off*
      [10 minutes later]
      A: *pant pant* ... It's... *pant* a vagina
      B: *right click, delete*

    • Maybe it's just not as good...

      This is the most obvious and likely correct reason: in order to get a 17% female tech workforce, facebook must be scouring the earth to find females to hire in the name of gender diversity, because universities just don't graduate a high proportion of female CS majors. And that is because female's aren't choosing careers in that area.

      When you are hiring people just because of their gender, this means that people who are manifestly inadequate to the task at hand will get their code rejected more often.

  • by minogully ( 1855264 ) on Tuesday May 02, 2017 @05:46PM (#54344495) Journal
    If Facebook started hiring lots of women just for the sake of having more women in the workforce (to meet some gender diversity quota) rather than based on the individual's skills, then it's likely that the average talent of the women in Facebook would be lower than their male counterparts. Taking this further, it seems likely to me that these women would also have their code rejected more often.
    • That could be a result of trying to rush things. You can't rush diversity, opportunity to learn needs to be built into every level of the education system. Trying to shoehorn some quotas on at the output end of the pipeline isn't going to end well. It needs small and consistent help all the way through so the graduates you want are actually ready to hit the ground running.
    • by El Cubano ( 631386 ) on Tuesday May 02, 2017 @06:05PM (#54344629)

      It also equally likely that their diversity efforts have resulted in a lower overall experience level for their female engineers. Tech has always had a smaller proportion of women than the general population. If they all of a sudden said "let's hire lots of female engineers," and there are not as many experienced female engineers to poach from other tech companies, then you have to hire newbies and other less experienced folks and train them up.

      Have you ever worked with a new or inexperienced engineer or programmer? They tend to write lots of crap code because they lack experience.

      Of course, we don't know for sure because the word "experience" appears neither in the WSJ's article nor in The Verge's article. Gee that seems like the sort of basic thing that a study like this would consider.

      • Of course, we don't know for sure because the word "experience" appears neither in the WSJ's article nor in The Verge's article. Gee that seems like the sort of basic thing that a study like this would consider.

        depends on what dataset you're trying to use to put forward the statistical result that supports your narrative.

        Lies, damned lies, and statistics (and all that jazz). Hell, if it really is an experience thing (likely given the article *does* mention that the rejections seem to align with rank of the coder, and women are at lower rank on average there) then by omitting that in your model means you don't even have to get outlandish with your p values. :p

      • by Shados ( 741919 )

        Yup. My current employer, while pushing hard for diversity, is doing pretty good at pushing to improve the company to attract said diversity, instead of just widening the net and bringing whatever they catch.

        We have a pretty high ratio of female engineers (and even better ratio at the lead/director/vp level) for the kind of company we are. Not 50/50, but higher than the Google and Facebook of the world.

        Pretty much all of the female engineers I've interacted with, including our junior ones, were top notch. H

    • by hey! ( 33014 )

      Or it could be a non-representative sample. Or the difference in rates might not be statistically significant. Or the sample used might be too heterogeneous in terms of content or subject to precisely compare rates. Or women could submit code more frequently and have the same acceptance rate. Or things might look different if you control for submission size.

      It's nearly impossible to tell what's going on with a single aggregate figure like this without access to the underlying data, if not the code in que

    • by anvilmark ( 259376 ) on Tuesday May 02, 2017 @06:35PM (#54344801)

      I have worked in IT for many years and have known some truly stellar female programmers - but I've never worked anywhere with 33% women.
      Based purely on industry statistics they had to bypass more experienced males in order to hire that ratio of females. There are just so many more males in the industry than females.

    • then it's likely that the average talent of the women in Facebook would be lower than their male counterparts.

      I don't think so. More likely is that Facebook *recently* started hiring lots of women, and did so including merit. The result would be a larger portion of junior programmers who are women than men which would likely result in the quality of code being lower not due to skill, but due to experience.

  • More (Score:5, Insightful)

    by Orgasmatron ( 8103 ) on Tuesday May 02, 2017 @05:50PM (#54344521)

    Even worse, the women who weren't quota hires will never be sure if they earned their spot with their vagina or not.

    • Even worse, the women who weren't quota hires will never be sure if they earned their spot with their vagina or not.

      Well, at least some neck-beard got laid.

      • Doubtful, unless these girls are nerds and clearly they aren't since they aren't very good at the programming. So, they hired some cool, hot chicks who date cool guy,s not nerds thus no neck-beard got laid as a result of the bad hire.

    • by Anonymous Coward

      Trying to balance the fact that their vagina doesn't/shouldn't matter while simultaneously trying to control the world with it.

    • I fail to see how this is flamebait. Crude perhaps, but not flamebait.

      It is a legitimate point. If you've made the decision to preferentially hire based on [trait], then that entire class of employee now is subject to the self doubt of "was I only hired because I had [trait] or am I good enough that I was hired because I am better than average?"

      self doubt can be quite harmful.

      • Crude perhaps, but not flamebait

        I think a few people interpreted it as a sex-for-job comment. Which is odd, because that doesn't usually leave much doubt in either direction.

    • We were hiring a new engineer. A senior manager comes in all excited, my boss and I are sitting next to each other:

      Senior: So tell me about this _____ applicant. Because she ticks most of the right boxes.
      [she was asian and female]
      My Boss: Oh did we mention she was a lesbian?
      Senior: Really? [in a super excited voice]
      Me and by boss dumbfounded: No, and if she were we wouldn't ask. We'll let you know who gets through to the next round on merit.

      She was good, but it wasn't the right job for her unfortunately.

  • by WillAffleckUW ( 858324 ) on Tuesday May 02, 2017 @05:56PM (#54344573) Homepage Journal

    The problem for many authors, not just coders, is that both women and men rank them more harshly.

    No matter how you slice it.

    I used to experiment with this by swapping names on code submissions with female colleagues and watching code suddenly be treated differently.

    The cutting critiques were the worst parts.

    Is it fair?

    No.

    Does it happen?

    Yes.

    My advice is find some token replacement method for code submissions so that evaluators can't extrapolate gender.

    • Or, remove any reference to who the person doing the coding was in the first place. You could easily do this in any number of ways. The easiest would be to submit the code to be reviewed, and be handed a secure token so that it can be traced back once the review process is complete. From there, the programmer can get the code back to fix/update or be revealed once code is approved.

      This way Code Snippet has a reference number and that is all the reviewers see.

      But I know that programmers often collaborate and

  • PMD (Score:4, Interesting)

    by hsthompson69 ( 1674722 ) on Tuesday May 02, 2017 @06:03PM (#54344615)

    https://pmd.github.io/ [github.io]

    Use an automated code review to baseline. Compilers care nothing about genitalia.

  • by OrangeTide ( 124937 ) on Tuesday May 02, 2017 @06:08PM (#54344647) Homepage Journal

    I can say confidently that everyone is terrible.

    • Re: (Score:2, Interesting)

      by Anonymous Coward

      Programming is a perfect, if often maddening, example of the creative problem-solving technique. The question, boiled down to its very essentials, is always this: how can I make this (expletive inserted or deleted as you wish) machine do what I want it to?

      There are other, lesser, considerations, of course. The system will invariably impose all manner of restrictions: the memory space isn’t big enough, the language is limited, input-output devices won’t do what you would like them to. These beco

  • by ghoul ( 157158 ) on Tuesday May 02, 2017 @06:26PM (#54344763)

    This study could be used as proof that Facebook is discriminating against male programmers by hiring female programmers with worse coding skills just to meet some "diversity" goals.

  • by slimjim8094 ( 941042 ) on Tuesday May 02, 2017 @06:43PM (#54344871)

    Code review isn't supposed to be about rejecting code, it's supposed to be about improving code and providing another set of eyes with a different perspective. In several years doing code reviews for men and women, and having my code reviewed by men and women (for >1000 overall), I can count on maybe two hands the number of changes that I'd count as rejected - either because the change was unneeded and I was misunderstanding, or because it was needed but I wasn't the person to do it because I wasn't experienced enough with the code I was changing. Many changes go through substantial rework, though as you gain experience you can write better code that needs fewer fixes - so if on average females are more junior (which is true across a wide range of industries and largely responsible for the gender pay gap) then they will on average face greater rework - though on an individual basis they will face less and less as they become more experienced just like everyone else.

    But thinking of - or practicing - code review as adversarial or something where changes can be "rejected" (other than for mundane reasons like trying to change another team's code in ways that don't fit their model of how their code works) is an antipattern. The most senior people, people who literally have invented entire disciplines, still have their code reviewed and change it in response to feedback. My tech lead likes to say that "confusion is a signal" - if your code is so brilliant or clever that it leaves a brand new engineer going "wha?" then it means you have to fix it, regardless of how senior you are, since the code should be understandable by the average employee. And when I review code I don't expect to pass down edicts, and probably 10-15% of my comments receive pushback from the author. It has to be a real problem for me to actually refuse to accept a change - maybe that's happened twice for reasons of code quality and not the mundane stuff I mentioned earlier like "I planned to rewrite how that test worked anyway, let's hold off on this hacky fix since I'll fix it properly". I prefer to chat informally with the author (and, and as an author, vice-versa) to come to something mutually agreeable, which lets me understand their concerns and vice-versa - and we both learn something.

    • by lgw ( 121541 )

      They're probably calling the normal process of commenting on a CR without giving a ship-it "rejection". As in: women upload more diffs than men before getting a ship-it, which may have little to do with code quality (perceived or real) in any way.

  • by LetterRip ( 30937 ) on Tuesday May 02, 2017 @06:47PM (#54344899)

    Or facebook doesn't get enough qualified women applying and thus hires less qualified women for programming jobs because they don't like the gender imbalance.

    This results in the average quality of female engineers being lower - resulting in both women not rising in the ranks and in lower quality patches.

  • What kind of code review system rejects code?

    The purpose of a peer-review system for code isn't to exclude bad code, it's to fix it so that it's good code before it goes in. Maybe when they say "rejects" they mean "receives comments requesting adjustments"? If that's what they're measuring, then I'm still confused. In my experience, assuming you're doing reasonably-thorough reviews, almost every non-trivial change gets some comments, and has to be updated a bit before it can be merged.

  • I know it's not quite coding however it is interesting to apply [youtube.com].

  • This seemed to suggest that a female engineer's work was more heavily scrutinized...

    ... suggested that the code rejections were due to engineering rank, not gender...

    ... speculate that Parikh's findings mean female engineers might not be rising in the ranks as fast...

    ... or perhaps that female engineers are leaving the company more often before being promoted.

    This author seems to be a moron. I suggest that Facebook hires an independent investigator, if this is truly a thorn in their side worth removing. (It's probably not). I wish "news" outlets such as The Verge would not be so quick to speculate...perhaps they're just pushing their biased point of view with no consideration for anything else?

    The odds are that Facebook's men are working longer hours and taking less time off than their female coworkers. Even in the same position with the same experience a

    • by Shados ( 741919 )

      The problem is compound by how free speech is quite dead. Say what you just said openly in a workplace of a semi-famous company. You will get fired faster than you can finish your sentence.

      And yeah, it's basically impossible to control for all factors here. It could be a genuine gender difference (after all, people keep trying to drill in our head that things need to be done differently to attract female engineers, so they have to be different somehow), and it's not even necessarily negative either. It coul

  • by Archfeld ( 6757 ) <treboreel@live.com> on Tuesday May 02, 2017 @08:31PM (#54345327) Journal

    Stop including name, rank, and sex as part of the code or review process. Just review the end product based on efficiency. I worked at a large institution and they hired a far greater % of the female applicants than the males, but still ended up with an environment dominated by younger males. You cant hire those that don't apply.

  • All the evidence indicates that its actually down to the relative quality of their work, yet here we are somehow still "speculating" that it actually _must_ be gender bias.

  • As expected, a lot of people here being all "maybe it's something else". I'd love to see an anonymized dataset online for folks to rate publicly, and see how the results fall out.

  • Every time you hear a story like this about men mistreating or under-valuing women in the workplace, ask the same women how the *women* they work with treat them, compared to the men. You may be surprised to learn that women often mistreat women coworkers even worse than men do, in a great many circumstances. This doesn't justify men mistreating women, but it does mean that men mistreating women is far from the whole picture.

Don't tell me how hard you work. Tell me how much you get done. -- James J. Ling

Working...