How to write a career-change résumé (I've done it three times)
I've changed industries three times. Heavy-civil construction first, highways and bridges. Then telecom and commercial contracting. Then corporate facilities and robotics. Every one of those moves started the same way: a résumé that was true, and still didn't work.
The problem with a career-change résumé isn't your experience. It's that the person reading it can't see how your last job connects to the one you want. You know the thread. They don't. Your job is to draw it for them, on the first page, before they decide you're a stretch and move on.
Here's what actually worked for me, three times over.
Your experience isn't the problem. The translation is.
When you apply inside your own field, the reader does the translation for free. A project engineer applying for a project engineering job doesn't have to explain what a project engineer does. The words already match.
When you switch fields, that free translation disappears. I learned this the hard way going from heavy-civil construction into a sales-and-project role. My résumé said "estimating engineer" and "project engineer." The people hiring for the new role read those titles and saw someone from a different world, because I was describing my old job in my old job's language.
The fix isn't to hide where you came from. It's to describe what you did in the language of where you're going. Same facts. Different words.
Lead with the target, not your history
A career-change résumé that starts with a straight chronology of your past is asking the reader to figure out the point. Most won't. They'll skim, see a title that doesn't match, and stop.
So put the connection up top. A short summary line that names the role you're after and the two or three things from your background that genuinely support it. Not a personality paragraph. A bridge. "Estimating and project background moving into sales engineering, with a track record of closing and delivering work on tight timelines" tells the reader how to read everything below it.
Then tailor the rest to the specific job. This is the part most people skip, and it's the highest-return thing you can do. Read the job description closely. Note the words it uses for the skills you actually have, and use those words. Most postings pass through an applicant tracking system (ATS) before a human reads them, and that system matches on the language in the posting. A résumé that mirrors the specific job clears that filter far more often than one generic résumé you send to fifty companies.
Tailoring per job is slow by hand, which is exactly why I built it into ResumAI. You keep one master résumé, and the tool tailors a version to each job description and scores it against the posting so you can see the gaps before you apply, not after you're rejected. But you can do the same thing manually. The method matters more than the tool.
Transferable skills, named in the new field's words
"Transferable skills" is advice everyone gives and almost nobody makes concrete. The trick isn't listing skills. It's renaming them.
When I moved out of construction, "reading civil plans and coordinating subcontractors" became "managing complex projects across multiple stakeholders on fixed deadlines." Same work. The second version is legible to someone who has never poured a foundation. Go through your real accomplishments and ask, for each one: what is the general skill underneath this, and what does the new industry call it? Write that.
A word of honesty here, because the products I build refuse to lie and the advice should too: renaming is not inventing. You're translating real work into words a new reader understands, not claiming experience you don't have. If you can't point to the thing you actually did, don't put it on the page. A career-change résumé that overreaches gets found out in the first interview, and you've burned a shot you worked hard to get.
Numbers travel across industries
Titles don't transfer well. Numbers do. A hiring manager in a field you've never worked in still understands "closed 150% more revenue in 30 days" or "promoted within 90 days" or "delivered on a fixed deadline with zero rework." A number is proof that doesn't need a translator.
When I switched into commercial contracting, my strongest lines weren't the job titles. They were the results: revenue up 150% in the first 30 days, 250% by 90. When I got promoted from estimating to project engineer in my first 90 days on a concrete crew, that speed said more than the title did. I didn't have the new field's résumé yet. I had receipts, and receipts carry.
If your past work has numbers in it, lead your bullet points with them. If it doesn't, go find them. How much, how many, how fast, how much saved. A vague bullet is a wasted line on a résumé that's already fighting to be understood.
What I'd tell myself before the first switch
- Write the summary line last, once you know which two or three facts actually bridge to the target role. Then put it first.
- Tailor to each posting. Use the job description's own words for the skills you really have. One master résumé, a fresh version per job.
- Rename your accomplishments into the new field's language. Translate; don't invent.
- Put numbers first in every bullet you can. They cross industries when titles don't.
- Don't hide the pivot. A clear, confident bridge beats a résumé pretending you were always headed here.
Changing careers is not a disqualification. It's a thing you can get good at. I went from concrete to robotics one deliberate step at a time, and the résumé was the tool that made each jump legible to the next employer. Yours can do the same work. Draw the thread, prove it with numbers, and let the reader see what you already know.
Building a résumé for a field you haven't worked in yet? ResumAI tailors your résumé to each job and scores it against the posting, so you can see the gaps before you apply. Start free, no card and no API key required.