Why did this candidate appear in my results?
A candidate should be explainable through the role artifact and the evidence that was discovered. SourcingOS is designed to preserve the distinction between why someone was discovered and whether they satisfy each requirement.
Last reviewed: 2026-09-06
Ask SourcingOS about this page
Discovery is not the same as qualification
A candidate can enter the slate through an adjacent-title, donor-company, public-evidence, ATS, or provider lane. That discovery path explains why SourcingOS looked at the person; it does not automatically prove the person satisfies the role.
Review requirement-by-requirement evidence
Look for the evidence tied to the explicit requirements. A candidate discovered through Linux administration should not receive must-have RHEL credit unless the evidence actually supports RHEL or an equivalent normalization.
Check the source lane
Source and lane context can explain why a candidate looks less obvious than a direct-title result. Adjacent and evidence-led lanes are intentionally designed to expand recall without rewriting the role brief.
Treat missing evidence as a question
If the candidate appears promising but a key requirement is not publicly evidenced, keep that field missing or verification-sensitive rather than assuming a positive match.