The Cleared Defense Engineer's Resume Playbook: TS/SCI, Polygraphs, and What You're Allowed to Say

The cleared talent shortage and why your resume is leverage right now

Clearance levels decoded

Most recruiters know Secret and TS/SCI. Few know the full hierarchy, and almost none understand reciprocity. Use the exact language in the second column on your resume; do not invent variations.

Trusted Workforce 2.0 has moved most levels from periodic reinvestigation to Continuous Vetting via DISS and (rolling out) NBIS. Reciprocity between DoD and IC is generally fast under TW 2.0; DOE Q has limited reciprocity with DoD TS and almost always requires a separate adjudication.

Polygraph types compared

Polygraph type is one of the highest-value pieces of information on a cleared resume. List it precisely if you have it; never imply one you do not hold.

If your polygraph is more than 7 years old, list the year and call it "prior" rather than "current"; sponsoring agencies define currency, and overstating it is a falsification risk.

Cleared resume terminology cheat sheet

These are the terms a cleared recruiter scans for and an uncleared recruiter glosses over. Use them precisely. Misusing them flags you as uncleared trying to look cleared.

SCIF

Sensitive Compartmented Information Facility. The accredited room/space where SCI work is performed. You may say you worked "in a SCIF environment"; do not name the SCIF or its location.

SAPF

Special Access Program Facility. The SAP equivalent of a SCIF. You may say "SAPF environment"; you may not name the program.

FSO

Facility Security Officer. The cleared employee at a contractor responsible for personnel security. Your FSO is your first call before you publish a resume.

JPAS

Joint Personnel Adjudication System. Legacy DoD clearance database. Decommissioned 2021; replaced by DISS. Do not list JPAS unless describing legacy work.

DISS

Defense Information System for Security. Current DoD system of record for clearance status. Recruiters verify your eligibility via a DISS visibility request.

NBIS

National Background Investigation Services. DCSA's next-generation system, rolling out to replace DISS. Mentioning familiarity is a plus for FSO and security-engineer roles.

Scattered Castles

IC system of record for SCI eligibility. The IC equivalent of DISS. Listing prior IC sponsorship implies a Scattered Castles record without naming it.

CONOPS

Concept of Operations. Used in defense and IC program documents to describe how a system or mission will be employed. Strong keyword for systems engineering bullets.

OPSEC

Operations Security. The discipline of protecting unclassified-but-sensitive information. Your resume itself is an OPSEC artifact.

COMSEC

Communications Security. Covers cryptographic key handling, secure-comms equipment, and related controls. "COMSEC custodian" is a specific, listable role.

CUI

Controlled Unclassified Information. Replaced FOUO and most legacy markings in 2020. List CUI handling experience verbatim; it is current and searchable.

FOUO

For Official Use Only. Legacy marking, deprecated under the CUI program. Use CUI on a 2026 resume unless describing pre-2020 work.

DoD 8140 / 8570

DoD cyber workforce qualification standards. 8140 superseded 8570 in 2023. Always use 8140 on a 2026 resume; reference 8570 only when describing certifications earned under the older framework.

Insider Threat

Formal program required of every cleared contractor under NISPOM. Listable as "Insider Threat program contributor" or "Insider Threat working group member" if you served on one.

OPSEC: what you can say vs what gets you a security incident

The NSA Prepublication Office's "Resume DOs and DON'Ts" is the canonical reference. Six rules below cover 90% of the cleared-resume mistakes that get FSOs called.

Before/after: a TS/SCI software engineer bullet

Same accomplishment. The before version reads either uncleared or, worse, OPSEC-noncompliant. The after version is what a cleared recruiter expects to see.

Wrote Python and C++ for the TITAN SHADOW SIGINT pipeline at the Fort Meade SCIF, processing collected foreign communications from the [target country] desk for the NSA S2 mission.

Built and maintained a high-throughput Python/C++ SIGINT processing pipeline in a SCIF environment, supporting national-level intelligence customers; reduced end-to-end processing latency 38% and added unit-test coverage from 22% to 81% across the core analytic library.

Where cleared talent goes (and what each prime hires for)

These ten employers run the largest cleared workforces in the US. Match your portfolio to one or two clusters before you start applying; recruiters at primes can spot a generic resume in seconds.

DoD 8140 cert-to-role map

DoD 8140 superseded 8570 in 2023 and is the qualification standard every cleared cyber and IT role on a DoD contract must meet. List your baseline cert by name; recruiters search on the cert string.

All certifications must be CE (Continuing Education) variants where applicable, and must be active. List the cert plus the year achieved (e.g., "CISSP (2023, current)"). The full official table lives at public.cyber.mil.

Inactive clearance: how to position the gap honestly

30-day pre-application checklist for cleared applicants

Run this list before you submit a single application. Each step is non-negotiable for cleared roles and most are skipped by uncleared engineers, which is exactly why their resumes underperform.

1. 01

   Days 1-3: Sit down with your FSO before you publish anything

   Your Facility Security Officer is the only person at your current employer authorized to tell you what is and is not OPSEC-safe to disclose. Bring a draft resume; ask specifically about program names, SCIF locations, customer names, and any classified contract numbers you may have referenced.

2. 02

   Days 4-7: Pull your DISS visibility and verify your record

   Confirm your clearance status, last investigation date, last polygraph (type and date), and any incident reports. Recruiters will request a DISS visibility on you within hours of an offer; you do not want surprises.

3. 03

   Days 8-12: Refresh your DoD 8140 baseline cert

   If you hold Sec+, CASP+, or CISSP, confirm CE status and CPE balance. If your baseline lapsed, schedule the exam now; most cleared cyber and IT roles are non-negotiable on the 8140 baseline.

4. 04

   Days 13-17: Build the cleared-only resume version

   Maintain two files: a sanitized public version (no SCIF locations, no programs, generic mission language) and a cleared-only version with the additional context you would share inside a SCIF interview. Deliver the cleared version only through a cleared recruiter or a contractor portal that verifies clearance.

5. 05

   Days 18-22: Refresh your reference list to include cleared peers

   Cleared employers often request cleared references who can speak to your work in a SCIF or SAP environment. Identify 3 to 5 cleared colleagues, confirm they will take the call, and store their non-work contact info.

6. 06

   Days 23-27: Polygraph readiness if you have a poly date scheduled

   If a sponsor will run you on a CI or full-scope poly within 60 days, abstain from polygraph-relevant risk behaviors, document any foreign travel and contacts since your last poly, and review your SF-86 entries for accuracy. Recruiters do not pre-screen for this; you must.

7. 07

   Days 28-30: Run the public resume through ATS scanners against 3 cleared JDs

   Score the sanitized version against one prime (Lockheed/Northrop/RTX), one integrator (Booz Allen/Leidos/CACI), and one cleared frontier-tech employer (Anduril/Palantir). Variance across the three tells you which keywords (CONOPS, RMF, DISA STIG, AWS GovCloud, DoD 8140 baseline) you are missing.