Writing a CV for a Career Change: The Four-Step Reframe

Career-change job hunts are the hardest kind. Not because the people doing them are unqualified — they almost always have a decade of valuable, transferable experience — but because the system is biased towards obvious matches, and a career-changer is by definition not an obvious match.

I've worked with hundreds of people through career pivots — operations to product, finance to data, journalism to UX, teaching to learning design, military to almost everything. The pattern is the same every time. They start by sending the CV they already have and getting nothing. Then they panic and either rewrite from scratch (badly) or give up.

Neither works. What works is the four-step reframe: a structured way of taking your existing CV and translating it into the new field, without lying and without burying who you are.

Step zero: stop hiding the pivot

The biggest mistake career-changers make is to hide the change and hope nobody notices. They keep the same job titles. They keep the same bullets. They submit it to product roles and hope a recruiter will magically see "operations manager" and think "obviously this person could do product."

They won't. Recruiters scan for fit, not potential. If you don't tell them what story to read, they read the obvious one — that you're an ops manager applying to a product role for some reason, probably opportunism. Into the maybe pile, which is the no pile.

The reframe starts with naming the pivot at the top of your CV, in your summary, in the most obvious place possible. Once a reader knows the story, every bullet beneath it is read in that frame.

Step one: rewrite the summary to name the pivot

Your summary is two to three sentences at the top of the CV. For a career-changer, this is the single most important section — more important than your job history, more important than your skills.

A bad career-change summary:

> "Operations manager with 6+ years of experience in fast-growing startups. Strong communicator and team player."

Tells the reader nothing. Doesn't acknowledge the pivot. Sounds like every other ops CV.

A good career-change summary:

> "Operations manager pivoting into product management. Six years building cross-functional processes inside fast-moving startups — owning roadmaps for internal tools, prioritising trade-offs across engineering and ops, and shipping software-adjacent workflows from spec through launch. Looking to bring the same systems thinking to external product."

This does several things. It names the pivot in the first six words. It frames the existing experience as relevant ("software-adjacent workflows"). It uses the target industry's vocabulary — roadmap, trade-offs, ship — without lying. And it tells the reader exactly what story to look for in the bullets below.

The summary is doing 80% of the reframing work. Spend disproportionate time on it.

Step two: translate bullets into the target industry's language

This is where most people stop short. They rewrite the summary, leave the bullets identical, and wonder why the rest of the CV reads like a different person wrote it.

Translation is not lying. It's choosing the words your target industry uses for things you actually did.

A few real examples:

• "Led a project to streamline reporting" → "Owned the roadmap for an internal reporting tool. Wrote specs, ran sprint planning with engineering, shipped four versions in six months, ran user interviews with finance to prioritise the next quarter."
• "Trained new staff on company processes" (teacher → learning designer) → "Designed and delivered a 12-module onboarding curriculum for 40+ new hires. Iterated based on weekly feedback surveys; reduced ramp time by 35%."
• "Wrote weekly internal newsletters" (journalist → content marketer) → "Owned a weekly content channel reaching 1,200+ internal readers. Drove a 40% open rate and a measurable 25% lift in cross-team awareness scores."

Same work in every case. Different language. The translated version sounds like someone who already does the target job — because functionally, you do.

The rule is: never invent. Always translate. If you didn't write specs, don't say you wrote specs. But if you wrote project briefs that contained user requirements and acceptance criteria, that's a spec, and you can call it one.

Step three: front-load transferable skills

Add a short section above your experience — call it "Highlights", "Transferable Skills", or "Core Competencies" — that lists the four to six things you've done that map directly to the target role. This is for the recruiter's six-second scan; it's the section that pulls them into the rest.

For an ops-to-product pivot, that section might look like:

• Roadmap ownership across cross-functional teams (engineering, ops, finance)
• User research and stakeholder interviews to shape feature prioritisation
• Spec writing and acceptance criteria for internal tools
• A/B testing operational changes and measuring outcomes
• Comfort with SQL and data analysis (Looker, dbt, Mode)
• Leading projects through ambiguity from idea to launch

Each bullet is true. Each bullet is in the target industry's language. Each bullet maps directly to a real product job description. The reader sees this section and the entire CV beneath is read in a different frame.

Step four: drop the bullets that don't help

This one feels counterintuitive, especially if you're proud of what you did. But every irrelevant bullet on a career-change CV is dilution. It pulls the reader's attention away from the pivot story and back into your old industry.

Yes, you ran the office's social committee for three years. Yes, you built the Excel macros that made finance close two days faster. Yes, you handled the legal review of three vendor contracts. If they don't help your case for the new role, drop them or compress them into a single line.

The CV gets shorter. The story gets sharper. The reader sees a focused candidate, not a generalist.

The two real obstacles, and how to handle them

After the four-step reframe, two obstacles remain. Both are addressable.

Obstacle 1: lack of formal experience in the target field

You can't translate around a complete absence. If you're moving into product management and you've never owned a roadmap of any kind — internal, external, side-project — you'll struggle.

The fix is to create one piece of real evidence before applying. Build a side project. Write a public spec for a feature in a product you use. Take on a stretch assignment in your current role that gets you a roadmap of any kind. One concrete piece of new-field experience changes the entire CV from "translation" to "translation plus proof".

Obstacle 2: pay history

This one is structural. If you're moving from a high-pay industry (finance, law, consulting) into a lower-pay one (product, content, design), some recruiters will skip you assuming you'll bail in six months. There's nothing on the CV that fixes this directly. The fix is in the cover letter — name it, address it, explain why the move is permanent.

Where AI helps (and where it doesn't)

A tool like ours [career-change CV builder](/cv-for-career-change) does steps one through three automatically. You paste your current CV and a JD for the role you want; it rewrites the summary, translates every bullet into the target industry's language, and generates a transferable-skills section pulled from your real experience.

What it can't do is decide what to drop in step four (you know best what's actually irrelevant), and it can't fabricate the side-project evidence in obstacle one. Those are still your job.

But the heavy lifting of translation — the part that takes most career-changers six painful hours and three failed drafts — happens in 30 seconds. You're left with the parts that actually require human judgment, which is where your time should go.

The honest bottom line

Career-change CVs aren't harder because the people writing them are less qualified. They're harder because the existing CV was written for a different audience, and most career-changers don't know they need to translate. Once you do — once you name the pivot, translate the language, and trim the irrelevant — you stop being an outsider trying to break in. You start being an obvious fit who happens to come from somewhere unexpected.

That's the version of you that gets the interview.