See what evidence-first sourcing looks like.
SourcingOS turns messy reqs into candidate evidence, role-fit reasoning, risk flags, and hiring-manager-ready summaries. This is the artifact a sourcer forwards — not a search results page.
SourcingOS does not just score candidates. It shows the evidence behind the recommendation.
Cleared DevSecOps Engineer — Northern Virginia or Remote-US
Must-haves: Kubernetes in production, Terraform/IaC, active TS/SCI, CI/CD hardening in an RMF/ATO environment. Req age: 47 days. Lanes already exhausted before SourcingOS: LinkedIn Recruiter saved search, ClearanceJobs alerts. The HM’s stated pain: “everyone we see has the clearance or the platform depth, never both.”
Jordan A. — DevSecOps Engineer (sample)
Public evidence suggests a DevSecOps engineer with sustained Kubernetes and Terraform activity, GovCloud-adjacent delivery, and public speaking on RMF-aware pipelines. A self-stated clearance breadcrumb appears on a public resume and would need verification. Three source profiles roll up into this record — SourcingOS proposed the identity match; a recruiter approved it. Nothing merged silently.
Kubernetes in production
Evidence found — confirm ownership
Terraform / IaC
Evidence found
Active TS/SCI
Unverified breadcrumb — must confirm before submittal
CI/CD hardening in an RMF/ATO context
Strong indirect evidence (talk + repos)
AWS GovCloud
Evidence found (baseline modules, original PRs)
Sec+ / CISSP (8140)
No public signal — ask
Mentoring / tech lead experience
No public signal — ask
Every claim has a source. Every source is visible.
| Signal | Evidence | Source type | Confidence | What to verify |
|---|---|---|---|---|
| Kubernetes experience | Sustained public platform work in a DevSecOps context — operators, Helm charts, 2021–2026 activity | GitHub / Public Profile | Medium-High | Confirm hands-on production ownership vs exposure |
| Security clearance fit | Public resume indicates active TS/SCI eligibility | Clearance-oriented sourcing lane | Low-Medium | Verify current clearance status and adjudication date directly with candidate |
| CI/CD background | GitLab CI pipelines and deployment automation referenced across repos and a public talk | Resume / Repo Evidence | Medium | Confirm scale, tooling, and production ownership |
| GovCon adjacency | Past employer appears in the federal contractor ecosystem (prime/sub mapping) | Company Mapping | Medium | Confirm contract/program relevance and any conflict constraints |
| RMF / ATO awareness | "Shifting RMF Left" — public conference talk listing (2025) | Conference / Community | High | Confirm role in ATO packages vs general familiarity |
| Open-to-work signal | "Exploring new opportunities" on a public profile README | Public Profile Signal | Low | Treat as a signal, not a verified claim — confirm interest in first call |
Nothing is marked “verified.” That’s deliberate: open-web signals are leads, not facts — and the distinction stays visible all the way to the hiring manager.
GitHub · Public resume X-Ray · Conference/community · Company mapping
4 of 6 lanes in this role’s source pack yielded evidence. The candidate first surfaced in the GitHub lane — a lane the previous LinkedIn-only search never touched.
OpenAlex · arXiv (research lanes)
Zero results — recorded as a lane outcome, not hidden. Lane yield is tracked so the next search for this role family starts smarter.
This profile matches 3 of 4 must-haves with medium-to-high-confidence public evidence, including the rare combination the HM flagged: platform depth and a credible clearance signal. The evidence spans independent sources (code, talk, resume, company graph) rather than one self-written profile — which is exactly what reduces false-positive risk on hard searches. Project-specific fit draft: 78/100(declared weights; capped by the unverified clearance — this is a fit-for-this-role estimate, never a judgment of the person).
Clearance status is self-stated and unverified — do not represent it to the HM as confirmed. Current employer unknown; public activity may lag reality. Compensation expectations unknown. No certification signals found — absence of public signal is not absence of the credential. Do not assume availability from the open-to-work signal.
1. Clearance level + adjudication date, directly with the candidate. 2. Current employer and prime/sub conflict constraints. 3. Hands-on GovCloud ownership vs adjacency. 4. 8140 certification status (Sec+/CISSP). 5. Interest level and timeline — the open-to-work signal is a lead, not consent.
“Public evidence shows sustained k8s/Terraform delivery and an RMF-aware mindset — a conference talk on shifting RMF left, plus hardened-pipeline repos. The clearance is self-stated; I’ll verify before anything moves. If it holds, this is the depth-plus-clearance profile we haven’t seen in 47 days. One calibration question for you: is hands-on GovCloud a must-have, or trainable in 90 days?”
This dossier is built to be forwarded.
In the beta workbench, Candidate 360s export as hiring-manager-ready summaries — with the evidence ledger, risk flags, and verify-next list intact, so the recommendation travels with its proof.
No silent merges. No invented evidence.
SourcingOS does not infer protected attributes, silently merge identities, invent employment history, or present uncertain data as fact. Identity matches are proposed by the system and confirmed by a recruiter. Human review is required before outreach, submission, or any hiring decision.
Join the private beta