How to list a government contractor on a resume starts with one factual distinction: your employer, the government customer, and the program are not interchangeable. Name the company that employed you. Add customer or mission context only when it is accurate, relevant, unclassified, and approved for public release under the rules that cover your work.

Who belongs in the employer line?

Use the organization that employed you during that period. A customer agency may have directed the mission, supplied the worksite, or accepted deliverables, but it was not necessarily your employer. Presenting it as one can create a false employment history and confuse verification.

USAJOBS tells applicants to include an employer name for each relevant work-experience entry. Its federal resume guidance separately calls for the job title, dates, work schedule, and descriptions showing relevant performance. That structure supports a clean contractor entry:

Company Name | Functional Job Title | City, State
Context: Supported a federal customer in an approved, unclassified mission area.

If you worked at a customer site, “supporting” or “on contract to” is usually clearer than placing the agency where the employer belongs. For a classified contract, ask the security office whether the customer may be named; the contract’s classification guidance decides. The NISPOM lets the contractor disclose, without a separate approval request, that a contract has been received and its subject in general terms, unless the government contracting activity prohibits it and provided the name or description of the subject is not classified (32 CFR 117.15(h)(8)(ii)(A)). Where naming the customer is not cleared, use a truthful general description such as “federal civilian customer” or “defense customer.”

The distinction complements the broader essentials of a government-contracting resume.

How should you separate company, customer, and program?

Give each entity only the role it actually held. The company belongs in the employment header. A releasable customer can appear in a context line. A program name belongs nowhere unless you have confirmed it is both unclassified and authorized for public use.

A recruiter may know the customer from the requisition. That does not authorize you to confirm a relationship omitted from public materials. You can still show fit through tools, methods, work products, decision scope, and results at the level your review authority permits.

How do you describe mission work without naming protected details?

Translate the work into function, constraint, action, and approved result. Replace a protected program name with the type of problem you solved. Replace an internal system label with a generic system class. Keep the description useful enough to support qualification, but no more specific than release rules permit.

NSA’s resume dos and don’ts offers a practical model for people covered by its guidance: describe projects in an unclassified manner without project names and prepare an external resume specifically for public dissemination. It warns against protected mission, infrastructure, location, project, application, supervisor, and marking details.

Those NSA instructions bind their intended audience; they are not a substitute for your employer’s rules. Their drafting logic is broadly useful, though. “Maintained named system at protected site supporting named target” reveals associations a reader does not need. “Maintained high-availability operational systems under strict change control” shows the skill without exposing the protected nouns.

Never copy a classified or internal staffing resume and merely delete the visible markings. NSA explicitly distinguishes a public external resume from an internal staffing document with markings removed. Start a clean document, using only releasable source material.

When is a number too sensitive for a resume?

A number is safe only when the underlying fact is accurate and its release is authorized. Staffing, budgets, equipment quantities, coverage, response volumes, performance, or site capacity can reveal protected scale even when every word around the number is unclassified.

NSA’s guidance specifically warns its audience about infrastructure information revealing strength, budget, or structure, including staffing and project-budget figures. Your program may draw different boundaries. Ask whether the quantity is already officially public, approved through review, or permitted by written guidance.

If exact scale is not releasable, do not invent a vague substitute that still signals sensitive capacity. Shift to the type of responsibility: led cross-functional coordination, improved a controlled process, reduced recurring rework, restored service within approved requirements. Quantify only the dimensions cleared for public use.

A job posting that asks for metrics does not override security duties. You can tell the recruiter that certain scale details are unavailable publicly and offer an approved description of complexity, decision authority, or result instead.

How should contract transitions appear?

Follow employment records, not the program’s continuity. If a recompete moved you to a different employing company, create separate employer entries and make continuity clear in the bullets. If the prime changed but your own employer did not, do not invent a new job solely because the contract structure changed.

For a genuine employer change, use the real end and start dates. A short context line can say that you continued substantially similar approved work after a contract transition, if that fact is releasable. Avoid claiming the government “transferred” or “retained” you unless that wording accurately describes a documented action.

For unchanged employment, one entry may include a carefully worded note about supporting successive contract vehicles only when naming that transition is permitted and useful. Often the better choice is to show progression in responsibility without discussing procurement history.

The reader can then see why company names changed without mistaking continuous customer support for continuous employment with one firm.

What details should you remove before public circulation?

Remove classified information, government-sensitive information, classification markings, codewords, protected project names, internal system identifiers, sensitive sites, target descriptions, protected unit associations, and operational details. Then review combinations. Individually harmless facts can become revealing when assembled in one bullet.

USAJOBS expressly tells applicants not to include classified or government-sensitive information. Cleared candidates should also check which personal and sensitive details to leave off a cleared resume, including data that creates privacy risk without proving qualification.

Do not replace a forbidden detail with hints that invite the reader to infer it. Phrases such as “you know the agency” or conspicuous redactions look evasive and add no evidence. Write the approved public version as a complete professional statement.

Check file properties, comments, tracked changes, hidden text, headers, and the filename. A clean visible page can still carry an internal program label in metadata. Export from the public-source document and inspect the final file before uploading.

When is security or prepublication review required?

Follow the obligations that cover you: employer policy, contract guidance, nondisclosure agreements, agency prepublication rules, and instructions from the security office. Clearance review is not a universal one-size process, and an old approval does not automatically cover newly added text.

For cleared contractors, 32 CFR 117.15(h)(8) binds the contractor not to disclose classified information publicly. It also requires prior review and clearance for public disclosure of unclassified information about a classified contract as specified in the contract’s classification guidance or by the government contracting activity.

The same paragraph contains exceptions unless the government contracting activity specifically prohibits them, including certain general contract facts and information already officially approved. Read the entire provision and the contract-specific direction. The exception is not permission for an employee to guess which resume detail falls within it.

Send the security or prepublication office the exact version you plan to use, in the format and channel it requires. Keep the response and approved copy. If you later add a customer, metric, location, project description, or new accomplishment, ask whether the revision needs another review.

What does a safe before-and-after entry look like?

The goal is not to make the work empty. It is to replace protected nouns and unreleasable scale with credible, approved evidence of skill. The revised bullet should still identify what you did, how you did it, and why the result mattered.

For clearance presentation itself, follow the separate guidance on how to show a security clearance on a resume. Eligibility wording does not authorize disclosure of the programs, accesses, or work behind it.

Frequently Asked Questions

Should I list the agency or the contractor as my employer?

List the company that employed you. If agency context is releasable and relevant, place it in a separate context line or bullet using wording your security process permits.

Can I name a classified customer if everyone in the field knows it?

Industry awareness is not release authority. Use only information approved for public use under your employer, contract, agency, and nondisclosure requirements.

Can I use a codeword without explaining it?

A codeword or project name may still be protected, and without approved context it rarely proves a transferable skill. Replace it with a releasable functional description.

How do I show impact when metrics are sensitive?

Use approved evidence such as the type of decision, process improvement, reliability outcome, coordination scope, or user benefit. Quantify only what the proper review authority has cleared.

What should I do before sending the resume?

Verify each employer line against your records, remove protected and government-sensitive details, inspect the file metadata, and submit the exact external version to the required security or prepublication review channel before circulation.