Job Search

How to write a resume when you're changing careers

Name the problems the new role exists to solve, then show the work from your old field as evidence you can solve them. Don't leave the translating to the reader.

13 min read

Almost every career change resume gets written the same way: listing what you did in your old field, as accurately as you can, and hoping the person reading it works out what that means for the job you want now. They usually won't, because they have a stack of resumes from people who already do the job, and about 30 seconds for yours.

This article covers how to pick the target role first, then how to find evidence that genuinely transfers instead of listing skills you hope count. It also covers rewriting your bullets in the new field's vocabulary, how to answer the question about why you're switching, and when a bridge role gets you there faster. Do the picking before the writing, because you can't translate your experience until you know what you're translating it into.

The advice comes from Ethan Evans, a retired Amazon VP who spent 15 years there and reviewed real career-changer resumes live on his Level Up show, including people leaving the military, a finance manager turned entrepreneur, and an esports team owner applying for HR jobs; Matt McCloskey, who went from practicing law to business development at Xbox to running engineering and product at Twitch; Phyl Terry, author of Never Search Alone; and Lauren Ipsen, who recruits senior executives at Daversa Partners. Every quote plays the exact moment it was said.

Pick the target role before you touch the resume

A resume that doesn't say what job you want is fine when your last title matches the job you're applying for. The reader fills in the gap. Change careers and that gap is the whole problem, because nothing on the page points anywhere. Evans reviewed a resume from a human resources student whose entire experience section was esports, and docked it before he read a single bullet.

The missing target. The player below is queued to 1:32, the exact moment Ethan Evans says it. Watch on YouTube.

"It loses a full letter grade right off the top because you have no idea what the person wants to do. And it isn't obvious... If his major was human resources and all the experience looked like human resource management, you might assume that he wants to do that. But here you have someone who's got a bachelor of science in human resource management, and then all esports experience. You have no idea what that might mean."
Ethan Evans, retired Amazon VP · Level Up

He hit the same thing reviewing a finance manager who'd started a company: "What job are you after? Maybe you customize that for specific jobs, but be clear about what you want, because you're all over the place here." The fix is one line at the top of the page naming the role you're applying for. It costs you nothing and it tells the reader which lens to read the rest through.

So write that line before anything else, and be specific. "Product marketing manager at a B2B software company" gives you something to aim at. "Looking to leverage my skills in a new challenge" is the sentence career changers reach for when they haven't decided yet, and a reader can tell.

Check that the market will give you that role

Deciding on a target is half of it. The other half is whether anyone is hiring for it from someone with your background right now. Phyl Terry calls the answer your candidate market fit, and he pushes people to write it down as narrowly as they'd define a product's market.

Candidate market fit. The player below is queued to 31:30, the exact moment Phyl Terry explains it. Watch on YouTube.

"We want this product to be for everyone, but we've learned with product market fit that doesn't work. We need a narrow, clear focus. Same thing with candidate market fit. So I say to people, I'm looking for a director of product role in a healthcare Series B startup in San Francisco. And people are like, oh, if it's so narrow I'm going to lose out. And here's the thing: when you're looking for a job you need a spear and not a net."
Phyl Terry, author of Never Search Alone · Lenny's Podcast

Terry's method for getting there is a listening tour: ten or fifteen conversations with people who do the job or hire for it, before you commit to a target. For a career changer those conversations do double duty. You learn whether the switch is realistic from where you're standing, and you learn the words these people use for the work, which you're going to need in a minute. The positioning playbook goes deeper on choosing a target you can actually win.

Find the evidence that answers the new role's problems

Here's the part almost everyone skips. Before you edit a bullet, write down the five to eight problems the target role exists to solve, in the hiring manager's language. Pull them from three or four job postings and from the conversations you just had. Not "strong communication skills." Things like "keep a launch on schedule when three teams disagree," "cut support ticket volume," "get a forecast the CFO will sign off on."

Then go through them one at a time and ask whether you can prove you've done it. McCloskey builds this into a simple table, and the question he asks is the one your reader is silently asking.

Would you hire you. The player below is queued to 19:15, the exact moment Matt McCloskey describes the exercise. Watch on YouTube.

"You basically became an expert, and you know, here are the 10 things that you need to get this job. And then you ask yourself, would you hire you? And just go through each requirement and give yourself a yes or no or maybe, and then list the evidence. So in this little chart here of requirement, yes or no, and evidence. So you have to be able to show the evidence at the level that you have."
Matt McCloskey, former VP of engineering and product at Twitch · Level Up

