Amentum's 382 in Hanover: The TS/SCI Resume When the Contract Walks

Amentum has filed three WARN notices in six weeks, and they are not the same layoff twice. 382 in Hanover tied to intelligence contract transitions, 77 at Fort Eisenhower, and 70 at Kennedy Space Center after NASA pulled Base Operations and Spaceport Services back in-house. If you are cleared and your badge just stopped working, the resume you wrote for your last recompete is going to lose you the next one.

What actually happened in six weeks

Amentum stacked three distinct WARN shapes that together map the dominant 2026 cleared-contractor layoff pattern: a prime-to-prime intel recompete, a security and SOC contract flip, and a federal insource. The mission did not move. The contract did.

• Hanover, MD (7710 Milestone Parkway): 317 cuts effective Oct. 31 plus 65 effective Nov. 13, for a total of 382. Maryland typed both notices "Mass Layoff - No Recall." The first filing breaks out as 317 facilities support services workers and 65 engineering services workers. Amentum spokesperson Chanel Mann attributed the cuts to the "transition of certain intelligence contracts" and named no successor prime.
• Fort Eisenhower (Augusta, GA): 77 intelligence-related jobs with first separations Oct. 31. The role mix is 27 guards, 22 computer operators, 17 alarm monitors, one access-control specialist, one admin, one program-projects manager, and one program-project supervisor.
• Kennedy Space Center (FL): 70 positions effective Nov. 30 after a NASA directive to insource Amentum's Base Operations and Spaceport Services (BOSS) division. Roles include engineers, technicians, planners, and analysts. 14 of the 70 are represented by a union.

The common thread: no recall language, no named successor, and in Kennedy's case, no successor at all. The surviving contract is going to a federal employee.

Why the "wait for the recompete" reflex is dead this quarter

Mass Layoff - No Recall is the legal reason you cannot wait, but the structural reason is the DMV labor pool. The Hanover 382 lands into a Maryland market that has already absorbed 29,200 lost federal jobs between January 2025 and April 2026, per a Maryland Comptroller analysis published through Brookings' DMV Monitor. You are not waiting for a recompete, you are competing against roughly 76 other displaced federal workers for every seat on your WARN.

Amentum's own 2026 WARN volume underlines it: 8 notices affecting 714 workers as of late September. The company employs about 50,000 globally, so no single WARN is big enough to generate a public severance norm or a dedicated outplacement vendor. You are rewriting the resume alone, and you are rewriting it against time.

The second structural shift is NASA's. Administrator Jared Isaacman announced in February 2026 that technical and operational work would move from contractors to civil servants, with "rapid onboarding." NASA also lost 22% of its civilian workforce in 2025. That means the insourcing is happening on a leaner civil-service base, which raises the technical bar for the federal-employee conversion a BOSS worker can realistically target. Amentum told analysts it now expects a 3% negative FY2027 revenue impact from NASA insourcing, up from a 1% estimate in Q2. That revision is why Kennedy is not the last BOSS-style WARN you will see.

The one phrase that has to leave your resume

"Transition of certain intelligence contracts" is what Amentum put in the WARN. It is also, almost verbatim, what cleared workers put in their next resume. Delete it. The next prime's recruiter is not searching for "Amentum" or for a program codename. They are searching for the mission function.

Rewrite in the opposite direction:

• Not "supported transition of intelligence contract at [COCOM]." Instead: "SIGINT target development against [sanitized target set], producing N finished intel products per quarter for [consumer command]."
• Not "performed contract-funded insider threat work." Instead: "insider-threat monitoring across 14,000-endpoint enclave, triaging DLP alerts in Splunk ES and escalating to CI."
• Not "facilities support services under prime contract." Instead: "access-control systems integration across SCIFs at three DoD sites, including Lenel OnGuard migration and TSCM coordination."

The mechanism is simple. Program codenames get sanitized to the point of invisibility. Mission functions do not. Pasting the posting into Refolk and getting your own resume back rewritten against the exact keywords the recompete's prime is screening on is the shortest path from WARN to interview, especially when you have 60 days of runway and no recall.

The Refolk index: who you are actually competing with

There are 31,775 US professionals with TS/SCI in their headline or profile in Refolk's index. Narrow to the title families being cut at Hanover and Fort Eisenhower (Intelligence Analyst, Cyber, Systems Engineer, Program Manager) and the number collapses to 709. Program Manager alone is about 9 of those 709, roughly 1.3%, which is why PM is the single hardest title to differentiate on and why "managed $XM program" bullets vanish into the pool.

The practical read: if your title is Program Manager, your resume has to carry a number no one else in those 709 can carry. EVM metrics, CPI and SPI held to within a stated band, cost-at-complete variance against baseline, FFP transition experience. Which brings us to the next shift.

FFP is the new resume bullet nobody has

Some remaining NASA contract work is transitioning to firm-fixed-price in line with an April executive order, which means cost-discipline muscle is suddenly the scarce signal. Most T&M contractor bullets do not demonstrate it. If you survived a prior FFP transition, surface it: baseline cost at award, actual cost at delivery, EVM reporting cadence, who ate the overrun.

