|
|
|
|
|
by rmartelli
3702 days ago
|
|
Their argument typically looks like this:
Choosing a candidate pool that is 80+% men (>X years experience as a developer) is inherently sexist. To eliminate structural sexism, we must remove hiring criteria that favors men. Let's tell our sourcers that looking for relevant industry experience is not important. For school I've been told that we should look if they have a degree or not, and not consider which institution. This explicitly considers all colleges the same. Every point in the post is an actual suggestion made on how to improve diversity. Obviously not all the suggestions have been implemented, but I'm afraid the committee for improving hiring might do just that. |
|
For example, someone might argue that actively seeking out recent graduates of coding bootcamps when hiring for junior positions will help find a more diverse set of candidates. And there's truth here: bootcamps tend to have better gender and somewhat-better racial balance than university CS departments or existing tech shops, and bootcamp graduates on average seem to be pretty good (there are selection and maturity and self-motivation effects there which raise quality compared to the typical randomly-chosen bunch os CVs).
But it's technically correct, so long as you don't mind completely misleading connotations, to describe that approach as "to eliminate racism and sexism, hire people who don't have CS degrees and don't have industry experience" and imply it's "lowering the bar".
And anecdotally, when people make claims like the ones in the OP article, my experience is that it's almost always the case that someone is carefully choosing how they describe things in order to be technically truthful while maliciously misrepresenting the situation in a way that suits their personal axe-grinding.