Three columns: the requirement, whether you've got it, and the specific piece of work that proves it. The evidence column is your new resume. Every yes becomes a bullet, and it goes near the top of whatever role it happened in, even if that role has an unrelated title.

The evidence is usually already on your resume, sitting in the wrong place. Reviewing a resume from a 20-year Army veteran moving into industry, Evans found the strongest fact on the page "buried in here near the bottom": the applicant had managed a $450 million budget. Everything above it was training jargon.

What he said next is what a career change resume has to do. "That's amazing. How do you convey that? How do you get that up at the top of your resume? Because in the business world, that's what I want. I'm looking for that business impact and business ability." You already know which of your facts would impress someone in the new field. The reader doesn't, and won't go hunting for them.

Be honest about which skills actually transfer

"Transferable skills" is where career change advice usually goes soft. A list of adjectives at the top of your resume, leadership and problem solving and adaptability, proves nothing, and every other applicant claims the same things. Evans is direct about what it takes to get someone to believe in a jump.

The big jump. The player below is queued to 1:10:44, the exact moment Ethan Evans says it. Watch on YouTube.

"You can try to make the big jump by getting people to believe in your transferable skills. That usually requires a relationship, or someone like Matt has suggested who was in your field and says, oh, I know these skills translate. It doesn't always work, but there's no problem mixing in a big gamble or a big swing with a more reliable approach."
Ethan Evans, retired Amazon VP · Level Up

Two useful things follow from that. The big jump needs a person vouching for you, so build that relationship while you're rewriting the document. The foot in the door playbook covers how. And you should run some safer applications alongside the ambitious ones, because a swing you take on top of a reliable approach costs you very little.

On the page itself, hold every claim to one test: can you point at a specific thing you did that proves it? Here's the difference in practice.

Wishful

  • "Strong analytical skills applicable to data analysis roles."
  • "Leadership experience that translates to managing engineering teams."
  • "Passionate about product with a customer-first mindset."

Evidence

  • "Built the weekly staffing model for 6 clinics, cutting overtime spend 18% in two quarters."
  • "Led 22 people across three shifts, including hiring, scheduling, and performance reviews."
  • "Interviewed 40 customers after a pricing change and rewrote the onboarding flow based on what they said."

The second column is the same person as the first. The difference is that a stranger can check it and picture you doing the same thing at their company.

Answer why you're changing, without the wobble

Work Coach records the answer and marks the sentence where your voice goes defensive. It keeps asking, until you can get it short enough that nobody feels the need to dig.

Start Free Trial

2-week trial, no credit card needed. Your data is never shared with your employer.

Rewrite the bullets in the new field's words

Every field has words that mean something inside it and nothing outside it. Yours does too, and you've stopped noticing which ones they are. Reviewing the resume of a soldier moving into private sector work, Evans stopped on the applicant's headline claim, master resilience trainer level one and level two, and admitted he had no idea what it meant.

Jargon that doesn't travel. The player below is queued to 1:08, the exact moment Ethan Evans says it. Watch on YouTube.

"So he's ready to leave the military and go into private sector. Well, private sector unfortunately doesn't know what you're talking about... Sometimes he does the right thing, where basic life support, we're talking about acronyms, you can do this: basic life support, BLS, and then you can use it all over the place. Oh, BLS, BLS, but I know what it is because you told me. That's okay. But there's just a ton of stuff in here that I don't know what it is, and that's a problem."
Ethan Evans, retired Amazon VP · Level Up

Jargon isn't only acronyms. It's also register. In the esports review, Evans flagged "the Super Smash Brothers scene" as a word choice that gives you away: "scene is what non-professionals say. It's not going to get you a job somewhere in human resource management. It might get you a job in something else." He wasn't objecting to the experience, only to a word that tells a reader you're outside the profession you're applying to.

Run your resume through three passes:

Pass one: the stranger test

  • Give it to someone with no connection to your old field and ask them to circle anything they can't explain back to you.
  • Every circled acronym gets spelled out on first use, or gets cut.
  • Every internal title, rank, or program name gets a plain description next to it: "master resilience trainer (ran the Army's stress and performance training program for a 3,000-person unit)."

Pass two: their words

  • Take the vocabulary from the job postings and the conversations you had, and use those words wherever they honestly describe your work.
  • Swap old-field register for new-field register: patients become customers, missions become projects, the scene becomes the industry.
  • Keep the underlying facts identical. You're changing the language, never the truth.

