How to Write a Cleared Resume Without an OPSEC Violation

If you've spent years supporting a classified program, you already know the anxiety: you need a resume that actually gets you hired, but you also know that a careless bullet point can turn into a phone call from your Facility Security Officer, or worse. Most resume advice online is written for the commercial world and simply doesn't address this. Here's how to write a cleared resume that's both compelling and safe.

Why This Is Genuinely Hard

Unclassified resumes are judged on specificity: "increased revenue 34%" beats "helped grow the business." But in the cleared world, specificity is exactly what can get you in trouble. Program names, customer identities, locations, technical capabilities, and even the existence of certain contracts can be classified or sensitive, even when the fact that "a job" happened isn't.

This creates a strange gap: recruiters and hiring managers want detail to evaluate you, but the details that would make your resume shine are often the ones you're not allowed to write down.

The Core Principle: Describe the Skill, Not the Secret

The safest and most effective approach is to separate what you did (a skill or function) from what it was for (the classified context). Almost every classified task maps to an unclassified verb-and-skill combination.

Notice the pattern: role, function, tools and skills, and impact survive. Names, locations, targets, and program identifiers do not.

A Simple Filter Before You Write Anything Down

Before including any detail, ask yourself four questions:

1. Is this classified at any level, or covered by a non-disclosure agreement, even if the classification itself isn't obvious to you? If yes, generalize it.
2. Could this detail, combined with public information about my employer or unit, allow someone to infer a classified fact? This is sometimes called the "mosaic effect," individually unclassified facts that add up to something classified. If yes, generalize it.
3. Would my Facility Security Officer or program security officer wince if they read this on LinkedIn? If you're not sure, that's your answer, ask them.
4. Am I naming a specific program, customer, platform, or operation? Program names are very often classified or at least sensitive and controlled, even when the general type of work is not.

If a bullet point fails any of these, rewrite it at a more general level rather than deleting the accomplishment entirely. Generalizing preserves the resume value without the risk.

The Formal Requirement Many Veterans Don't Know About: Prepublication Review

This is worth understanding clearly, because it goes well beyond a casual FSO check for some readers specifically. If you're a current or former affiliate of certain agencies, particularly NSA or CIA, you likely signed a non-disclosure agreement that creates a lifetime obligation to submit information intended for public release, and this explicitly includes resumes and LinkedIn profiles, for formal prepublication review before posting it.

• NSA/CSS Policy 1-30 governs review of NSA/CSS information intended for public release by current and former affiliates, in either an official or private capacity, and implements DoD Directive 5230.09 on clearance of DoD information for public release. NSA has published its own explicit resume guidance addressing exactly this situation directly.
• CIA's Prepublication Classification Review Board performs the equivalent function for current and former CIA employees.
• DOPSR (Defense Office of Prepublication and Security Review), housed within the Pentagon, handles broader review of materials from members and veterans of the military and the wider Intelligence Community.

This isn't a bureaucratic formality you can safely skip. It's a binding obligation tied to the non-disclosure agreement you signed, and it has real legal history behind it, the U.S. Supreme Court addressed the prepublication review system directly in Snepp v. United States. If your background includes NSA, CIA, or similar IC service, confirm with your former agency's public affairs or security office whether your resume needs formal review before it goes anywhere public, rather than assuming a general FSO conversation covers it.

What's Almost Always Safe to Include

• Your clearance level and status (for example, "Active TS/SCI with CI Polygraph, granted 2022"), this is standard and expected. Never write the actual polygraph results or investigative details, just level, status, and date.
• Your employer's name, if it's a known defense contractor or government agency, the employer relationship itself is rarely classified.
• Your job title and general duties, described functionally.
• Tools, systems, and methodologies that are unclassified in nature even if used in a classified environment, such as specific programming languages, analytic platforms, tradecraft categories, or general disciplines like network defense or systems engineering.
• Certifications and training (CompTIA Security+, DAWIA, PMP, specific service schools), these are public by design.
• Quantifiable impact stated generically: leading a team of a certain size, reducing reporting turnaround by a stated percentage, managing a budget of a certain size. Numbers are fine when they don't reveal classified capability or capacity information tied to a specific system.

What to Leave Off, Every Time

• Program nicknames, codewords, or Special Access Program names, even ones you've seen unofficially
• Specific adversary nations or groups named as the target of your work
• Specific platforms, sensors, or weapons systems by proper name, unless that system is officially, publicly acknowledged
• Exact locations of overseas or classified facilities
• Customer unit designations below a very general level, naming the agency category is usually fine, naming the specific unit usually is not
• Anything explicitly marked classified, even at the Confidential level, even if you're paraphrasing from memory rather than copying text directly

Where to Put Your Clearance Status

Placement matters almost as much as content. Cleared recruiters often filter by clearance status first, so put it somewhere immediately visible, directly under your name and contact information, or in a dedicated "Security Clearance" section near the top of the resume, especially if you hold multiple clearances or need to note polygraph type and investigation year. Burying this information lower in the document reduces your chances of being surfaced in an initial recruiter search.

Platform Matters: LinkedIn Is Not the Same as a Closed Cleared Platform

