Blind hiring pros and cons come down to one trade. Hiding who a candidate is removes a real bias from the first cut, and it also removes context you sometimes need. For engineering teams, my answer is simple: go blind at the screening stage, then stop once you are talking to people. The famous studies are weaker than their reputation, and one government trial found that blind shortlisting made outcomes worse for women.
Key Takeaways
- Name-based bias in resume screening is well documented: in one field experiment, white-sounding names got 50% more callbacks.
- The orchestra study everyone quotes is statistically shakier than the headlines suggest.
- In an Australian government shortlisting exercise, de-identified applications lowered women's chances, because hiding identity removed reviewers' positive bias.
- Blind screening helps most when it hides employer brands and schools, and it stops being useful once interviews start.
What Blind Hiring Hides, Stage by Stage
"Blind" means different things at different steps. Most teams that say they do it only hide the name on the resume. The bigger signal in engineering is usually the employer: a famous company name on a profile does more work in a reviewer's head than almost anything else on the page.
| Stage | What gets hidden | Why it matters |
|---|---|---|
| Resume screen | Name, photo, school, employer names | Removes name and brand shortcuts from the first cut |
| Skills test | Everything except the work | Graded on output, not on who wrote it |
| Interview | Nothing (you meet the person) | Structure replaces blindness here |
| Offer | Nothing | Identity, references and checks matter |
The interview row is the important one. You cannot keep a candidate anonymous through a conversation, and you should not try. What protects you there is structure: same questions, same rubric, scores written before the debrief. We cover that in structured vs unstructured interviews.
The Blind Hiring Evidence, Pros First
The strongest case for blind screening is about names. In the Bertrand and Mullainathan field experiment, researchers sent nearly 5,000 resumes to over 1,300 job ads in Boston and Chicago. White-sounding names received 50 percent more callbacks. Applicants with white names needed to send about 10 resumes to get one callback, against about 15 for applicants with African American names.
That is one study from the early 2000s. A 2017 meta-analysis in PNAS pooled 28 field experiments covering 55,842 applications and found that, since 1989, white applicants received on average 36% more callbacks than African Americans and 24% more than Latinos. The authors saw no change in discrimination against African Americans over 25 years.
Then there is the orchestra study. Goldin and Rouse found that a screen during auditions increased by 50% the probability a woman advanced out of certain preliminary rounds. People repeat this as "blind auditions made women 50% more likely to be hired," which the paper does not say. In 2019, data scientist Jonatan Pallesen and statistician Andrew Gelman both pointed out very large standard errors; Pallesen wrote that the difference "is not statistically significant for any of the groups." It is a landmark study whose statistical strength has since been questioned. Cite it that way or skip it.
The Cons, Including One Most Articles Skip
In 2017, Australia's behavioural economics team ran a trial with over 2,100 public servants from 14 agencies, who each shortlisted applicants for a hypothetical senior role. When reviewers could see identity, they were 2.9% more likely to shortlist women. The researchers estimated that de-identifying applications would lower women's chances of being shortlisted by 2.9% and raise men's by 3.2%. Their conclusion: "the need for caution when moving towards 'blind' recruitment processes."
Context matters here. The agencies already had active diversity programs, so hiding identity removed a bias that was helping. If your team is already working hard on a balanced pipeline, blind screening can undo some of that work.
The other cons are practical. You lose context: a career gap explained by a startup that failed, open-source work under a real name, a portfolio. And blind screening does nothing about the interview, where most bad hiring decisions get made. A 2022 re-analysis by Sackett and colleagues ranked structured interviews as the top predictor of job performance, at a validity of .42. Fix the interview first if you can only fix one thing.
Where Sol Fits
We built blindness into how Ruzora shows engineers. When you describe the role to Sol on our homepage, it checks the vetted bench and, if engineers fit, shows up to three profile cards in the chat. Those cards show seniority, years of experience, overlap with US hours, skills and a short summary. No names, no employers. After you give a work email, the shortlist arrives with contact details removed, and as Sol puts it, "Names and employers stay hidden until we sign." Full identity and interviews come after a founder call and a signed agreement. More on how that works in Meet Sol and in our post on the anonymized resume.
Our reason for hiding employers is partly bias and partly business: the company name is what makes a profile findable. We think that is fine to say out loud.
A Concrete Version
A 40-person B2B SaaS company opens a senior backend role and gets 120 applicants. The hiring manager wants to try blind screening on the first pass.
They strip names, photos, schools and employer names, and keep job titles, years of experience, skills and a link to a short written answer about a system the candidate built. Two engineers review each profile for about 3 minutes, so 120 profiles x 3 minutes x 2 reviewers = 720 minutes, or 12 hours of engineer time. They advance 24 people to a short coding exercise, then 8 to structured interviews.
What they notice once names come back at the interview stage: 5 of the 8 finalists came from companies the team would not have recognized. Two candidates from well-known companies whose written answers were vague did not make the cut. That is the point of the exercise. It also cost 12 engineer-hours, which is why most teams only do it for roles with large applicant pools.
The Honest Counterpoint
Skip blind screening when the pool is small. With 15 applicants, you will read every profile closely anyway, and hiding details just slows you down. Skip it for referrals, where the whole point is who vouched for the person.
Skip it, too, when the employer really is the signal. If you need someone who has run payments at a regulated bank, the bank's name tells you something real about the controls they worked under. Hiding it means you ask in the interview instead, which is fine, but be honest that you are moving the check, not removing it.
And read the Australian result again before you announce a blind hiring policy. If your current process already corrects for bias in a direction you like, blindness can reverse it.
Frequently Asked Questions
What are the main blind hiring pros and cons?
Pros: it removes name and brand shortcuts from the first resume cut, where field experiments show bias is real. Cons: it hides useful context, it does nothing for interviews, and one large shortlisting exercise found it reduced women's chances in an organization whose reviewers already favored them.
Does blind hiring work for software engineers?
It works best for the first screen of large applicant pools, especially when you hide employer names along with personal names. Pair it with a graded work sample and a structured interview, or it will not change much.
Is blind hiring legal in the US?
Generally, yes. Hiding names and employers on an early screen is a common practice. What regulators look at is outcomes: Title VII's disparate-impact rule applies to any selection procedure, blind or not, so track who advances at each stage. General information, not legal advice.
The Bottom Line
Use blind screening where bias is easiest to measure, at the resume cut, and use structure everywhere after that. If you want to see what a blind first look feels like, tell Sol what you are hiring for and judge the profiles on the work before you see a name. Read how we vet the engineers behind them, or skip ahead and request a shortlist.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers, with a vetted shortlist in 72 hours. See available engineers.
