Anonymizing CVs for Blind Hiring: a Recruiter's Checklist

Blind hiring works — when it's done consistently. The 2024 NBER review of 17 field experiments shows callback gaps narrow by 30–60% under structured anonymization. But the same studies note that inconsistent anonymization (some fields stripped, some not) can actually amplify bias because reviewers latch onto whatever signal remains.

If you're running blind hiring at a recruitment agency, you don't need a research paper — you need a checklist. Here's ours.

The 12-point anonymization checklist

#	Field	Action
1	Full name	Replace with Candidate #<hash>
2	Email	Strip entirely
3	Phone	Strip entirely
4	Profile photo	Remove all embedded images
5	Street address	Strip to country only
6	Date of birth	Strip
7	Nationality / citizenship	Strip
8	Gender / pronouns	Replace pronouns with "they/them"
9	Marital status	Strip
10	Graduation year	Strip (keep degree)
11	Employer names	Replace with industry + size band
12	LinkedIn / GitHub URLs	Strip until shortlist stage

Rows 1–9 are table stakes. Rows 10–12 are the ones agencies most often miss — and they leak more bias signal than you'd think. Graduation year is a strong age proxy; employer prestige drives halo effects; LinkedIn URL leads reviewers straight back to a photo.

What to do instead of stripping

A field stripped to a blank doesn't make a CV less readable — but a field replaced with an abstracted signal keeps reviewers in flow. Examples:

• Employer "Goldman Sachs" → "Tier-1 global investment bank, 40k+ employees"
• Graduation year → "Education completed" / "In progress"
• Location → "EU-based" / "US East Coast" / "Remote-only"

This is what we call structured anonymization: keep the category of information, strip the identifying token. Reviewers can still assess experience without being able to Google the candidate.

Where this breaks

Two failure modes we see repeatedly:

1. Reviewers re-de-anonymize from context. "Worked on the Slack acquisition" → reviewer infers Salesforce, infers seniority band, infers compensation expectations. The fix is to also abstract project names above a threshold of public recognizability.
2. Cover letters bypass the pipeline. Anonymization that only runs on the CV file leaves the cover letter as a back-channel. Process both, or don't accept cover letters at the shortlist stage.

GDPR and "right to be forgotten" notes

EU agencies should retain the anonymized version for the duration of the search and purge the original after a configurable window (we default to 90 days, see our GDPR page for details). Don't keep the original "just in case" — that defeats the consent basis you collected at upload.

CV Cleaner Pro applies the full 12-point checklist by default and lets you toggle each field per role. See it on the demo CV →