Pass three: scale

  • The reader can't tell whether your old employer was big or small, so say it: headcount, budget, number of sites, tickets per week.
  • Add a number to every bullet you can, even an honest approximation.

Then fix the thing Evans says almost every resume gets wrong, which matters double when you're switching fields. Describing what you did tells a stranger very little, because the activity belonged to a job they don't understand. A result they recognize, money saved or customers kept or time cut, carries over without any explanation.

Why it mattered. The player below is queued to 2:50, the exact moment Ethan Evans says it. Watch on YouTube.

"If your resume mostly reads about what you did and not why it mattered, you're only halfway there. You don't just want to be known for the work you did. You're not getting hired to do work... You're being hired to generate money for your company. You're being hired therefore to generate a result."
Ethan Evans, retired Amazon VP · Level Up

In that same review he kept hitting bullets full of impressive scale with no outcome attached, monitoring 190 applications for 2.1 million users, and said the same thing each time: "Excellent data giving me the size. What was the impact?" A career changer can't afford that gap, because the scale of your old employer means nothing to a reader who has never worked in that field. The tailoring playbook covers the line-by-line mechanics once your bullets carry results.

Decide what to cut and how much of the old career to keep

Career changers cut too little. You're proud of work that took years, and the instinct is to keep all of it and let the reader sort it out. But every line that doesn't answer one of the new role's problems is competing with the lines that do.

Cut

  • Certifications, licenses, and training that only matter in the old field, unless the new role names them.
  • Old-field tools nobody in the new field has heard of.
  • Adjective lists at the top claiming transferable skills. Replace them with the target role line and two or three bullets of evidence.
  • Detail on early roles. One line each, and only if they hold evidence you need.

Keep

  • Any work that maps to one of the new role's problems, wherever it happened.
  • Scale and money: budgets owned, people led, customers served, revenue affected.
  • Progression. Getting promoted three times says something in any field.
  • Enough of the old career to explain your timeline. If your dates have holes in them, people assume the worst.

Keep the whole timeline visible, compressed. Roll up a decade of old-field roles into a short section with titles and dates and one line of detail on the ones that matter. Evans praised exactly this move reviewing a soldier's resume, where a block labeled early positions covered six years in four words: "You don't want to have your resume drag on and on." He read the roll-up, said "got it," and moved on, which is exactly what you want him to do with your old field.

One warning on the other side. When you compress and reframe, keep it honest, because a reader who suspects you've inflated your role will stop giving you the benefit of the doubt on everything else. Reviewing the finance manager who described himself as an entrepreneur while the details stayed vague, Evans watched his chat start guessing what the guy had really done: "The last thing you want in a reviewer is suspicion." Career change resumes are already asking for more trust than usual. Don't waste that on a title you can't defend.

Handle the question about why you're switching

Every career change resume raises the same question, and you're better off answering it than pretending it isn't there. Two lines under the target role at the top of the page will do it. Say what you're moving toward, and give a concrete reason grounded in work you've already done.

A two-line version that works

  • "Operations manager moving into product management. Spent the last three years as the internal customer for our order management tool, wrote the specs for two rebuilds of it, and want to do that as the job rather than on the side."
  • "Registered nurse moving into clinical software implementation. Rolled out a new EHR across four units, trained 120 staff on it, and spent most of that project translating between clinicians and the vendor's engineers."

What makes them work

  • They point forward, at the new work, instead of explaining what went wrong in the old job.
  • They name a specific project as the reason, so the switch sounds like a next step instead of a leap.
  • They're short, about two lines, and the bullets underneath make the rest of the case.

Say nothing about a bad manager, burnout, or an industry in decline. Those may be true, and they cost you the benefit of the doubt on the page. Save the fuller version for the interview, where the story gets three or four sentences instead of two lines, and where the person can ask follow-ups.

That spoken version needs rehearsing more than most answers do, because you'll give it in every conversation you have for months. Ipsen has watched senior candidates work it out live in interviews they cared about.

Practice before it counts. The player below is queued to 54:19, the exact moment Lauren Ipsen says it. Watch on YouTube.

"Being able to tell your story, like practice telling your story. So often people don't do that, especially when they're not looking for jobs. And then it's not until their tenth interview that they know how to tell their story and what they did and what they impacted and why they were someone to be missed when they moved on."
Lauren Ipsen, executive recruiter at Daversa Partners · Lenny's Podcast

