The Military-to-Civilian Resume Translation Reference, Term by Term

This is a lookup document for translating a military service record into civilian resume lines. It is for service members leaving active duty, reservists moving to a civilian search, and veterans whose current resume still reads in code. Every generic guide tells you to translate jargon and quantify results, then leaves you to figure out that a 68W maps to EMT or that an expired clearance cannot be written as "Active." This reference gives you the row: each service element with its civilian phrasing, what it proves, how it misleads, and where on the page it goes. Jump to your own MOS, rank, or clearance status and leave with a line you can paste.

Why the DD-214 is the wrong place to start

The DD-214 is a verification document, not resume content. It was built to prove honorable discharge and support VA claims, and it has approximately 30 data blocks: name, rank and pay grade, dates of service, separation and reentry codes, primary MOS, AFSC or rating, and character of discharge. None of that is written to persuade a hiring manager.

The problem is density, not accuracy. A recruiter who reads "25B - Information Technology Specialist" straight off the form still has no idea whether you managed 5 servers or 500, led a team of 2 or 20, or handled a budget of $10K or $10M. The line is true and useless at the same time.

The numbers that make you hirable live somewhere else. Your NCOERs, OERs, FITREPs and EPRs carry the specific accomplishments: headcount, dollar values, systems run, outcomes, and leadership evidence. So the correct starting move is to pull the evaluations, not to paste the form. A resume built only from the DD-214 is structurally weak because the document was never meant to hold that content.

MOS to civilian job title: the lookup that translates your code

Translate every code through the O*NET Military Crosswalk before you write a single title. The tool matches military occupations to civilian ones by skill set, and you search it by branch, by military code, or by a title keyword.

The procedure is short. Use the dropdown to select your branch, enter your military code (for example 92Y for Army or 0311 for Marines) or a title keyword, and click Go. Open a Summary Report and read the Tasks and Skills sections. If those tasks match what you actually did day to day, that occupation is a strong resume candidate. Keep one to three titles per code and discard the rest.

Behind the tool is the Military Occupational Classification crosswalk maintained by the Defense Manpower Data Center, supplemented by enhanced Labor and Defense analysis under Section 222 of the VOW to Hire Heroes Act. The crosswalk files were updated in August 2024. A parallel path is the DOD COOL portal, and the CareerOneStop translator covers the same ground from the other direction.

One caveat controls the whole exercise: MOC codes are often reused for unrelated titles, which produces diverse and sometimes confusing results. This is why the Tasks section is the arbiter, not the title list. A single trade shows how wide the mapping runs.

The crowded return in both directions is the reason you never trust the first title the tool surfaces. Read the daily tasks, keep only what matches your work, and let the Summary Report, not the code, decide.

Rank to civilian scope: translate the job, not the title

Translate rank into scope, never into a one-to-one title. Ranks and civilian titles do not line up cleanly across every field, so a rigid chart can inflate you into a director you were not or shrink you below what you led. The reliable move is to describe scope in civilian terms: headcount led, budget or equipment managed, systems run. A recruiter who reads "led 12 people and managed $2M in equipment" understands your seniority instantly.

Use the table below as a starting read, not a rule. It is practitioner framing, not an official equivalency chart.

The warrant officer row deserves special care. A W-1 to W-5 is a deep technical authority, and the mistake is to translate the rank as junior because the number looks low. Scope a warrant officer as a principal engineer or senior specialist, and let the technical depth carry the line. The O-3 Captain who commanded a company of 100 to 200 people plus equipment and budget is senior manager or junior director scope, and should be written that way even though "Captain" means something different in a civilian org.

How to list a security clearance on a resume, by status

Write the clearance line that matches your verifiable status exactly, because employers check it through DISS and any gap between your wording and the record rejects your candidacy. The three statuses map to three different lines. Statute sets the reinvestigation intervals - 5 years for Top Secret, 10 years for Secret, and 15 years for Confidential - and a clearance can be reinstated within 24 months without a new investigation. Past 24 months, a new investigation is required.

The honesty math shifted quietly. By September 2021, over four million national security positions had moved to continuous vetting, which eliminated fixed periodic reinvestigations for many roles. That means the old "5-year TS" framing can now read as dated. A current-status line - "eligibility on file," with a date - ages better than a hard expiry claim and is easier to defend when a recruiter pulls DISS.

Use standard abbreviations. Write "TS/SCI," not "Top Secret/SCI" and not "TSSCI," because recruiters search their ATS for the standard token, and defense contractor recruiters report using "TS/SCI" as their first filter. The token is a search key, so an off-standard spelling can hide you from the exact search you want to appear in.

Active:   Active TS/SCI (current through 2027) | Character of service: Honorable
Inactive: TS/SCI eligibility on file, last active 05/2024 (within 24-month reinstatement window)
Expired:  Previously held Top Secret (T5, DoD, adjudicated 2020)

The scarce band: cleared plus proven senior scope

Clearance is common; clearance plus proven senior leadership is not. This is the single most useful strategic fact for a transitioning veteran, and it changes where you spend your effort.

In Refolk's index of professional profiles, only a small slice of that pool sits at the top of the scope ladder.

The read is direct. A cleared veteran who can credibly frame Director-scope leadership competes in a band that holds roughly one in eleven of the cleared population, not in the crowded base of a quarter million. That is the entire argument for spending real time on step 3, the rank-to-scope conversion. The clearance gets you into the search. The proven scope gets you out of the pile.

Clearance opens the search. Proven senior scope decides whether you win it.

This is exactly the kind of narrow, high-value search a hiring team runs when they need cleared leadership rather than cleared headcount.

OPSEC: what stays off the page, and what to write instead

