Search Teardown: RHEL Administrator Near Annapolis Junction With Secret Clearance
This is a methodology example, not a report of live candidate results. The point is to show how a senior sourcer should decompose a hard cleared-technical brief before searching.
Last reviewed: 2026-09-06
Ask SourcingOS about this page
1. Preserve the literal brief
Example brief: “Find me a RHEL admin with 5+ years of experience in or near Annapolis Junction, MD with Secret clearance or higher.”
- Role: RHEL / Linux Administrator
- Experience: 5+ years relevant systems-administration evidence
- Location: Annapolis Junction, Maryland area
- Clearance: Secret or higher — verification required
2. Separate normalization from expansion
RHEL can normalize to Red Hat Enterprise Linux because those are the same product name. Linux administration, SELinux, Ansible, Satellite, systemd, LVM, identity management, hardening, and platform-engineering titles are discovery expansions unless the hiring team explicitly made them requirements.
Location expansions such as Fort Meade, Jessup, Laurel, Columbia, Odenton, or nearby Maryland clusters should remain visibly marked as search expansions rather than rewriting the original location requirement.
3. Build independent search lanes
Run direct-title/RHEL lanes, adjacent Linux systems titles, donor-company/GovCon lanes, clearance-language lanes, public technical-evidence lanes, ATS rediscovery, and licensed people-data expansion separately enough to measure contribution.
- Direct: RHEL Administrator / Linux Systems Administrator
- Adjacent: Linux Engineer / Systems Engineer / Platform Engineer
- Environment: hardening, STIG, RMF, ATO, GovCloud where relevant
- Donors: nearby primes, integrators, subcontractors, mission programs
- Evidence: public technical work plus recruiter verification
4. Rank against the brief, not the expansion list
A candidate should not receive credit for “must-have RHEL” merely because they know Ubuntu plus Ansible. Likewise, public “Secret” language can support discovery but cannot be represented as verified current clearance.
The review view should show requirement-by-requirement evidence, missing information, and the exact source supporting each claim.
5. Calibrate after the first slate
Ask the hiring manager whether hands-on RHEL depth, automation, specific security-hardening experience, datacenter/cloud context, or current clearance status is driving rejections. Convert that feedback into an explicit search-plan delta rather than simply searching “more like” one approved person.