Whoever the candidates were, whatever their backgrounds and accolades and educations, he didn't care. No one was to know who they were rating, and after a while there were complaints of bias... for talent.
During that period, yes, there were more women and people of color chosen than historically comprised their body, but they were from everywhere. It turns out musicians didn't want to be reduced to bigoted demographics, so it attracted many more "non-traditional" candidates when word spread you could make it on merit.
Blind auditions were scrapped when he left, and so did actual diversity. You can include everyone today in a single introduction by mentioning Yale, Juilliard, Paris Conservatory, Royal Academy, etc.
Merit destroys class privilege, which is a big faux pas when your patrons tend to be family of people who want to advance their careers in your institution. Just recently, I couldn't help but notice the timing of the creation of another superfluous position being filled by a fledgling choral director and a $MM donation by his parents to expand the performance hall he'll be using.
Mere dutiful patronage, surely, in these times of austerity.
I asked a question, mentioned the orchestra approach and suggested blind tests for tech recruiting.
i.e. HR scrubs the name, pronouns and anything likely to subconsciously discriminate and pass their resume to the hiring team. Not perfect, but it gives X at least a better shot.
I was pretty much told it would never work and there were better ways and dismissed with a wave of a hand.
So why don't we do these somewhat blind tests?
Just look up "meritocracy dead" on a search engine of your choice. It's pretty minds boggling what people want to replace the goal of meritocracy with these days.
it is certainly still possible for lower class children to get a leg up, but it's still an uphill climb
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.
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.
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.
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.
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.
What? Other engineering fields have certifications and standards processes that actually mean something, and enforcement of it. That’s how they determine the baseline standard.
Software engineering’s closest thing is a 4-year degree who’s so routinely undervalued (per alignment to work requirements) it’s challenged by 3 month bootcamps, which are themselves challenged by garage-living dropouts with no explicit formal education.
And traditionally you had near-decade training with an apprentice/master system, or in a trade school, or expected-lifetime employment & training with the same company.
Software development is pretty new in trying to force feed training in large quantities with little to no verification, standards process or really any legitimate first or third-party trust-rings or evaluation process. I mean shit we’re still running on the assumption that the 20-year old dropout has decent potential to be an expert in his field ala wiz/gates/carmack.
As an industry, I think we’re fairly unique in our general incompetence.
It makes sense if you want to increase diversity to have the beginning of the funnel get lots of diverse candidates in. The recruiter is not a decision maker in most places, so the hiring bar is not necessarily affected by whether the recruiter got more diversity candidates into the funnel or not.
As an example, in my experience there were not a lot of female candidate resumes coming in via normal channels. If the recruiter wants a bonus for increasing gender diversity, they are doing extra work to go and find female candidates and convincing them to apply. That is probably exactly what you want to be happening.
Unfortunately when you have affirmative action or hiring quotas, you inadvertently to create a culture where the diverse individuals are seen as less skilled and less qualified even when many of them would have gotten to the same place without the quotas.
That's not affirmative action. That's like giving free SAT prep to disadvantaged minorities. Affirmative action is further down the line, moving the bar for test/interview results to hit targets.
Which is not to say Google doesn't do it, just that the programs you're describing aren't it.
That is, of course, if your resume doesn't get tossed out for not being diverse enough [0][1]
[0] https://www.theverge.com/2018/3/2/17070624/google-youtube-wi...
[1] https://www.wired.com/story/new-lawsuit-exposes-googles-desp...
They do get filtered later. Over the years only one person who bombed an on site with me got hired. It was a young white man. I believe described this case on HN before.
Been there, done that. It’s a no go.
Wow this is not at all correct based on my experience.
It is so common for "non-diverse individuals" to have gotten where they are based on things like network that I really don't think you can tell just by looking at someone.
The worst developers I have worked with are often traditional "non-diverse" candidates.
That's generally in proportion to the ratios in the workspace itself, nothing surprising statistically.
Now ask yourself who are best developers you have ever worked with. Even that is probably non-diverse ones.
That's a real question, and I don't have a good answer.
That apprenticeship is expensive. It takes a lot of handholding. Not because they're not smart, but just because there's a vast amount of information that's hard to write down. It's a million little factoids, and they're easy to Google ... once you already know that they're there.
It's not impossible to build a company with one really good senior dev and a bunch of fresh-outs. But that's made one level more complicated when you've got a diversity of cultures in the room, and the hiring process ends up coming down to "Well, that guy just seemed like a better fit". So the excluded ones give up, and the process perpetuates.
I'm oversimplifying like crazy, and every real situation is different. But startups don't have the money or time to do better, and established companies just keep repeating their situations because that's what got them there.
Some day somebody may figure out how to change that... and they're almost certainly going to get run through the wringer on HN accusing them of being affirmative-action SJW wokeness virtue-signallers. Which just makes it one step harder, and when they fail (as most new things do) it will further cement for people that Those People just can't code.
And, yet, YC funds these kinds of companies all the time. So why isn't YC tapping that pool?
> But that's made one level more complicated when you've got a diversity of cultures in the room
I don't buy that.
Tech happily on a daily basis deals with people who can barely speak the same language.
[for the people downvoting: I'm just pointing out what the article says.]
That doesn't seem a likely course of action.
The lawsuit would be hilarious.
Why don’t you ever suspect that young white guy to just have the job bececause their father knows the CXO from golf? Did that sysadmin use to room with the tech lead in colleges? Empirically, such employment biographies are far more common than your hypotheticals. Gut somehow, they do not seem to provoke this righteous anger of meritocracy.
By the same conflation one could argue that nepotism is a prefectly valid employment tactic due to quota-filling also being.
Now, it does annoy me having had to jump-backwards through the modern interviews for tech position and now there are people like the author who get handed the same kind of jobs solely based on the genitalia the were born with and still complains about it.
So save your dollar store philosophy and stop making judgments about my reasons.
Yet people lose their shit when it comes to trying to apply proactive equalizers to a historically deeply unfair society.
There's no real mystery, it's just selfishness taking precedence over correcting past wrongs.
That said, to do it effectively, I believe we need to focus on doing it early on in schooling, and the burden and pressure being put on companies is a heavy one because it doesn't align with where the opportunities first diverge.
I agree with the need to attempt to correct unfairness by starting early, though. Just also pay attention to confounding factors, and never lose sight of the goal.
In hiring, which is not a zero sum game, we can prevent these undesired behaviors (acknowledging and correcting for bias) without giving token advantages which undermine meritocracy
What is selfish is you punishing someone else with the same skin color, and then upholding literal racism as a virtue.
They absolutely should lose their shit over that.
Unless you're in a small company with a substantial ownership stake, not only should you accept the reality of this but also accept that dealing with it is part of your job. Making the best of the team and resources available is part of the job description.
If given the reins of the hiring process, a given developer could not do a better job filling out company's a roster.
The company has made decisions. Unless you were consulted on those decisions, your opinions aren't desired. Most of the time, your helping of those decisions' consequences will be inline with your responsibility for them: nil (scapegoating happens and shit rolls downhill, but I'd argue both are necessarily rare).
In this case, I think it's funny because the same mentality results in a more kumbaya attitude in the workplace (it's not my job to pick my coworkers. Whatever their faults, it is my job to succeed anyway). It's the type of thing I'd expect to be a bit of a upvote magnet...but I suppose hating on crappy coworkers trumps warmfuzzies in the HN crowd.
That's the miracle of "affirmative action" or whatever you want to call it.
When looking at candidates internally, if a company decides to do affirmative action there are those that you know are there because of their skills (non-diverse individuals) and there are the other ones. Are they there because of skills? Could be, could also be HR wanting to push diversity? Also possible.
Some places I've even seen a "diversity quota" for tech recruiters that's tied to a bonus. So at every "diverse" hire you encounter you have to ask yourself: are they here because of skills or because someone was one hire short of cashing out their bonus?