Career-change resumes: translating experience across industries.

I've coached hundreds of career switchers: teachers into software, lawyers into product, journalists into UX research, bankers into founder-mode. The ones who succeed share a common pattern: they stop apologizing for their past and start translating it.

The resume is where that translation happens first. Let's get it right.

Start with the story, not the format

Before you write anything, you need a one-sentence story. The template:

I've spent [time] doing [past], which gave me [transferable thing]. I'm moving into [future] because [credible reason], and I've been doing [concrete evidence] to make that move.

Real example from a recent client:

I spent seven years as a trial lawyer, which taught me to lead teams of experts through ambiguous, high-stakes work on tight deadlines. I'm moving into product management because I want to build tools rather than navigate existing systems, and I've been doing a product apprenticeship with a YC-backed startup for the last six months.

If you can say that sentence out loud without flinching, the resume mostly writes itself. If you can't, the resume is not your problem yet — go back and work on the sentence.

The case against "functional" resumes

A lot of career-change advice online recommends a "functional resume" — reorganizing by skill instead of by job, because supposedly this "hides" your old career. Don't do this.

Three reasons:

1. Recruiters hate them. Functional resumes are associated with candidates trying to obscure something. The first question after receiving one is "wait, what have they actually been doing?"
2. ATS parsers struggle with them. Most parsers expect chronological work history with roles tied to companies and dates. Reorganizing breaks the parse.
3. They don't work anyway. The reader will reconstruct the chronology in their head within seconds — and now they're spending those seconds doing your work instead of reading your content.

Keep a chronological structure. The translation happens inside each role's bullets, not in the overall architecture.

The bridge structure that works

The structure I recommend for career changers:

1. Name + one-line role tag for your target role. Not "Former Attorney" — something like "Product Manager — consumer SaaS."
2. A two-line summary that compresses your one-sentence story.
3. Most recent evidence of the new direction. Apprenticeship, certification, freelance, project, bootcamp — whatever is most credible. This often goes above your older job history.
4. Prior experience, chronological. Re-framed bullets, not erased ones.
5. Skills and education, standard.

Notice what's happening: your old career is still on the resume, in chronological order. It's just no longer the first thing the reader sees.

Finding your real transferable skills

"Transferable skills" has become a buzzword that means almost nothing. A useful definition: a transferable skill is a specific capability that translates directly into the target role — not a personality trait, not a generic description.

"Communication skills" is not a transferable skill. "Led client-facing briefings on complex, risk-sensitive material to non-technical stakeholders" is.

"Problem-solving" is not a transferable skill. "Diagnosed root causes of production outages across a 200-service codebase, typically within an hour of escalation" is.

A taxonomy that helps

Walk through these categories and list the things you've concretely done. The ones you can answer with a specific, past-tense sentence are your real transferable skills.

• Synthesizing ambiguous information: (reporters, lawyers, consultants, researchers)
• Leading without authority: (teachers, nurses, clergy, community organizers)
• Selling under friction: (fundraisers, admissions officers, recruiters)
• Designing processes under constraint: (operations, ops-heavy roles, event planners)
• Translating between specialists and non-specialists: (doctors, architects, engineers-turned-PMs)
• Making high-consequence decisions fast: (surgeons, pilots, dispatchers, commanders)
• Running multi-stakeholder projects: (producers, project managers, chiefs of staff)

Rewriting bullets for a new audience

The core skill of the career-change resume is bullet translation. Same fact, different vocabulary.

Example: teacher → software engineer (via bootcamp)

Notice the move: we generalize the action one level ("structured learning sequence" is the architecture; "5th-grade math" is the context). The SWE reader sees "designed a system that scaled to multiple users."

Example: lawyer → product manager

Example: journalist → UX researcher

Building credibility without a matching title

The hardest part of a career-change resume isn't translation — it's the first real evidence that you're serious about the new field. You need something on the resume that isn't a re-framing of old work.

Options, ranked by credibility:

1. Paid work in the new field, even freelance or contract. One month of a real engagement outweighs six months of self-study.
2. Open-source contribution, published work, or shipped project that's visible, dated, and demonstrably yours.
3. A structured program with real stakes — apprenticeship, fellowship, reputable bootcamp with a portfolio output.
4. A certification from a recognized authority, if the field has one (AWS, CPA, PMP, etc.). Useful but weaker than shipped work.
5. Courses and personal projects. Fine to mention, but the reader takes them at a significant discount.

A career-change resume with nothing in the top three categories is an aspirational resume, and those have a much lower hit rate.

Two full examples

Teacher → junior software engineer

Lawyer → product manager

FAQ

Will I be taken at my old seniority level?

Usually not, in the first role in the new field. Most switchers land 1–2 levels below where they left off. That's a real cost, and you should budget for it financially and emotionally before the job search starts.

Should I hide my old career?

No. You can't, and trying signals insecurity. Instead, re-frame it so the reader sees how it made you stronger.

Is a cover letter more important for career changers?

Yes. A cover letter gives you 200 words to tell the one-sentence story and explain the move. Most applications skip cover letters; a career-change applicant should write one.

What about LinkedIn?

Update in lockstep. LinkedIn headline and summary should match your resume's top-of-page claim. Recruiters cross-check within the first 60 seconds.

How long is the transition phase?

Typically 6–18 months from "I want to switch" to "I have an offer in the new field." If you're looking at 3-month timelines, the switch is usually too steep — narrow it (adjacent field first, then farther).

The short version

• Before writing, get your one-sentence story right.
• Keep a chronological structure. Don't "functional-resume" it.
• Re-frame old bullets in the vocabulary of the new field.
• Have at least one piece of real evidence for the new direction on the resume.
• Expect to land 1–2 levels below your old seniority. That's normal.