Candidate Identity Resolution: How to Merge Evidence Without Merging the Wrong Person
Candidate intelligence becomes dangerous when the system is overconfident about identity. The same person may appear across several sources, but similar names, employers, locations, and skills are not always enough to justify an automatic merge.
Last reviewed: 2026-09-06
Ask SourcingOS about this page
1. Keep source profiles intact
Each source profile should retain its source identity and provenance even when it is linked to a canonical candidate. This makes it possible to audit where a claim came from and to reverse a bad association.
The canonical candidate is an organizing layer over evidence, not a license to erase source boundaries.
2. Prefer deterministic anchors when available
Strong identity anchors include exact provider identifiers, verified emails, exact profile URLs, or other stable identifiers with known provenance. Weaker signals such as similar names, titles, cities, or employer histories can support a proposal but should not be treated the same way.
The system should know the difference between an anchored link and a probabilistic similarity match.
3. Create reviewable proposals for uncertainty
When evidence suggests two profiles may be the same person but is not decisive, generate an identity proposal that shows supporting and conflicting signals. The reviewer should be able to confirm or reject it explicitly.
A rejected proposal is learning too: it can reduce future false merges for similar patterns.
4. Merge provenance atomically
When a merge is confirmed, the candidate graph should move or relink the relevant source profiles and dependent evidence consistently. Partial merges create corrupted histories where evidence and source records point to different identities.
Identity operations therefore deserve stronger transactional and audit guarantees than ordinary UI state changes.
5. Show previous recruiting history after resolution
Identity resolution becomes much more useful when it reveals that a candidate was previously sourced, applied, contacted, rejected, advanced, or reviewed for another role.
That history saves recruiter time and prevents awkward duplicate outreach—but only when the underlying identity link is trustworthy.
Key takeaways
- Preserve source-profile provenance.
- Distinguish deterministic anchors from similarity signals.
- Route uncertain matches through explicit review.
- Make confirmed merges transactional and auditable.
- Use resolved identity to surface recruiting history safely.