Military to civilian resume: translating the experience section
The O*NET crosswalk gives you occupations, not job titles. Here is how to turn a service code into an experience section a recruiter can actually read.
Nathan Cole · · 9 min read
Short answer: run your service code through the O*NET military crosswalk, pick one civilian occupation off the list it returns, and write the whole experience section in that occupation's vocabulary. Do not start with a thesaurus, and do not start with a title you like the sound of. The crosswalk is the only free public tool that maps a military code to the exact classification BLS wage and outlook data are keyed to, which makes it the one translation an employer's own numbers already agree with.
What the crosswalk will not do is hand you a job title. That gap is where most transition resumes come apart, so the rest of this is about closing it.
What the crosswalk actually returns
Type Navy enlisted code LS - Logistics Specialist - into the crosswalk and you do not get an answer. You get 29 civilian occupations, 12 of them carrying O*NET's Bright Outlook flag, running from Administrative Services Managers (11-3012.00) at the top of the list to Stockers and Order Fillers (53-7065.00) at the bottom. In between: Financial Managers, Purchasing Agents, Management Analysts, Accountants and Auditors, Procurement Clerks, Customer Service Representatives, Postal Service Clerks, Packers and Packagers. All of that from a single two-letter code.
The spread is not the tool hedging. An LS spends a tour doing procurement, inventory accountability, disbursing and postal work, and every one of those is somebody's entire civilian career. What the crosswalk is showing you is the seams along which your job can be cut. Choosing where to cut it is your decision, and it is the first real one of the transition.
| What the crosswalk gives you | What it is actually telling you |
|---|---|
| A list of O*NET-SOC codes | The occupations whose published task lists overlap your service code |
| A Bright Outlook flag | That occupation is projected to grow rapidly, to have large numbers of openings, or to be new and emerging - nationally, not near you |
| An order | O*NET-SOC code order, low to high. Managers print first because 11- sorts before 53-, not because they suit you better |
| No job titles | Titles are written by whoever posted the req; occupations are a classification |
| No read on rank or years | LS and LSS are separate entries with different lists; your seniority is invisible to it |
The list comes out of task overlap between classifications, so it tells you nothing about whether a hiring manager in your city will read your record the same way. What it does hand you is a classification code, and that code is the join key: every wage, education and outlook figure in the rest of this post is filed under one of the numbers on that list.
Why "Operations Coordinator" is not an occupation
Search O*NET for the phrase "operations coordinator" and it returns 909 occupations. Not one of them is called that. The nearest matches are Airfield Operations Specialists (53-2022.00), General and Operations Managers (11-1021.00), and Production, Planning, and Expediting Clerks (43-5061.00) - three jobs that share one word and almost nothing else.
Here is the position, and you are free to disagree with it: writing "Operations Coordinator" at the top of a transition resume is the most expensive line a separating service member puts on the page. It feels like progress because it sounds civilian and it sounds broad. But an applicant tracking system copies that string into a title field, a recruiter searches that field using the words their own open reqs use, and a bucket that wide competes with everybody while matching nobody. A Logistics Specialist who writes "Logistician" instead is claiming an occupation with a median wage of $82,320 a year as of May 2025, projected growth of 18 percent from 2025 to 2035, and roughly 26,600 openings a year - a claim a recruiter can check and a database search can find.
Two honest landing spots for a Logistics Specialist
The same crosswalk sends an LS toward both Logisticians and Production, Planning, and Expediting Clerks. Those are not two rungs of one ladder. They are separate occupations with different wage floors and opposite trajectories, and picking the wrong one costs you either the interview or about $22,700 a year in median pay.
Two civilian occupations the crosswalk returns for one Navy code
Both appear on the LS crosswalk list. Wages, employment and projections from the BLS Occupational Outlook Handbook (logisticians; material recording clerks), May 2025 wages and the 2025-35 projection round; job zones and the clerks' hourly wage from O*NET OnLine.
| Logisticians (13-1081.00) | Production, planning, and expediting clerks (43-5061.00) | |
|---|---|---|
| Median annual wage, May 2025 | $82,320 | $59,650 |
| Median hourly wage, May 2025 | $39.58 | $28.68 |
| Typical entry-level education | Bachelor's degree | High school diploma or equivalent |
| Employment, 2025 | 255,100 | 392,100 |
| Projected change, 2025-35 | +18% | -1% |
| Projected openings | About 26,600 a year | About -5,000 jobs net over the decade |
| O*NET job zone | Four - considerable preparation | One to two - very little to some preparation |
The clerk role is not a junior version of the logistician role. It is scheduling and expediting against a plan somebody else built; the logistician role is building the plan and defending it. If your service work was executing a distribution schedule someone handed you, claim the clerk occupation and be excellent in it - it employs 392,100 people and it hires. If you designed the resupply, argued for the budget and owned the shortfall, claim the logistician occupation. Then accept that BLS lists a bachelor's degree as its typical entry-level education, and plan to answer for that in the cover letter rather than pretend the question will not come.
Where the same occupation pays completely differently
One occupation, five industries, $40,260 between top and bottom.
That top row deserves a second look if you are separating this year. Federal government pays logisticians the most of the five industries BLS lists, and it is also the sector that reads a service record with the least translation required. The tradeoff is a completely different application: a federal resume runs long and asks for detail - hours per week, supervisor names, grade levels - that a private-sector recruiter would never read. Do not send the same document to both.
Write the role line the way the form will store it
An applicant tracking system copies your most recent title and employer into two short fields. Those two fields are what a recruiter scans in a list of two hundred candidates. The role line is not decoration; it is the record.
Before, which is roughly what a DD-214 encourages:
92A Automated Logistical Specialist / NCOIC, SSA
United States Army
Maintained 100% accountability of TA-50 IAW CSDP; executed monthly 10% inventories
After, written against 13-1081.00:
Logistics Supervisor (Automated Logistical Specialist, 92A)
United States Army
Ran inventory accountability for $[X]M of equipment across [N] units, set the
monthly cycle-count schedule, and coordinated resupply with [N] external suppliers.
Four things changed there. The civilian occupation leads and the service code follows in parentheses, so a defense recruiter searching "92A" still finds you and a commercial one is not stopped at the first word. The acronyms are gone, because nobody types CSDP into a search box. The verbs and nouns are the occupation's own - inventory accountability, cycle counts, supplier coordination, resupply - which is the language O*NET uses to describe the work itself. And the numbers are yours to fill in from your own records. Do not round them upward. They are the one part of this that a reference call can check.
The software line does more work than the summary
O*NET publishes the software people in each occupation report using, and the useful finding is how badly the two lists separate. Put them side by side and the office core is identical.
| O*NET software skills | Logisticians (13-1081.00) | Production, planning, and expediting clerks (43-5061.00) |
|---|---|---|
| Software categories listed | 19 | 24 |
| Excel, Word, Outlook, PowerPoint | Yes | Yes |
| SAP and other ERP software | Yes | Yes |
| Microsoft Project | Yes | Yes |
| SQL and Microsoft Access | Yes | Yes |
| Also named | Warehouse management systems, SharePoint, Visio, AutoCAD, Microsoft SQL Server | Oracle Database, materials requirements planning systems, industrial control software, time accounting software |
So the clerk occupation lists more software than the logistician occupation, not less, and every headline product a transition resume reaches for first sits on both. Writing "proficient in Excel, Word and Microsoft Project" claims neither occupation. The entries that do any separating are the specialist ones in the bottom row, and those are the ones nobody bothers to name.
Now look at what you used in service. GCSS-Army, R-Supply, DPAS, a property book you maintained daily for four years - and none of those product names appear on either O*NET list, because they are not sold to commercial employers. A recruiter searching a candidate database does not type them.
So write both. Name the system, then name the category it belongs to in plain words, on the same line: the system you ran, and "enterprise resource planning" or "warehouse management" or "materials requirements planning" beside it. You lose nothing, and you become findable to a search that was never going to include your system's name.
One limit worth stating: this list is what people in the occupation report using, not a list of requirements. An employer can want something on it and still hire someone who has never touched it.
If the posting wants a bachelor's and you have a DD-214
Read the education numbers before you decide the door is shut. Among O*NET respondents in Logisticians (13-1081.00), 75 percent said a bachelor's degree was required - which also means 8 percent said a high school diploma and another 8 percent said a post-secondary certificate. Those are the two doors, and they are narrow but real.
The wider one is next to it. Logistics Analysts (13-1081.02) sits inside the same SOC code, carries the same $82,320 median wage as of May 2025, and its respondents report 64 percent bachelor's, 23 percent associate's degree and 5 percent some college with no degree. Add those two together and more than a quarter of the people in that seat got there without four years. A separating Logistics Specialist with an associate's should be applying to Logistics Analyst postings by name, not to Logistician postings and hoping.
And at the other end of the crosswalk, Production, Planning, and Expediting Clerks report 37 percent high school diploma, 21 percent some college and 19 percent less than a high school diploma. What none of these numbers tell you is what employers demand - they are what people already in the seat say the job required of them, which is a different question, gathered from the winners.
If your code is not in the crosswalk
Search by title instead of code, and set the branch selector before you search. The crosswalk treats near-identical codes as separate entries: LS and LSS (Logistics Specialist, Submarine) return different lists off a one-letter difference, 29 occupations against 25.
If your code genuinely returns nothing usable, do not force the nearest match. Work the other direction - find a civilian occupation whose O*NET task list reads like your actual day, then check that the crosswalk maps it somewhere adjacent to you. The Department of Labor's Veterans' Employment and Training Service runs the Transition Assistance Program and publishes its Employment Fundamentals of Career Transition materials, which is the official route when the self-service tool comes up empty.
Does saying you are a veteran help?
Veteran employment, 2025 annual averages
Veterans were less likely to be unemployed than nonveterans in 2025, and Gulf War-era II veterans came in at 3.6 percent. Two caveats matter more than the headline. BLS notes the 2025 annual averages exclude October because of the federal government shutdown, so they are not cleanly comparable with other years. More to the point, an unemployment rate says nothing about whether those veterans landed work connected to what they did in uniform - a Logistics Specialist stocking shelves is employed, and the statistic cannot see the difference. That is exactly the difference the experience section decides.
Practically, the veteran-status question on an application is a separate demographic field, usually collected for federal contractor reporting rather than screening. Ticking it does not put your service record in front of a hiring manager. Your experience section is still the only thing doing that job.
The one thing to get right
Pick one occupation off the crosswalk and commit the entire resume to it. Not two, not a hybrid, not "Operations Coordinator" hedging between them. Every bullet, the role line, the skills list and the summary written in one occupation's vocabulary, so that the parser filing you and the recruiter searching for you reach the same conclusion about what you are.
Keep the ceiling in view while you do it. Supply Chain Managers (11-3071.04) report a median of $107,230 a year on O*NET's 2025 wage data, and 67 percent of O*NET respondents in that occupation say a bachelor's degree is required - which is a five-year target, not a first application. The first application is Logistician, or clerk, written cleanly and sent often.
After that, the repetition is the tax: the same six fields, the same dates, the same equipment figures, retyped into every portal. HeroApply answers the screening questions from your resume, so the translation you did once carries into every form that follows.
Sources
- BLS Occupational Outlook Handbook - Logisticians (May 2025 wages, 2025–35 projections)
- BLS Occupational Outlook Handbook - Material Recording Clerks (May 2025, 2025–35 projections)
- BLS - Employment Situation of Veterans, 2025 (released April 28, 2026)
- O*NET OnLine - military crosswalk, Navy enlisted code LS (Logistics Specialist)
- O*NET OnLine - Logisticians 13-1081.00 summary
- O*NET OnLine - Logistics Analysts 13-1081.02 summary
- O*NET OnLine - Production, Planning, and Expediting Clerks 43-5061.00 summary
- O*NET OnLine - Supply Chain Managers 11-3071.04 summary
- O*NET OnLine - occupation search for "operations coordinator"
- U.S. Department of Labor, Veterans' Employment and Training Service
Frequently asked questions
How do I find the civilian equivalent of my MOS?
Use the O*NET military crosswalk, which takes a service code or a military job title and returns the civilian occupations whose task lists overlap it. It is free, it covers enlisted and officer codes across the branches, and it returns O*NET-SOC codes that BLS wage and outlook data are keyed to. It will not give you a job title to put on your resume - only an occupation to write against.
What civilian jobs can a Navy Logistics Specialist apply for?
The crosswalk returns 29 civilian occupations for Navy enlisted code LS, 12 of them flagged Bright Outlook. They include Logisticians (13-1081.00), Purchasing Agents (13-1023.00) and Shipping, Receiving, and Inventory Clerks (43-5071.00). The list prints in O*NET-SOC code order - it is not ranked by fit, by pay, or by what you personally are ready for.
Should I put my MOS code on my resume?
Put it once, in the role line, and never in a bullet. A hiring manager outside defense does not know what 92A or LS means, and the recruiter searching a candidate database is typing civilian skill terms, not service codes. The exception is a federal or defense-contractor posting, where the code is a genuine search term.
Do I need a degree to work as a logistician?
BLS lists a bachelor's degree as the typical entry-level education for logisticians, and 75 percent of O*NET respondents in the occupation said a bachelor's was required. That is what incumbents hold, not what every employer demands. Production, planning, and expediting clerks - a common adjacent landing spot - report 37 percent high school diploma and pay a median of $59,650 a year as of May 2025.
Are veterans more likely to be unemployed than nonveterans?
No. BLS put the 2025 unemployment rate for all veterans at 3.5 percent against 4.2 percent for nonveterans, with 294,000 unemployed veterans over the year. The figure says nothing about whether those veterans found work related to their service occupation, which is the harder question.
Let HeroApply do the applying
It finds the jobs that match your resume, answers the screening questions in your voice, and submits the application - desktop, phone or cloud.
The best of the blog, once a week
One email with the week’s guides. No spam, unsubscribe any time.