Some details cannot go on a public resume no matter how much they would strengthen it, and the substitution rule is fixed: replace the proper noun with a category. NSA prepublication guidance is explicit that a resume must be completely unclassified and must not knowingly include operationally sensitive information, including anything marked For Official Use Only.

The following must stay off a public resume:

• Mission, operation, and exercise names.
• Agency-level customer names such as NSA, CIA, NRO, NGA, and DIA.
• Specific program names and non-public system names.
• Classified personnel counts.

The fix is to generalize, not to delete. A program name becomes "a defense customer." An agency becomes "a national-security customer." A classified headcount becomes a scoped but unclassified figure if one exists, or a scope description if it does not.

The subtle leaks are the dangerous ones. A line like "Analyzed Chinese cyber espionage operations" reads as a strong accomplishment, but it can reveal collection priorities, so it must generalize to a threat category. The test is whether the line survives being read by someone outside your clearance. If it would tell them something they should not know, rewrite it before it reaches a public page.

Awards and schools: translate selectivity, not the badge

Convert military training into a signal any civilian understands: competitive selection, survived. The badge means nothing to a non-veteran, but the attrition number does the persuading.

Selective schools translate as competitive-selection evidence. Frame Airborne as a roughly 3-week program with about 20% attrition, and Ranger as a 62-day advanced leadership course with a graduation rate under 50%. Air Assault and Pathfinder follow the same pattern - name the selectivity, then let the reader draw the conclusion. The point is not the tab; it is that you were selected for and completed a program most people do not finish.

Awards need a citation-based civilian line. Keep any award that came with a citation - Bronze Star, Meritorious Service Medal, Joint Service Commendation Medal - and reframe the citation in civilian terms with a one-line description of what you actually achieved. An award with no translation is a decoration a civilian recruiter cannot weigh.

Placement is where this most often fails. Military training has civilian market value only if it sits where employers look for credentials. Burying "Ranger School" inside an experience bullet wastes it. Put selective schools and awards in Education or Certifications, with the civilian translation attached, so a scanner finds them where credentials belong.

Ranger School - 62-day advanced leadership course, graduation rate under 50%
Airborne School - selective 3-week program, ~20% attrition
Meritorious Service Medal - recognized for [one-line civilian achievement: outcome, scale, impact]

Placement and the six-second scan

Where each element sits on the page decides whether an ATS and a human ever see it. Hiring managers scan a resume in an average of six seconds, and a parser only files text into a structured field if it appears where the parser expects it.

Clearance belongs in the header, directly under your name and contact information, before the professional summary. This is mechanical, not cosmetic. Clearance language in the header is captured into the structured Security Clearance field at a notably higher rate than the same wording in a summary paragraph or a bullet, and that structured field is what recruiters filter on. Header placement is the difference between appearing in a cleared-talent search and not appearing at all. Some sources place clearance in a footer or an "Additional Information" section; the parser finding backs the header camp, so default to the header.

The character of service line pairs naturally with clearance in the header. The MOS-derived title goes into experience with its scope numbers. The skills block holds the standard tokens the ATS searches for, mirrored to the target posting's language.

The translation procedure, end to end

Run these steps in order. Steps one and two build your raw material, three and four make it civilian and safe, and five through seven put it on the page where it will be found.

Refolk can compress the middle of this run: it writes the resume from your own history, tailors it to each posting's language, and scores how well you actually fit, which is the tailoring work step seven describes done at scale across a batch.

How the translation goes wrong

Most failed military-to-civilian resumes fail in one of eight specific ways. Each has a check you can run before you send.

The most damaging is writing "Active" on a clearance that is past its window. It reads to a recruiter as "ready tomorrow," but the moment it is checked against DISS it rejects the candidacy and raises integrity questions. The line does the opposite of what you wanted.

Blind trust in a rank chart is the second. Because ranks and civilian titles do not line up cleanly across every field, a chart can inflate or deflate you. Verify with actual scope numbers instead of a lookup row.

Leaving an MOS code raw is the third. A civilian recruiter and an ATS both read "25B" or "E-6" as noise. The check is simple: would a non-veteran friend understand the line? If not, it is not translated.

Reused MOS codes are the fourth. Because codes are often reused for unrelated titles, the Crosswalk can hand you a title that has nothing to do with your work. Confirm the Summary Report tasks match your actual daily job before you adopt it.

The OPSEC leak via a "harmless" detail is the fifth and the most easily missed. A line naming a specific adversary's operations can reveal collection priorities. Generalize to threat categories.

Pasting the DD-214 as a resume is the sixth. "25B" alone tells a manager nothing about servers, team size, or budget. Check that every line carries a number.

Burying a selective school in a bullet is the seventh. It wastes the strongest credential on the page. Move it to Education or Certifications with the attrition framing.

Putting clearance in the footer is the eighth. Header placement is captured into the structured Security Clearance field recruiters filter on at a higher rate than a buried mention, so a footer clearance may never populate the field a search runs against.

Keeping the resume current

The translation is not a one-time job, because two things underneath it move. Clearance status changes on a clock, and the crosswalk data updates.

Track your clearance window against real dates, not memory. The 24-month reinstatement window is the hinge: inside it, you write "eligibility on file, within reinstatement window"; outside it, you write "previously held," and the honest line changes on a specific day. Because continuous vetting has replaced fixed reinvestigations for many positions, re-confirm your own status rather than assuming the old periodic timeline still describes you. When in doubt, the verifiable current-status line is safer than a hard expiry claim, and it survives a DISS check.

Re-run the Crosswalk when you retarget. The MOC crosswalk files were last updated in August 2024, and the civilian title that reads best depends on the posting you are chasing. Before a new batch, re-open the Summary Report for your codes, confirm the tasks still match the roles you want, and refresh the skills block with the target posting's exact tokens.