This is a nuance worth understanding: what's appropriate to post varies by how public the platform actually is. LinkedIn is broadly, publicly visible to anyone, including outside the cleared community entirely, which is why some practitioners specifically discourage listing polygraph type there, even though clearance level alone is standard. Closed, cleared-industry platforms have a narrower, vetted audience, which is part of why some detail that's discouraged on LinkedIn is more commonly accepted in that context. When in doubt, treat each platform separately, and follow the more conservative standard on anything with broad public visibility.

Handling the "Gap" Problem

A common fear: "If I generalize everything, my resume looks vague and my eight years of experience look like nothing happened." Two fixes:

Lean on transferable skill language, not classified specifics. Frame accomplishments around the function you performed for any qualified reader, a hiring manager with the right clearance and background will recognize what you're describing without you naming names. "Led targeting analysis in support of counterterrorism operations across multiple theaters" tells a cleared reader everything they need to know without a single classified fact.

Use scope and scale, not source. You can usually quantify your impact, team size, budget, number of systems, number of briefings delivered, mission success metrics stated generically, even when you can't say what the mission was. "Provided direct analytic support that contributed to over 200 actionable intelligence reports" is powerful and safe.

The Two-Resume Strategy

Many experienced cleared professionals maintain two versions. A public resume for LinkedIn and general job boards is fully generalized, safe for anyone to read, with no assumption the reader is cleared. A cleared-network resume, submitted directly to a cleared recruiter or through a facility's internal process, sometimes supplemented verbally in an interview, can use somewhat more specific but still unclassified professional language, since the audience is vetted and the venue is appropriate. This still isn't a place for classified specifics, it just allows more industry jargon and program-type language that you might soften for a general audience.

Never assume a cleared job board or cleared recruiter gives you license to include classified information. Clearance verifies trustworthiness and access eligibility, it does not verify need-to-know for your specific program, and it doesn't change classification rules.

If You're Ever Unsure

Ask your FSO or security officer to review your resume before you post it. This is a completely normal request, and most FSOs have seen hundreds of these. It's far better to ask a "silly" question than to self-report a spill later. If your background includes NSA, CIA, or similar service, confirm separately whether formal prepublication review applies to you specifically.

When in doubt, go up a level of abstraction, not down. It's always safer to say "supported national security customers" than to guess at how specific you can be. Classification guidance also evolves. Something you couldn't say five years ago might be releasable now, or vice versa, don't rely on memory of old guidance, check current classification guidance for your program if you have continued access, or ask your FSO.

A Worked Example

Unsafe draft:

"Served as lead SIGINT analyst on a specific named program at a specific base, providing targeting support against a specific country's missile program using a specific named system."

Safe, still strong rewrite:

"Served as lead signals intelligence analyst supporting a national-level customer's missile-defense mission, providing targeting analysis that directly informed senior decision-makers. Managed a two-person analytic cell and briefed findings to O-6 level leadership on a recurring basis."

The second version tells a hiring manager exactly what kind of analyst you are, what your scope of responsibility was, and how senior your audience was, without a single classified fact.

Frequently Asked Questions

Do I need formal prepublication review to post my resume, or is asking my FSO enough?

For most cleared contractors, an FSO review is the standard and sufficient step. If your background includes NSA, CIA, or similar Intelligence Community service, you likely have a separate, lifetime prepublication review obligation tied to your non-disclosure agreement, confirm this directly with your former agency rather than assuming a general FSO check covers it.

Is it safe to list my polygraph type on LinkedIn?

Some practitioners specifically discourage listing polygraph type on broadly public platforms like LinkedIn, even though clearance level alone is standard, while closed, cleared-only platforms are more commonly accepted for that level of detail. When in doubt, treat each platform separately and follow the more conservative standard on anything with wide public visibility.

Where should I put my clearance status on my resume?

Directly under your name and contact information, or in a dedicated "Security Clearance" section near the top. Cleared recruiters often filter by clearance status first, so visibility matters.

Can I be more specific on a resume submitted only to a cleared recruiter or cleared job board?

Somewhat more specific professional language and industry jargon may be appropriate given the more vetted audience, but this never extends to classified specifics. A cleared platform verifies trustworthiness and eligibility, not your need-to-know for a specific program.

What's the biggest mistake cleared professionals make on their resumes?

Naming a specific program, unit, platform, or operation by its proper name. Almost every classified task can be described accurately through function, scope, and impact without naming the specific program or context it occurred in.

Bottom Line

Your resume doesn't need classified specifics to be compelling. It needs clear function, real scope, and honest impact, all things you can describe safely. If your background includes formal prepublication review obligations, take those seriously as a binding requirement, not optional guidance. When in doubt, generalize up, and let your interview, and your security officer, fill in what's appropriate for the audience in front of you.

Ready to find your next cleared role? Browse open cleared positions on Cleared+ →

Reviewed and updated by the Cleared+ editorial team. Sources: NSA/CSS Policy 1-30, DoD Directive 5230.09 (Clearance of DoD Information for Public Release), and public reporting on the Defense Office of Prepublication and Security Review (DOPSR). This article is for general informational purposes and isn't legal advice, always confirm your specific obligations with your FSO or former agency's security office. Have a correction or update to suggest? Contact us.