Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Because sometimes that does happen -- where a downsize disproportionately targets a minority group.

Why would a downsize disproportionately target a minority group unless you directly admit that part of your management is racist?



It can happen for tons of reasons. Some coincidental, some were initially benevolent.

Imagine a company with an office in Atlanta, that hires a disproportionately large number of black employees relative to the rest of the company due to the proximity to more diverse engineering talent. Then they close the whole Atlanta office and lay everyone off.

Or

Imagine a minority tech influencer that does a great job of recruiting underrepresented people to the part of the company they work for.

Or

"We're staffing up our test engineering group, and we're making a new junior test engineer program that targets career switchers." => "Hey, we're getting especially good employees from underrepresented groups in this career switching program, let's double down the advertising to these groups." => "Times are tough, engineers can test their own code. Let's axe the whole entire test engineer group."

I'm sure you can come up with your own examples also.


I'm not immediately against Twilio's actions here (though the messaging is pretty bad), but not one of these examples strikes me as a bad thing beyond layoffs being bad in general.

Deciding whether or not to close an entire office should probably not take into account the racial makeup of that office. You either have the funds to keep it open if you don't, because if you now keep the office you have all these other expenses and end up having to lay off even more people.

If someone doesn't meet the bar to survive a layoff saying "oh but they help us hire people with green skin, keep them on!" is pretty blatantly saying "you're not good enough to do your job, but you're a good enough token to keep your job." It's offensive and discriminatory.

Recently hired, early-career/less-skilled, and QA/test are always let go first before mid-career and seniors who aren't at the top of their pay band. If you're at the point of double-digit percentage layoffs, the testing group is a pretty attractive target.

I think the issue I have is that I have no problem whatsoever with examining your hiring (and firing) practices to try to eliminate implicit or unintentional biases against any group - disadvantaged, underrepresented, or not. What I have a problem with is saying "here is a completely legitimate, bias-free business decision that is in the best interest of the company (e.g. closing the Atlanta office for cost savings). But it hurts this minority group, so we're not going to do it, which puts the business on less solid ground and has a larger net negative impact."

If bias results in you disproportionately impacting one group over another, you should fix it. If business does, it's more racist to try to "fix" it by taking everyone's demographics into account.


What? I can't invert my mind enough to understand this phrasing.

There doesn't have to be an admission. It could be overt and conscious, or it could be subconscious (e.g. associating minorities with having less competence without even realizing it).


What is the definition of "disproportionately"?

If 12% of purple-skinned employees were laid off but only 10% green-skinned ones, is that disproportional, confirming racism?


Because the people in charge are often in the majority group and when they're going down a list of names, their biases come into play.


Policies with no racial component often disproportionately target a minority group when metrics or properties that are purportedly race-neutral are, in fact, biased. Basing firing decisions on these qualities (arrest record, credit history, where they attended college) doesn't have racist intent, but it likely to have racist outcomes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: