On this page▾
- The conversation nobody is having honestly
- Where bias actually lives in your funnel
- Sourcing: stop fishing in the same pond
- The resume screen is where you bleed talent silently
- Structured interviews beat your gut, and your gut hates that
- What lowering the bar actually means, and why you should not
- Goals versus quotas, and why the distinction is everything
- Where technology helps and where it makes things worse
- The honest version of the goal
Diversity hiring is one of the few topics in recruiting where almost everyone is performing rather than thinking. One camp treats it as a moral obligation to be signaled through statements and pledges, with the actual hiring barely changing. Another camp treats any focus on diversity as an attack on quality, assuming it must mean lowering the bar. Both are wrong, and both are wrong in a way that makes the problem worse.
I want to make an argument that should be uncontroversial but somehow is not: you can build a meaningfully more diverse team without lowering your bar one inch and without any of the theater, and the way you do it makes your hiring better for every candidate, not just underrepresented ones. The trick is to stop intervening at the end of the funnel, where the trade-offs are real and ugly, and start intervening at the top and middle, where they mostly are not.
Picture your hiring funnel as a series of filters: where you source, who applies, who passes the resume screen, who passes the interviews, and who you decide to hire. The instinct when people want a more diverse team is to lean on the last step - to weight the final decision toward underrepresented candidates. That is the one place where you do face a real trade-off against your other criteria, and it is also where the law gets complicated, and it is the least effective lever you have.
The leverage is almost entirely upstream. If your sourcing only reaches people who look like your current team, no amount of fairness at the end fixes a pool that was skewed before anyone applied. If your job descriptions quietly signal that only one kind of person belongs, you lose candidates before they ever hit your funnel. The candidates you never saw are invisible in your metrics, which is exactly why the upstream problem is the one people ignore. Fix the top of the funnel and the bottom mostly takes care of itself.
Most teams source from the same three channels their last hire came from, which means they keep catching the same fish. If your engineering team came mostly from two universities and one ex-employer's alumni network, your pipeline is structurally homogeneous and it has nothing to do with anyone's intentions. The pool was narrow before bias ever entered the picture.
Widening the pool is unglamorous, concrete work. It means sourcing from professional communities you are not already plugged into, posting where different audiences actually look, building relationships with organizations that reach groups you do not naturally reach, and being honest about which referral sources are just cloning your existing team. None of this lowers the bar - you are still going to hold everyone to the same standard. You are just making sure the standard gets applied to a pool that actually represents the available talent, instead of the slice of it that happens to share your background.
The resume screen is the most bias-saturated step in most processes and the one people scrutinize least. A reviewer glances at a name, a school, a company, a gap in employment, and makes a snap judgment that feels like merit but is heavily contaminated by pattern-matching to people who succeeded before. The candidate who took two years off to care for a parent, the one from a school you have never heard of, the one whose name your reviewer cannot pronounce - they get cut for reasons that have nothing to do with whether they can do the job.
There are real fixes here that cost you nothing in quality. Strip names and schools from the initial screen so reviewers judge experience and skills. Define what you are actually screening for before you look, so you are not inventing criteria to justify a gut reaction. Better still, replace the resume screen with a work sample as early as you reasonably can, because a work sample measures the thing you care about directly instead of through the noisy proxy of a resume. Every one of these makes your screening more accurate for everyone, which is the whole point - this is not charity, it is rigor.
The unstructured interview - a friendly chat where the interviewer goes by feel - is both the most popular hiring method and one of the least predictive, and it is a bias amplifier by design. When you go by feel, you reward the candidates who feel familiar, who share your references, who interview in the cultural style you happen to find comfortable. You call it chemistry. It is often just similarity.
Structured interviews - the same questions, asked the same way, scored against a defined rubric - are less pleasant and more predictive, and they dramatically reduce the noise that bias hides inside. The discipline is to decide what good looks like before the interview and to score against that, not to retrofit a justification onto whoever charmed you. Interviewers resist this because it feels mechanical and it takes away the fun of trusting their instincts. But your instincts are exactly the thing that has been quietly narrowing your team. Structure is how you hold a real standard fairly, which is the only version of a standard worth having.
Let me be direct, because dancing around this helps no one. Lowering the bar - hiring someone you believe is less qualified to hit a demographic target - is a bad idea, and not only for the obvious reasons. It is corrosive to the person you hire, who will be presumed to be a diversity hire and will have to fight that assumption every day. It is corrosive to the team, which learns the standard is negotiable. And it is unnecessary, because it is solving a problem that better sourcing and fairer screening would have solved without the cost.
The entire argument of this article is that you do not have to choose between diversity and quality, because the false choice only appears when you have done nothing upstream. If your pipeline is narrow and your screen is biased, then yes, at the final step you face an ugly trade-off between representation and your other criteria. Fix the pipeline and the screen, and that trade-off largely dissolves. You end up with a more diverse team and a higher bar, because you have been applying a real standard to a wider and more fairly evaluated pool the whole way through.
Setting a goal - we want our pipeline to reflect the available talent pool, we want to interview a representative slate - is healthy and legal and focuses effort where it belongs, at the top of the funnel. Setting a quota - we must hire this many of this group regardless - moves the intervention to the bottom of the funnel, where it creates the exact trade-off you should be avoiding and where it tends to run into legal trouble.
The useful frame is to set goals on inputs you control and outcomes that reflect fairness, not on the final demographic composition of who gets hired. Hold yourself accountable for whether you sourced widely, whether your slates were representative, whether your screen was structured. Those are things you can fix through better process. The final composition is a downstream result of doing the upstream work well. Manage the inputs and let the outputs follow, rather than reaching for the output directly and distorting everything to get it.
AI in hiring cuts both ways on bias, and anyone who tells you it is simply good or simply dangerous is selling something. Trained carelessly on your historical hiring data, an algorithm will learn your past biases and apply them at scale with a veneer of objectivity, which is worse than a biased human because it is harder to argue with a number. There are well-known cautionary tales of exactly this. So I am not going to pretend the technology is automatically a force for fairness.
Used carefully, though, it helps in the places that matter. It can anonymize screens so reviewers judge skills not names. It can enforce a structured, consistent evaluation so every candidate gets the same questions scored the same way. It can surface candidates from sources your team would never have searched. The deciding factor is whether the system measures the job or pattern-matches to your past hires, and whether you can actually see and audit why it made each call. A tool that hands you a score with no reasoning is a bias-laundering machine. A tool that shows its work lets you catch the bias.
The reason to build a diverse team is not to put out a statement or hit a number that makes a board slide look good. It is that homogeneous teams have correlated blind spots, make worse decisions about products and customers they do not resemble, and quietly recruit more people exactly like themselves until the whole organization is optimized for one narrow worldview. Diversity, done as rigor rather than theater, is just a way of making sure your team can see more of reality than any one type of person can.
So do the unglamorous work. Widen where you look. Strip the noise out of your screen. Structure your interviews. Hold the bar high and apply it fairly to a wider pool. Set goals on the inputs you control and resist the urge to fix the output directly. Skip the statements and the theater entirely; nobody who matters is fooled by them anyway. You will end up with a stronger, broader, sharper team - and you will get there without ever once lowering the bar or pretending you did something you did not. That is the only version of this worth doing.
