Free Tool

Clearance Search Builder

Build search strings for cleared and GovCon roles the way a cleared recruiter actually runs them: clearance terms in the LinkedIn Recruiter and ClearanceJobs lanes where candidates self-attest, and deliberately out of public X-Ray, where the open web can’t verify clearance and the term mostly returns job posts. Pick a level, poly, cert focus, and market — get four lanes plus a downloadable pack.

Role / title

Location / market (optional)

LinkedIn Recruiter (clearance OK — self-attested)

("DevSecOps Engineer" OR "Platform Engineer" OR "Cloud Engineer" OR SRE) AND ("TS/SCI" OR "TS SCI" OR "Top Secret SCI") AND (Security+ OR CISSP OR AWS OR Terraform OR Kubernetes) AND (Fort Meade OR "Annapolis Junction" OR Columbia MD) NOT (student OR instructor OR professor OR bootcamp OR sales OR "help desk" OR "desktop support")

Clearance terms allowed here; treat any match as candidate-stated, not verified.

ClearanceJobs keyword line

("DevSecOps Engineer" OR "Platform Engineer" OR "Cloud Engineer" OR SRE) AND (Security+ OR CISSP OR AWS OR Terraform OR Kubernetes)

Run inside ClearanceJobs; the platform already scopes to cleared candidates.

Public Google X-Ray (NO clearance terms)

site:linkedin.com/in ("DevSecOps Engineer" OR "Platform Engineer" OR "Cloud Engineer" OR SRE) (Security+ OR CISSP OR AWS OR Terraform OR Kubernetes) (Fort Meade OR "Annapolis Junction" OR Columbia MD) -intitle:jobs -inurl:jobs

Clearance intentionally omitted — the open web cannot verify it and the term mostly returns job posts.

GitHub skill lane

site:github.com (AWS OR Terraform OR Kubernetes)

Skill signal only. Clearance is never inferable from code.

Verify directly, every time. Clearance level, adjudication date, and poly status cannot be confirmed from public sources. Any clearance term a candidate lists is self-stated until you confirm it with them and the facility security officer. SourcingOS never represents an unverified clearance as a fact.