Tell it out loud five or six times before it counts, and listen for the moment your voice goes defensive. That's usually the sentence where you start justifying the old career instead of describing the new one. Cut that sentence. The tell me about yourself playbook covers how the switch fits into your 90-second opening.

When a bridge role beats a direct jump

Sometimes the honest answer to "would you hire you" is no, and no amount of rewriting fixes it. If the target role needs two or three things you've never done, you're asking a stranger to take a risk that a rewrite can't talk them out of. The move then is to find the job that's halfway, get the missing evidence there, and jump from a shorter distance.

McCloskey has done this across five or six disciplines and three industries, starting as a practicing lawyer. He left a great job on Xbox's third-party team, a $900 million business, for a $20 million business inside Xbox Live, purely because the smaller one let him own a profit and loss statement for the first time. Checking that box is what made the next moves possible.

The step in between. The player below is queued to 49:12, the exact moment Matt McCloskey explains how to choose one. Watch on YouTube.

"So what we're doing here is we're coming up with lots of different adjacent paths, but which one should you choose? You should choose the one where you can get there the fastest. Because this isn't the destination. This is the stepping stone to your final destination. Because you have to transition from where you are... and there may be a step in between."
Matt McCloskey, former VP of engineering and product at Twitch · Level Up

A bridge role changes one variable instead of two. Keep your function and change the industry, or keep the industry and change the function. A nurse who wants to be a product manager at a health software company can go be an implementation specialist there first, where the clinical background is the qualification, and apply internally in 18 months as a colleague rather than a stranger. Evans makes the same point about how much of the job you need on day one: "You can do 80% of the job and you ask for the last 20%."

Two other paths shorten the distance. Do the new work inside your current job, since a side project with a real result is evidence you can put on the page. And apply to the companies where your old field is the customer, because the medical device company hiring a product manager is one of the few places your nursing years count as domain expertise rather than a detour.

Frequently asked questions

Should I use a functional resume that groups skills instead of jobs?

No. Recruiters see that format and assume you're hiding something, and it removes the dates and titles they use to place you. Keep the reverse chronological structure and do the work inside it: target role at the top, evidence bullets reordered so the transferable work leads, old-field detail compressed.

How do I handle having zero experience in the new field?

You almost never have zero. You have work that solved the same kind of problem in a different setting, and your job is to describe it in the new field's terms. If you genuinely can't find any, that's a signal to go get some before you apply: a side project, a volunteer role, a piece of the new work inside your current job, or a bridge role.

Do I need a cover letter for a career change?

Yes, more than most applicants do. It's the one place you get a paragraph to connect the old work to the new role without cluttering the resume. Three short paragraphs: the role you want and why now, one specific project from your old field that proves you can do the central thing this job requires, and what drew you to this company. Keep it under 200 words.

Will I have to take a pay cut?

Often yes, at least at first, and less than people fear if you keep your industry or your function rather than changing both. Bridge roles usually pay closer to your current level than an entry-level job in the new field would, which is another argument for them.

Should I explain the switch on LinkedIn too?

Yes, and it's easier there. Put the target role in your headline and the two-line explanation at the top of your About section. Recruiters search by title, so a headline reading "operations manager moving into product management" gets you into searches your last job title never would.

How long does a career change take?

Longer than a same-field search, and the number of applications per response goes up. Terry's advice about getting a group of people to search alongside you matters more here, because the timeline is long enough that morale becomes the thing that decides whether you finish.

The method on one page

Before you write

  • Name one target role, specifically enough to put it at the top of the page.
  • Have ten to fifteen conversations with people who do it or hire for it, and check the switch is realistic from where you are.
  • Write the five to eight problems that role exists to solve, in their language.

Find the evidence

  • Three columns: requirement, yes or no, and the specific work that proves it.
  • Every yes becomes a bullet, placed near the top of whatever role it happened in.
  • Drop any claim you can't attach a real project to.

Rewrite

  • Spell out or cut every acronym, title, and program name that doesn't travel.
  • Use the new field's vocabulary for the same facts.
  • Give every bullet a result and a number, and state the scale of your old world.

Cut and explain

  • Roll up old-field roles into one line each, keeping the timeline visible.
  • Two lines under the target role saying what you're moving toward and the project that started it.
  • Nothing about a bad manager, burnout, or a dying industry.

Before you send

  • Someone outside your field reads it and can say what job you want and why you'd be good at it.
  • You've said the reason for the switch out loud five or six times without sounding defensive.
  • You know which of your applications are the safe ones and which are the swing, and you're sending both.