CV anonymisation comes up regularly in discussions about responsible recruitment. It is useful — but it is often presented as a complete answer to hiring bias, which it is not. Here is what it really changes, and what you need alongside it.
What an anonymised version hides
In practice: name, photo, age, address and sometimes the school attended. The aim is to remove, at the first screening stage, the signals that have nothing to do with the ability to do the job but still influence judgement — largely unconsciously.
What anonymisation does not solve
An anonymised CV can still be rejected for the wrong reasons: poorly defined selection criteria, a missing scorecard, or bias creeping back in at the interview — where anonymity necessarily disappears. Anonymisation protects the first screening, not the whole process.
When to anonymise, when to reveal
- ✓Anonymise before the first screening — that is when CV volume pushes towards fast decisions, the ones most exposed to bias.
- ✓Reveal as soon as an interview is scheduled — a normal human conversation needs it, and hiding it beyond that adds nothing.
- ✓Keep the original accessible — anonymisation should never replace the full file, only complement it for the first screening.
The legal framework, in one sentence
The GDPR governs the processing of personal data used for these decisions, and the principle of non-discrimination in hiring applies whatever the tool used to screen applications — anonymisation is a recommended good practice, not an obligation that excuses you from checking the rest of the process.