How to Write a CV for a Career Change (Without Erasing Your Past)

Why career change CVs are harder than they should be

The conventional CV is built for someone whose past predicts their future. Yours doesn't, at least not on the surface. That mismatch creates two specific recruiter fears you need to defuse:

• Will this person actually do the new job, or are they job-shopping? Recruiters worry that career changers will return to their original field within a year if it doesn't work out — wasted hiring, wasted onboarding
• Can they actually do the new job? Without a track record in the field, recruiters need other evidence that you have the skills — and they're not going to give you the benefit of the doubt
• The bigger the field gap, the louder both fears get. A retail manager moving into UX is more friction than a marketing manager moving into product
• Both fears collapse fast when the CV is engineered for the situation. Most don't. The ones that are stand out massively

Knowing what recruiters fear is half the work. The other half is engineering the CV — and the cover letter, and the portfolio of proof — to address those fears directly rather than hoping they don't come up. They always come up.

The five-part reframing framework

A career-change CV has five distinct moves it needs to make, in order. Each one closes a different recruiter worry. Skip any of them and the CV reads as confused; do all five and it reads as deliberate.

Concrete vocabulary translations by field

The five-part framework is the structure; the actual translation work depends on where you're coming from and where you're going. A few common transitions and the vocabulary shifts that work:

The translations work because they describe the actual transferable activity, not because they hide your background. A retail manager who led a team really did lead a cross-functional team; an engineer who refactored services really did prioritise technical debt. You're naming the work in language the new field recognises.

The "one-line bridge" technique — examples for common transitions

The single most important line in a career-change CV is the bridge sentence in your summary. It explicitly connects past to future and saves the recruiter from having to figure it out. Four worked examples:

• Teacher → product manager: "Eight years teaching secondary maths; transitioning into product management after a year of side projects building learning-tech tools, the most recent of which reached 4,000 weekly active users. Looking for an associate PM role at an edtech company where my classroom-floor product intuition is an asset."
• Engineer → data science: "Senior backend engineer (7 years) moving into data science; completed Stanford's CS229 plus three deployed projects on Kaggle (top 8% in two competitions). Looking for a mid-level data science role at a company that ships ML to production rather than treating it as research."
• Retail manager → UX: "Eight years managing multi-store retail operations; transitioning to UX research after the Google UX Design certification and three end-to-end projects shipped with feedback from real users. Looking for a junior UX research role where my experience interviewing customers daily for nearly a decade is a credible foundation."
• Lawyer → consulting: "Six years corporate law (M&A team at top-tier firm); transitioning to management consulting. Recently completed McKinsey's online case-prep programme and four case-interview cycles with hired coaches. Looking for an analyst role where my contract-structuring and stakeholder-management experience translates into client work."

Notice the pattern: each bridge names the past (with credibility-establishing detail), names the future (with the specific role they're going for), and provides the proof that the transition is real (cert, projects, hours invested). The recruiter doesn't have to wonder if you're serious — the bridge demonstrates it.

Building the portfolio — the proof you actually need

The career-change CV references the portfolio; the portfolio is what closes the deal. Without it, the CV is just a claim that you can do work you haven't demonstrated. With it, the CV reads as evidence-backed.

What counts as portfolio for a career-changer:

• A completed certification or degree program in the target field — Google certificates, AWS, Coursera specialisations, university certificates
• Two or three substantial projects, ideally with measurable outcomes — "built and deployed X; reached Y users; performance was Z"
• Freelance or contract work in the target field, even small engagements — three small clients beat zero big ones
• Volunteer work in the target field — non-profits often welcome career-changers and the work counts
• Public artefacts that demonstrate the skill — a GitHub profile, a published portfolio site, a blog, conference talks, articles

Realistic time investment: building a credible portfolio for a major career change typically takes 6-18 months of part-time work alongside your current job. Start before you start applying — every application sent before the portfolio is ready burns a contact unnecessarily.

Where to talk about WHY (cover letter vs CV)

The CV announces the change; the cover letter explains it. Trying to do both on the CV crowds out the actual content; trying to avoid the topic in both makes the application read as evasive.

• CV summary — one line that acknowledges the transition and frames the bridge. Doesn't explain why
• Cover letter — the story. Why this change, why now, why this specific company, what you've done to prepare. Three short paragraphs
• Interview — the deeper context if asked. Most interviewers will ask once and accept the answer; have a 90-second version ready

The cover letter is also where you reassure the recruiter that this isn't a phase. Concrete preparation (certifications completed, projects shipped, hours invested) closes the "will they stick with it?" fear far better than any sentence about passion. Show the work, not the enthusiasm.

Things that work surprisingly well for career changers

Beyond the CV itself, certain application strategies disproportionately help career-changers. Four worth knowing:

• Adjacent moves first — pivoting from teaching to L&D (corporate training) is easier than teaching to UX. Once you've made the adjacent move, the next move is incremental rather than dramatic. Two adjacent moves often beat one dramatic one
• Smaller companies before bigger ones — startups and SMBs care more about what you can do than about credentialing. A senior engineer at a 20-person startup who needs a product person will care about your projects; a hiring manager at a 50,000-person corporate will need to justify hiring a non-traditional candidate to a committee
• Internal pivots before external ones — if you're already at a company you like and the company has the kind of role you're targeting, the internal move is almost always easier than the same move externally. Internal candidates have credibility the external candidate has to earn from scratch
• Bootcamp and apprentice routes for steep changes — for transitions where the skill gap is large (engineering, data, design), formal retraining programmes (bootcamps, apprenticeships, graduate-entry tracks) provide both the skills and the credentialing in one package

These aren't workarounds — they're the high-percentage paths most successful career-changers actually take. The lone applicant cold-applying to a senior role in a totally new field is rare; the path that worked is usually some combination of the above.

What NOT to do

A few patterns reliably sink otherwise-strong career-change applications. Avoid all of these:

• Hiding the past — trying to make your CV look like you're already in the new field without acknowledging the transition reads as evasive. Recruiters check LinkedIn
• Apologetic language in the summary — "despite my background in retail" frames the past as a problem. The bridge sentence frames it as relevant
• Generic career-change phrases — "seeking new challenges", "passionate about pivoting into X", "committed to this transition" all read as filler. Specific evidence beats every adjective
• Sending the same CV to both old-field and new-field roles — the career-change CV underperforms in the old field (looks distracted) and the old-field CV underperforms in the new field (looks irrelevant). Maintain two versions
• Skipping the cover letter — the CV alone can't explain a career change. Always send a cover letter for career-change applications, even when the job posting says it's optional
• Underestimating preparation time — applying before the portfolio is ready burns contacts. Get the proof together first, then apply

Pre-send checklist for career-change CVs

• Summary opens with the bridge sentence — past + future + explicit link
• Skills section is above experience (not below)
• Skills are grouped by relevance to the new role, not by source
• Past role bullets use the vocabulary of the target field
• Portfolio is built and at least one substantial artefact is shipped
• Portfolio is referenced in the summary and at least one experience entry
• Older roles are compressed; only transferable-skill bullets remain
• Cover letter prepared for every application — never skipped
• No apologetic language anywhere on the CV or in the cover letter
• Specific preparation evidence (certs, projects, hours) named with numbers

A career-change CV done well doesn't hide what you've done — it makes everything you've done feel obviously relevant to where you're going. The transition that read as awkward before the CV was engineered reads as deliberate after it. That shift is the entire game; the framework above is how you produce it.