4 ms·
That's one take. Another take is that people want chums at work. An average person hires someone they see themselves as being friends with rather than the best
by asdff 6y ago
That's one take. Another take is that people want chums at work. An average person hires someone they see themselves as being friends with rather than the best qualified candidate. Animals such as bees, monkeys, and ourselves are also biased to favor their genetic group (kin selection). In other words, you subconsciously favor people who look like you and act like you.
In that light, the non diverse office might be seen as less productive. Maybe this is a bunch of pals goofing off, rather than people hired to do work?
But the whole point of the diversity hire isn't that you get someone who isn't white and that's it. The idea is that for every job, there are thousands of people who are qualified to do it, and among those, there are certainly people from all sorts of walks of life, and you'd spend earnest effort overcoming your subconscious biases by dipping your hand into the pool of equally skilled candidates, and pulling out the one that this overtly white dominated society we live in has held down since forever.
- darkwater 6y agoThanks for saying and explaining what diversity hiring actually is. Much needed and much appreciated.
- Fellshard 6y agoSo the whole thing is based off of false premises; good to know.
- thu2111 6y agoIt sure would be easier to build software firms if every job got thousands of qualified applicants. Obviously, that isn't the case.
- asdff 6y agoThat has more to do with the lack of marketing of the job opening than a lack of qualified talent out there
- setr 6y agoI think more generally the issue is being swamped with unqualified talent, such that it's difficult to identify actual talent amongst the mess. A lot of people are not trying to be good at what they do, they're just trying to be paid for what they do.
- asdff 6y agoWhat's the issue? Look through resumes, see who has worked in this area before, interview and see if they talk the talk, hire and get them up to speed to walk your walk. If the job is so complex that you have difficulty finding someone who can fit in every required peg, then that job should be broken into smaller, more manageable tasks that can be done by several more common people from the labor pool. It's just good business sense, too. If you require some specialist that takes forever to find and they leave, then you are screwed while hunting for a replacement. If you've instead broken that complicated job into digestible pieces, and someone leaves, you can hire a decent candidate before your employee even leaves, and have your employee get their replacement up to speed in their last few weeks along with the rest of the team.
- setr 6y agoThe general problem, I think, is that talking the talk is not that hard, especially if you're not already well-covered in that domain (e.g. an established department/strong competency in the specific area) -- see all of sales. It's not that hard even if you are well-covered in that domain -- see all of pre-sales, and all of consulting. The fundamental issue is that describing a solution in broad strokes is much easier than in detail, and an interview doesn't give you so much time to even get into those details; and spending time to further evaluate is at least weeks of effort (because it's difficult to differentiate between someone competent getting up to speed on your codebase, and someone incompetent, and someone incompetent but can be made competent, without sufficient time to evaluate). A lot of time is burned in recruitment cycles, largely because its much easier to say you're competent than to prove that you're not. (not to mention the natural reluctance & possible legal difficulties with firing). Jobs get thousands of applicants; few of whom are worth considering, and resumes/interviews really don't tell you all that much. They tell you more than nothing, which is why they're used, but it's difficult to be comfortable on those alone, and there's not that much more you can do before it becomes weeks/days of free labor by your candidate. Anyways, there's more than enough money burned on the subject that "throw more marketing at the problem" is very likely too easy an answer.
- 908B64B197 6y ago> But the whole point of the diversity hire isn't that you get someone who isn't white and that's it. The idea is that for every job, there are thousands of people who are qualified to do it, and among those, there are certainly people from all sorts of walks of life, and you'd spend earnest effort overcoming your subconscious biases by dipping your hand into the pool of equally skilled candidates, and pulling out the one that this overtly white dominated society we live in has held down since forever. How did you find a recruiting pipeline where you can confidently say that there are thousands of equally competent potential hires in it? In Software Engineering? I'm very curious to know where and how you source talent.
- prepend 6y agoI have interviewed hundreds and hired dozens of software developers over the years. It’s always been a challenge to find qualified candidates and I’ve never had a situation where there were 5 similarly qualified programmers, much less thousands. I think there may be some positions where there lots of people equally skilled, but not aware of any in tech. Perhaps there are thousands in the entire world, but not that apply to my positions. I think this is a good argument for trying to get more and better applications. But it confuses me to think that of the applicants I get, I can assume many are equally skilled.
- animal531 6y agoI spent some some doing work for a recruitment company and my takeaway from that was that culture fit is the #1 predictor of a successful placement.