Switching industries: what to put in the experience section
Keep the jobs and titles you actually held, and rewrite what sits underneath. Here is what a form stores, and what changes between two industries.
Nathan Cole · · 9 min read
Short answer: keep every job you actually held, keep the titles exactly as your employer wrote them, and rewrite the lines underneath in the vocabulary of the industry you are moving to. The experience section is not where you explain the pivot. It is where you show the work was the same work under a different sign.
What follows is what an application form stores from those fields, what two occupations look like when their O*NET pages sit side by side, and the handful of lines that actually change when a Restaurant Manager applies for an Operations Manager job.
What the form does with your experience section
The experience section is not read as writing. It is read as four data types, and each one behaves differently.
Greenhouse's Talent Matching - the feature that lets a recruiter search everyone who has ever applied - "parses the resumes with ML models and extracts skills, job titles, years of experience, start/end dates of employment, and company names from employment history as structured data." It also processes "a derived industry classification associated with candidate's past employers." Read that last clause twice if you are switching industries, because it is the whole problem in nine words.
| What you enter | What the system holds it as |
|---|---|
| Employer name | A company name, plus a derived industry for that employer |
| Job title | A job title, indexed for recruiter search |
| Start and end dates | Employment dates, from which years of experience are computed |
| Bullet points | Text in the attached file, plus any skills the extractor recognizes |
That table is the mechanism, and it explains something that otherwise feels arbitrary. A Restaurant Manager applying to an operations role has an employer whose derived industry is food service, and no wording anywhere on the page changes that. The two fields you genuinely control are the title, which should stay true, and the skills, which are pulled from what you write. So the work goes into the skills, and none of it goes into disguising where you worked.
Workday puts the other half of this in the employer's hands. Its career-site documentation says an administrator can "define the sections that candidates must complete when they apply for a job," which is why the same resume produces a three-field form at one company and eleven separate work-history entries at the next.
Do a restaurant manager and an operations manager share skills?
They share all of them, and that is not a figure of speech.
Put the O*NET summaries for Food Service Managers (11-9051.00) and General and Operations Managers (11-1021.00) next to each other and the skills lists are the same twenty-two entries. The same eight in the first group - active listening, monitoring, speaking, reading comprehension, critical thinking, active learning, learning strategies, writing. The same fourteen in the second, including coordination, management of personnel resources, management of financial resources, negotiation, systems analysis and systems evaluation. Not similar lists. The same list, in a different order.
Two occupations, side by side on O*NET
From the O*NET OnLine summaries for 11-9051.00 (Food Service Managers) and 11-1021.00 (General and Operations Managers).
| Restaurant / food service manager | General and operations manager | |
|---|---|---|
| Skills listed on the summary | 22 skills | The same 22 skills |
| Knowledge areas listed | 11 - including Food Production and Education and Training | 9 - every one of them also on the food service page |
| Technology named | Point of sale software, ChefTec, MenuPro | SAP, Salesforce, Tableau, Oracle Primavera |
| Job Zone | 1-2 - very little to some preparation | 4 - considerable preparation |
| SVP range | Below 6.0 | 7.0 to under 8.0 |
| Most-cited education in O*NET's survey | 30% high school diploma or equivalent | 29% high school diploma, 27% bachelor's degree |
This is why "highlight your transferable skills" changes nothing. Everybody transfers. If the skills lists decided the outcome, every food service manager in the country would already be an operations manager, and the two occupations would not sit in different job zones. The distance between them is in the bottom half of that table, not the top row.
One caution on the education row. Those percentages are what O*NET's survey respondents said the job requires - they are not a record of what the people hired last year actually held, and O*NET does not publish that. The 29% is a useful corrective to the idea that the door is bolted shut without a degree. It is not permission to leave the education field blank.
What actually differs is the toolset
Compare the technology lines and the gap stops being abstract. O*NET names point of sale software, ChefTec and MenuPro for food service managers. For general and operations managers it names SAP, Oracle PeopleSoft, Salesforce, Tableau, QlikView, Oracle Primavera and Apache Hadoop.
The knowledge sections do not move with them, and this is the part worth arguing about. O*NET gives food service managers eleven knowledge areas and general and operations managers nine - and all nine of them already sit on the food service page, including Production and Processing, the one that sounds least like a restaurant. The two the restaurant job has and the operations job does not are Food Production and Education and Training. Read in that direction, the food service manager knows everything the operations job is documented as needing, plus two things it does not ask for. What is missing is not knowledge. It is software.
So the honest gap for a Restaurant Manager is not judgment, not scheduling, and not handling a supplier who missed a delivery on a Friday. It is that the target job runs on an enterprise resource planning system and a business intelligence tool, while yours ran on a point of sale terminal and a spreadsheet.
That points at three things worth putting in the experience section, in this order:
- The systems you did use, by name. QuickBooks, Excel, whichever POS. O*NET lists spreadsheet software and accounting software on both pages, so those are shared vocabulary rather than filler.
- The financial scope you held. Food cost percentage, weekly purchasing spend, payroll against a headcount. Management of financial resources appears on both skill lists; give it a number.
- Anything that reads as a repeating process rather than a shift. Inventory counts, supplier terms, a rota built against forecast covers.
Restaurant Manager to Operations Manager, one bullet at a time
Here is the same job, described twice. Before:
Restaurant Manager, Harborline Grill · Mar 2021 – Present Ran a busy 140-cover restaurant. Hired and trained staff. Ordered stock and kept food costs down. Handled customer complaints and health inspections.
After:
Restaurant Manager, Harborline Grill · Mar 2021 – Present Operations lead for a $2.4M single-site P&L; owned the weekly labor and COGS budget. Managed 34 staff across two shifts, including hiring, onboarding and a training program. Ran purchasing for 40+ SKUs against forecast demand; negotiated terms with 9 suppliers. Held food cost at 28.5% through two years of supplier price increases. Systems: Toast POS, QuickBooks, Excel forecasting models, ADP scheduling.
The title did not change. The employer did not change. The dates did not change. What changed is that every line now names a resource being managed, a number attached to it, or a tool - which is what O*NET's shared skills list is made of, and what a skills extractor can pick up.
Notice what got deleted. "Handled customer complaints" is service orientation, which sits on both occupations' lists and therefore separates you from nobody. "Busy" is not a measurement. If a line would be equally true of a supervisor at any restaurant in the country, it is occupying a row that could have held a number.
Keep the title you actually held
Plenty of career-change advice tells you to neutralise your titles: write "Operations Manager (Restaurant)" or "Site Operations Lead" so the words line up with the posting. Do not do it.
The extracted title is matched against a recruiter's search and stored beside an employer whose derived industry says food service. A title you never held, sitting next to a company that contradicts it, is the one line on your application that can be checked in about thirty seconds, and it looks worse than the pivot it was meant to smooth over. Employment verification runs against the title your employer has on file, not the one that reads better.
There is a legitimate version of the same move. Write the title exactly as it was, then put the scope in the first line underneath. "Restaurant Manager" followed by "operations lead for a $2.4M single-site P&L" says everything "Site Operations Lead" was reaching for, and it is true.
What the money says about the move
Food service managers, May 2025
The Bureau of Labor Statistics puts the median for food service managers at $69,390 a year, or $33.36 an hour, as of May 2025. There were 344,300 of those jobs in 2025, and BLS projects employment to grow 6 percent between 2025 and 2035. General and operations managers had a median of $105,770 in May 2025, with the lowest tenth under $50,090 and the highest tenth above $253,390.
Hold those two spreads against each other, because the overlap is the interesting part. The top decile of restaurant management, $107,640, sits a couple of thousand dollars above the median for the job people are moving into. A Restaurant Manager already near the top of that range is not switching industries for a raise in year one. A manager sitting at the median is buying a different ceiling: $253,390 at the top of the new occupation against $107,640 at the top of the old one, roughly two and a third times higher.
What this data does not tell you is the thing you most want to know: how often the move works. BLS publishes wages and projections for each occupation separately, O*NET publishes skills for each occupation separately, and neither one tracks people crossing between them. O*NET does not even list general and operations managers among the related occupations for food service managers - its related list keeps you inside food service, next to chefs and first-line supervisors. Read that as a description of how the taxonomy is wired, not as a verdict on the move.
If the new industry runs on a system you have never touched
Say so in the skills line, at the level you actually have. There is a real difference between "SAP" and "SAP (coursework)", and only one of them survives a first interview.
The Restaurant Manager example above lists Toast, QuickBooks, Excel and ADP. That is four named systems, and ADP is the sort of thing an operations job description asks for without anyone expecting a restaurant to have used it. Name the small ones. A skills extractor takes the string it finds; it has no opinion about which employer is impressive.
If the form asks how many years you have in the industry
Answer for the function, not the sector, and say which one you answered. A line you can paste into the free-text box next to a numeric field:
Nine years in operations management, four of them running a single-site P&L. Those years are in hospitality rather than manufacturing.
A blank is worse than a low number here, because an empty field routes to the same place a zero does and gives the recruiter nothing to push back on. If the field is a hard numeric knockout and the honest number falls below the threshold, enter the honest number and expect the rejection. A knockout question you lied past becomes a withdrawn offer at reference stage.
If the job is smaller than the one you are leaving
Enter the real scope anyway, and do not shrink your history to look like a tidier fit. A hiring manager who worries you are overqualified will ask about it; one who never sees the number never gets as far as the question.
The one thing to get right
Give every job in your experience section a resource, a number and a tool, and change nothing else. Not the titles, not the employers, not the dates - those three are the fields a system stores as data, and they are the three where invention costs you the most. Everything you want a reader to understand about the pivot lives in the lines underneath, and those lines are entirely yours to rewrite.
Do that once, properly, on the resume file itself. Then, if the retyping across a dozen work-history forms is what is actually stopping you from applying, the platform fills those fields from your resume, so the version you rewrote is the version every employer receives.
Sources
- O*NET OnLine - Food Service Managers (11-9051.00) summary
- O*NET OnLine - General and Operations Managers (11-1021.00) summary
- BLS Occupational Outlook Handbook - Food Service Managers (May 2025 estimates)
- BLS Occupational Outlook Handbook - Top Executives, including general and operations managers
- Greenhouse Support - Talent Matching Data Processing FAQ
- Workday - Setup Considerations: External Career Sites
Frequently asked questions
Should I change my job title to match the industry I am moving into?
No. Greenhouse extracts job titles and company names as structured data and also derives an industry classification from your past employers, so a retitled role sits next to an employer whose industry contradicts it. Keep "Restaurant Manager" and put the translation in the line underneath, where a person reads it and no system is trying to match it against anything.
Do I have to list every job when I am switching industries?
List every job you want counted, because years of experience are computed from the employment dates you enter, not from a summary you write. Leaving a role out shortens your history in the recruiter's search filter. If a job is genuinely irrelevant, keep the dates and cut the bullets to one line rather than deleting the entry.
What if I have no experience at all in the new industry?
That is the normal case for an industry switch, and it is not what the experience section is for. O*NET lists the same twenty-two skills for food service managers and for general and operations managers, and every knowledge area on the operations page is also on the food service one; what differs is the software. Spend the section proving the skills, and name the tools you have actually used, including the small ones.
Where do I explain why I am changing industries?
Not in the experience section. The screening questions are where a form asks you directly, and a summary line at the top of the resume is where a human looks for it. The experience entries themselves should read as though the move has already happened.
Does a career change make an applicant tracking system reject me?
No system rejects you for a career change on its own, because nothing in the parse is scored. What happens is quieter: your extracted titles and derived employer industries do not match what the recruiter typed into the search box, so you never appear in the list. That is a visibility problem, not a rejection.
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.
Nathan Cole · Applications Editor
Nathan explains what the application form is actually checking - screening questions, applicant tracking systems, and how many applications it really takes.
The best of the blog, once a week
One email with the week’s guides. No spam, unsubscribe any time.
