Describe the hire
Start in natural language, structured fields, or with a JD. Recruiter-entered requirements remain distinct from search expansion.
Candidate Search · private beta
Search like a recruiter. Keep the reasoning visible.
Describe who you need, review exactly what SourcingOS understood, then search and inspect people without turning AI suggestions into hidden requirements or black-box scores.
Requirements stay explicitSearch expansion stays reviewableEvidence stays source-linked
Candidate SearchRecruiter review first
Senior RHEL administrator near Annapolis Junction with 5+ years and Secret or higher
Target titlesRHEL AdministratorLinux Systems Administrator
Must-haveRHEL5+ years relevant experience
GeographyAnnapolis Junction, MDRecruiter-entered
ClearanceSecret or higherRequires verification
Suggested expansionAnsibleRed Hat Enterprise LinuxLinux infrastructure
Workflow
One search flow, not six separate screens.
The product should feel like a sourcing copilot: understand the role, let you correct it, find people, and keep the search editable after results arrive.
Review the interpretation
See titles, must-haves, preferences, geography, seniority, and suggested expansion before candidate sources run.
Search supported sources
SourcingOS executes supported public-source lanes and labels guided or unavailable sources honestly.
Review people with evidence
See why each person surfaced, which requirements have evidence, what remains unknown, and what needs verification.
Save, refine, or investigate
Move strong people into a role, inspect Candidate 360, or adjust the search without rebuilding the entire brief.
Search control
Natural language when you want it. Explicit filters when you need them.
Experienced sourcers should not have to choose between a ChatGPT-style brief and recruiter-grade field control.
Brief the search conversationally.
Describe the person, constraints, target market, or what went wrong with the last pass. SourcingOS turns that into editable search structure.
Use structured, searchable criteria.
Titles, skills, location, seniority, companies, industries, clearance, tenure, open-to-work, and contact history stay visible as recruiter-controlled fields.
Start from source material.
Extract role evidence from a JD or use a resume as a similarity seed without silently converting resume facts into hiring requirements.
Candidate review
Every result should answer “why did this person surface?”
Candidate review is organized around evidence coverage, unknowns, source provenance, identity confidence, and recruiter action — not a single opaque match percentage.
Candidate 03
Jordan A. · Senior Platform Engineer
Public engineering evidence + recruiter-reviewed identity context.
RHELAnsibleAWS
RequirementRHEL production administration
StateEvidence found
SourcePublic profile + project evidence
NextVerify scope and recency
Ready when your next hard req is
Start with the search. Keep the evidence.
Use the recruiter workspace if you already have access, or request the private beta and try the free tools while you wait.