Blind CV screening sounds like one of those ideas that should obviously work. Hide the name, remove the photo, maybe strip the university too — and suddenly you're judging candidates on skill, not subconscious pattern-matching. Clean. Fair. Done.
Except it's not quite that simple.
If you're a founder making two or three hires a year, you don't have an HR department running structured experiments. You're reading CVs at 9pm between client calls. Blind screening can genuinely help — but only if you understand what it does and doesn't fix, and how to actually implement it without building a whole new process.
Let's get into it.
What blind CV screening actually means
Blind CV screening means removing identifying information from a CV before you evaluate it. The basics are:
- Name (often the biggest one — research shows names signal gender and ethnicity)
- Photo
- Address (postcodes can signal socioeconomic background or distance)
- Graduation year (can reveal age)
- University name (can be left in or removed depending on what you're testing for)
Some teams go further and also strip dates from work history, or redact specific company names if those companies are unusually associated with a particular demographic.
The goal is to force yourself to evaluate what the person has actually done, not who they appear to be.
Does the research support it?
Yes — with caveats.
The most-cited study on this comes from Australia. Researchers sent identical CVs with different names to employers and found that candidates with Anglo-Saxon-sounding names received 35% more callbacks than candidates with Chinese, Middle Eastern, or Indigenous Australian names. The CVs were otherwise identical. That's a real, measurable, uncomfortable gap.
In the UK, a similar 2009 study by the Department for Work and Pensions found that applicants with white-sounding names needed to send around 9 applications to get a callback, compared to 16 for applicants with ethnic minority names. Same qualifications, different names.
Blind screening directly addresses this. When you can't see the name, you can't (consciously or not) make assumptions based on it.
But here's where it gets complicated: a 2016 study from Australia's Behavioural Insights Team found something counterintuitive. When they ran a blind recruitment pilot across Australian federal agencies, blind screening actually reduced the callback rate for women and minority candidates in some roles. Why? Because the evaluators — when they couldn't see demographic signals — defaulted even more heavily to proxies like prestigious employers and top-tier universities, which skewed back toward majority groups.
The lesson isn't that blind screening is bad. It's that blind screening is a first-line filter, not a complete solution.
What blind screening does well
For small teams, blind screening is genuinely useful for a few specific problems:
1. Name-based bias This is the clearest win. Removing names reduces the chance that a candidate called "Mohammed" or "Priya" gets unconsciously deprioritised versus a candidate called "James." There's enough evidence here to make this worth doing consistently.
2. Photo bias If you're hiring in a country where CVs sometimes include photos (Germany, much of Asia, parts of Eastern Europe), removing photos removes a huge vector for bias — attractiveness, perceived age, race. If you're receiving CVs from international applicants, this matters.
3. Forcing criteria clarity Here's an underrated benefit: when you remove the "vibe" signals from a CV, you're forced to articulate what you're actually evaluating. That's a useful discipline. Teams that implement blind screening often report that it forces them to agree on what a good CV actually looks like before they start reading — which improves consistency across the whole process.
What blind screening doesn't fix
Blind screening only covers the CV review stage. Once you hit the interview, every bias comes rushing back in — appearance, accent, mannerisms, likability. Research consistently shows that most hiring decisions are heavily influenced by first impressions formed in the first few minutes of an interview.
It also doesn't fix:
- Structural bias in job descriptions — if your job post requires "10 years of experience" for a role that doesn't need it, or uses language that's been shown to attract male applicants over female ones, you've already narrowed your pool before a single CV arrives
- Network-based hiring — if you're mostly hiring from referrals, you're largely hiring people who look like your existing team, and blind screening doesn't touch that
- Interview bias — structured interviews with consistent questions and scoring rubrics help far more here than any CV adjustment
- Education snobbery — if your evaluators are unconsciously filtering for Oxbridge or Russell Group degrees, blinding the name doesn't remove that signal
How to actually implement it as a small team
You don't need special software. Here's a simple process that works:
Option 1: The manual redaction method
- Assign one person (ideally not the hiring manager) to receive all CVs first
- That person opens each CV and deletes or blacks out: name, email address, phone number, photo, home address, and graduation year
- They rename the file to something neutral ("Candidate 1", "Candidate 2")
- The hiring manager reviews the redacted versions and scores them against your criteria before seeing any identifying information
This takes about 5 minutes per CV. For a typical small team hiring round with 30–60 applicants, that's a few hours of admin — annoying, but manageable.
Option 2: Use your ATS or hiring tools
Several applicant tracking systems now offer blind review modes. If you're already using a tool that supports this, turn it on. It's usually a toggle in settings.
If you're not using an ATS and you're making 2–4 hires a year, you probably don't need one — but you do need a consistent process.
Option 3: Standardise your application form
Instead of accepting CVs entirely, ask candidates to fill out a structured application form with specific questions: relevant experience, a work sample, key skills. This isn't exactly blind screening, but it removes a lot of the formatting and presentation variance that lets unconscious pattern-matching creep in.
Forms also make it much easier to compare candidates side-by-side on the same criteria, which is arguably more valuable than hiding names.
The bigger picture: bias reduction as a system
If you're serious about reducing bias in your hiring — and you should be, both because it's the right thing to do and because homogeneous teams demonstrably underperform diverse ones — blind CV screening is one piece of a larger set of practices:
- Write better job posts. Biased language in job ads narrows your pool before anyone applies. "Rockstar," "ninja," "crushing it" — these phrases have measurable effects on who applies. Keep requirements tight and honest.
- Score before you discuss. When reviewing CVs or conducting interviews, have each evaluator score independently before any group discussion. Group discussion without prior individual scoring strongly favours whoever speaks first.
- Use structured interviews. Same questions, same order, for every candidate. Score against a rubric before comparing candidates to each other.
- Track your funnel. If you're not tracking what percentage of applicants from different backgrounds make it through each stage, you have no idea where the drop-off is happening.
Blind CV screening sits at step one of this process. It's not sufficient on its own, but skipping it is a missed opportunity to reduce a real, documented source of bias at almost zero cost.
A realistic expectation for small teams
If you're a 12-person company making 3 hires this year, you're not going to run a controlled experiment to measure whether blind screening is working. That's fine. You don't need to.
What you can do is implement blind name removal consistently, pair it with clear evaluation criteria before you start reading, and use structured interviews afterwards. That combination will meaningfully improve the quality and fairness of your decisions without adding significant overhead.
Don't let perfect be the enemy of practical. Removing names takes five minutes. Do it.
Where Penroll fits
Penroll helps small teams structure the front end of hiring — from writing clear job posts to screening applicants against defined criteria — which pairs naturally with a blind review process. When your evaluation criteria are explicit before you start reading CVs, blind screening works better. Penroll makes it easier to get that structure in place without building a whole hiring ops function from scratch.