The surviving primes (CACI, Leidos, Deloitte, TekSynap, Barbaricum, and IntelliBridge all show up as current TS/SCI employers in Refolk's index) are reading proposals under the same executive order. A bullet that says "led FFP conversion from T&M on $14M task order, held CPI at 0.98 across 11 months" is worth more right now than another "cleared PM, 10 years." The pool does not have it.

Fort Eisenhower's 77 is a different resume

The Fort Eisenhower cuts are not an analyst layoff. They are a guard-force and SOC layoff, and the resume rewrite audience is physical security, SOC and NOC operations, and alarm monitoring, not intel analysis. Writing one resume for all 77 would miss the market by a wide margin.

The role mix dictates three distinct rewrites:

1. 27 guards: target DoD base-security contracts under the next prime, plus commercial physical-security roles at data-center operators and campus security at primes with their own cleared facilities. Lead with armed/unarmed status, DA Form 7708 history, and specific post experience.
2. 22 computer operators and 17 alarm monitors: this is SOC Tier 1 to Tier 2 work in cleared language. The rewrite moves it into commercial SOC vocabulary: SIEM (Splunk, Sentinel), ticket volume per shift, mean time to acknowledge, escalation runbooks. Managed security service providers hire for this all day.
3. The access-control specialist and the two program leads: physical security engineering is a narrow commercial market (badging systems, Lenel and Genetec integrators) but it pays, and the specialist title transfers cleanly if the resume names the systems.

Guards applying to SOC jobs with a guard resume will not clear a parser. The exact rewrite work, posting by posting, is what Refolk is built to do: paste the SOC listing, get the guard-force experience reframed as monitoring and incident response in the vocabulary the SIEM-literate recruiter is scanning for.

Kennedy's 70: the federal resume most contractors have never written

The Kennedy BOSS workers have a lane the Hanover and Fort Eisenhower workers do not: they can apply to NASA as civil servants, because that is literally where the work is going. Isaacman's "rapid onboarding" line is public policy, not a hint.

The federal resume is a different document. It is not a one-pager. It carries hours per week for each role, GS-equivalent grade, supervisor name and whether they can be contacted, and KSA (Knowledge, Skills, Abilities) narratives against the specific announcement. Most laid-off contractors have never written one and apply to USAJOBS with their commercial resume, which gets scored to failure.

The pivots a BOSS engineer, technician, planner, or analyst should run in parallel:

• NASA civil-service conversion via USAJOBS, federal format, KSA narratives written against the announcement.
• Commercial space on the Space Coast: BOSS supports SpaceX, Blue Origin, Boeing, Lockheed Martin, and United Launch Alliance operations. Launch operations, range safety, ground systems, and spaceport logistics map directly, and the resume stays commercial format.
• Next prime for whatever BOSS successor contract eventually appears: assume this is the slowest path and do not plan around it.

The 60-day plan if your badge stops working Oct. 31

The urgent sequence for a cleared worker on a No-Recall WARN is clearance protection first, resume second, applications third, references fourth. The order matters because clearance currency drives everything downstream.

1. Days 1 to 3: confirm clearance status in DISS, request a copy of your SF-86 export from your FSO before the badge dies, and get your most recent SCI indoc dates in writing.
2. Days 3 to 10: rewrite the resume by mission function, not program. Build one master and one federal variant if NASA conversion is in play. Strip every acronym a non-cleared recruiter cannot parse, then add a cleared-only addendum.
3. Days 10 to 45: apply in parallel to the likely landing primes (CACI, Leidos, Deloitte, TekSynap, Barbaricum, IntelliBridge for Hanover intel; MSSPs and base-security primes for Fort Eisenhower; NASA USAJOBS plus commercial space for Kennedy). Tailor each application to the posting.
4. Days 45 to 60: references and read-ons. A cleared reference who can confirm your SCI access is worth three commercial references. Line them up early.

Clearance currency windows are usually 24 months out of access before you require reinvestigation, but confirm against your specific agency's rules. If you are inside the window, say so on the resume, in plain English, in the summary line. Recruiters are searching for it.

FAQ

Does Amentum offer severance or outplacement I should factor into the timeline?

No public severance norm has been reported for the 2026 Amentum WARNs, and Maryland typed both Hanover notices Mass Layoff - No Recall. Assume the WARN pay period is your runway and plan the 60-day sequence against the stated effective date. If HR offers more, treat it as upside.

Should I keep my clearance language on a commercial resume?

Yes, but surgically. Put "Active TS/SCI with CI poly, current as of [date]" in the summary line and in a one-line clearance block. Do not pepper acronyms (SAP, SCIF, GENSER, DCID 6/9) through the bullets of a resume you are sending to a commercial recruiter. They will not parse, and they signal that you have not rewritten for the audience.

Can I target NASA as a civil servant if I was an Amentum BOSS contractor?

Yes, and the Kennedy insourcing is the specific case where the policy intent is on your side. Isaacman's "rapid onboarding" directive plus the fact that your exact work is now a federal billet makes BOSS workers natural candidates. The catch is the federal resume format: hours per week, GS-equivalent, supervisor contactability, and KSA narratives against each USAJOBS announcement. Write it as a separate document, not a reformat.

What is the single most common mistake on a cleared resume after a contract transition?

Leading with the program codename or the prime instead of the mission function. Recruiters at the next prime search for SIGINT, DCGS-A, insider threat, Lenel, Splunk ES, EVM, CPI, and FFP, not for "Amentum" or a sanitized program name. Rewrite every bullet around what you did for the mission, not which contract vehicle funded it.