The career-change resume is one of the hardest writing problems in the job search. Your work is real. The skills transfer. But a recruiter scanning your resume in seven seconds doesn't see "transferable senior operator" — they see "doesn't have the experience" and move on. The translation problem is the whole problem.

This post is about how to do that translation without exaggerating, without inventing new credentials, and without burying the experience you actually do have.

Not all career changes are the same

The first thing to do is figure out which kind of career change you're actually making. The advice differs by type.

A lateral function shift — same industry, different function — is the easiest move and the most common. Engineer to PM in the same company is the canonical case. Industry context transfers; function vocabulary doesn't. Lead with the domain familiarity, then build a bridge section that translates your work into the new function's terms (projects shipped, stakeholders managed, decisions owned).

An industry pivot — same function, different industry — is moderate difficulty. Function transfers; industry knowledge doesn't. The translation work is mostly vocabulary substitution: replace industry-specific terms with the target industry's vocabulary where the underlying work is the same. A "claims processing workflow" becomes a "high-volume operational pipeline" when moving from insurance to tech.

A full pivot — both industry and function — is the hardest move. The resume by itself struggles to clear the bar; referrals will do more of the work. Pick one anchor (function or industry) to translate toward, and accept that.

A two-step pivot — a bridge role first — is often the right move when the gap is too wide. A year in a bridge role beats two years of failing cold applications.

What the recruiter is actually weighing

A useful mental model: when the function or industry is new, the recruiter compensates by weighing other signals more heavily. They're not just scoring direct keyword match — they're looking for compensating evidence.

The biggest compensating factor is demonstrated work in the new domain: a portfolio piece, a side project, a contracting gig, a volunteer role, a paid course completion with a project artifact. Even a small piece of work in the target field outweighs years of indirectly relevant experience. This is the single most underused move in career-change resumes.

The second is translated achievements in the new field's vocabulary. The same accomplishment, written in target-field language, scores differently. This is the work of the resume itself.

The third is credibility-by-association: brand-name companies, well-known schools, recognizable certifications. You can't manufacture these on a deadline, but if you have them, surface them.

The fourth — and the smallest of the four — is direct keyword/skill match with the posting. Most career changers over-index on this and ignore the first three.

How to translate a bullet without overstating

The translation work is concrete. Take a bullet from your origin field, identify the underlying work (what you actually did, in plain language), and rewrite it in the target field's vocabulary.

The rules:

• Translate the work, not the credentials. You can rewrite a teaching role as "curriculum strategy" because the underlying work is similar. You can't rewrite it as "product management" because the underlying work is not.
• Use the target field's verbs. "Managed", "led", "owned" are universal. "Onboarded", "shipped", "tested", "iterated" carry domain weight.
• Keep the numbers. Quantification from the origin field travels with you. Even when the dollar amounts are small for the target field, the fact of having handled them shows you can.
• Don't claim credentials you don't have. A teaching role isn't a PM role. A research role isn't an engineering role. The translation makes the relevance visible; it doesn't manufacture new experience.

For the underlying writing technique, see achievements-vs-responsibilities. For where to place the translated content on the page, see chronological-vs-functional-resume — most career changers benefit from a hybrid format.

The bridge section

A specific suggestion for the full-pivot case: include a small section above your work history titled "Selected projects" or "Recent work in [target field]". Two to four bullets, drawn from courses, side projects, contracting, volunteering, or open-source work. Each bullet describes a discrete piece of work in the target field with a concrete outcome.

This section does more work than the entire prior-experience block for a recruiter who otherwise wouldn't see relevant experience on your resume. It's also the section a hiring manager will be most curious about in the interview, which makes it the most leveraged 4 lines on the page.

What this isn't

A few clarifications:

• It's not about hiding your background. A career-change resume should make the change visible. Recruiters can spot evasion; an honest pivot reads better than a disguised one.
• It's not a substitute for network. Career-change resumes convert at a lower rate via cold application than same-field resumes. Referrals close more of the gap than any single resume edit will.
• It's not a license to claim experience you don't have. Translating work is different from inventing work. Every translated bullet should survive a five-minute interview question about it.

The short version: translate the work into the target field's vocabulary, build at least one demonstrated piece of work in the new domain, and choose your change type honestly — the playbook differs by type, and applying the wrong one is the most common mistake.