[jason_dstillery]

I tried to be careful in my phrasing, which is why I said "broader population of qualified candidates" and not "population at large" or "general population", and "good chance" instead of "certainty", because as you point out there are unfortunately systemic factors outside of your immediate short-term control that will affect the numbers.

But I think a lot of people/companies use this as an excuse to just not even try, and that doesn't make sense. Even if a group's share of qualified candidates is smaller than its share of the general population, that share certainly isn't zero, and once your team reaches a certain size its not hard to check the math and see if your process is producing results in bounds of reasonable estimates. Very frequently it isn't, and that can point to hidden or explicit biases that you can work to remove from your process.

[GunboatDiplomat]

>But I think a lot of people/companies use this as an excuse to just not even try, and that doesn't make sense.

Doesn't it? I doubt that hiring people of different ethnic backgrounds from the same country makes any difference in the performance of a team, so exerting extra effort to do so is likely a net loss for the company.

[jason_dstillery]

Let's say I see 2 qualified candidates a week and they accept our offer at a rate of 20%. To ramp up to a team of 12, I'll had to have seen 60 candidates, which will take 30 weeks.

But then I take a look at my process and realize I've got a problem that's keeping 1/3rd of my qualified candidates from even applying. Fix that, and I jump up to seeing 3 qualified candidates per week, which drops my ramp time to just 20 weeks.

The effort I put into fixing my hiring process just gave me 10 bonus weeks of a fully-ramped team. If your company actually knows how to use developers to make money, that could be literally millions of dollars.