How to write a CV when you're switching careers (without looking desperate)

You spent six years in consulting. Now you want a product management job. Your CV lists "MECE frameworks" and "client presentations" — neither of which is in any PM job description. Every piece of career advice says "focus on transferable skills" without telling you how.

This is the playbook we give career switchers. It works for any direction: ops → product, teacher → engineer, finance → marketing.

Step 1: Find the bridge

Before you touch your CV, ask yourself the uncomfortable question: what in my current work actually maps to the new role?

The dumb answer is "soft skills — leadership, communication, problem-solving". Every candidate has those, so they don't differentiate you.

The good answer is a specific, concrete bridge. Some examples:

• Consultant → PM: "I've sat in weekly steering committees with C-suite execs — stakeholder communication under pressure is my default mode."
• Teacher → UX designer: "I've A/B-tested lesson plans on 300+ students. Iterating on user experience based on real feedback data is literally my job."
• Ops lead → Data analyst: "I rebuilt our inventory forecasting model in Excel; now I want to do the same work at scale with Python and a real warehouse."

One concrete bridge is worth more than a list of transferable skills. Find yours before you write anything.

Step 2: Rewrite your experience section around the bridge

Your current work history is probably described in the vocabulary of your old industry. That's fine for your current role; it's deadly for a career switch.

Before (consultant trying to become a PM):

• Led a 6-person engagement team through a supply chain transformation for a Fortune 500 retail client
• Developed MECE frameworks to diagnose root-cause issues across 3 business units
• Presented findings to the C-suite and managed stakeholder alignment

After (same person, reframed for PM):

• Owned the roadmap for a supply chain transformation (6-person team, 9 months) — shipped 4 workstreams end-to-end, including a new inventory dashboard used by 120+ store managers
• Ran weekly steering committees with the VP Ops, COO, and CIO; built the prioritisation framework they still use to decide between competing operational bets
• Defined the success metrics for the rollout (inventory turnover, stockout rate, NPS) and tracked them monthly post-launch

Same work. Reframed in PM vocabulary: roadmap, workstreams, stakeholders, prioritisation framework, success metrics, post-launch.

This is where most career switchers fail. They don't reframe. They submit the same consulting CV to a PM role and wonder why they're not getting callbacks.

Step 3: Add a "pivot projects" section

Recruiters are allergic to career switchers because the risk is real — you might hate the new field. The single best way to de-risk yourself is evidence you've done the new work, even informally.

If you're trying to switch into engineering:

• A real GitHub with 3-5 projects (even small ones)
• A side-project deployed to a URL
• An open-source contribution, even a tiny one
• A blog post explaining something technical

If you're trying to switch into product management:

• A case study deck for a product you'd redesign
• A write-up of a side project you PM'd, even with 2 users
• A Medium post analysing a product launch

If you're trying to switch into data:

• A public Kaggle notebook
• A personal SQL challenges repo
• A Tableau public profile with dashboards

Make this section prominent. Put it above your old work history if the old history is irrelevant. The recruiter needs to see evidence that you've actually started doing the new work — not just want to.

Step 4: Write a summary that addresses the pivot head-on

Pretending the switch isn't happening is worse than acknowledging it. A good summary says, in three sentences:

1. Who you are today (the relevant bits of your current role)
2. Why you're pivoting (in one sentence — not a life story)
3. What you bring that makes the switch viable

Example (consultant → PM):

"Management consultant (6 yrs) specialising in retail operations and supply chain. Pivoting to product management because I've spent the last 2 years doing PM work on my engagements — owning roadmaps, running steering committees, defining success metrics — and want to make it my full-time role. I've completed Reforge's PM Foundations and built 2 PM case studies (links in Projects)."

Direct. Evidence-backed. No apologising.

Step 5: Cut ruthlessly

The temptation is to keep all your old work because "experience counts". For a career switch, most of your old work actively works against you — it signals that your default is the old role, not the new one.

Cut:

• Awards, certifications, and bullets that only make sense in the old field
• Tools and acronyms from the old field that aren't used in the new one
• Extra-detailed descriptions of old roles — compress them to 2-3 strong bullets each
• The hobbies / languages section (unless relevant to the new role)

What you keep should be defensible in a sentence: "I kept this because it shows X, which is relevant to Y."

Step 6: The cover letter does heavy lifting

For a career switch, the cover letter is not optional. It's where you address the pivot in full, explain the bridge, and pre-empt the "why are you applying to this?" question.

Keep it short (250 words) and honest. See our cover letter guide for the structure.

Step 7: Target roles realistically

Even with the best CV rewrite, a 6-year consultant probably won't land a Staff PM role at Google on a first application. Calibrate:

• First 6 months: target roles where your old experience is a nice-to-have bridge — consulting → PM at a B2B SaaS selling to enterprises, teacher → UX researcher in edtech, finance → marketing at a fintech.
• Month 6+: once you have one role in the new field on your CV, you become a much easier yes to the next company.

Most career switchers hate this advice because they want to jump directly to the ideal role. The math doesn't usually work. One bridge role buys you access to the rest of the industry.

How CVCL handles career switches

If you paste a PM job description and upload your consultant CV, CVCL will reframe your existing experience in PM vocabulary automatically. It won't invent new experience — we're strict about that — but it will translate what you've done into the language the recruiter wants to read.

Score-matching is free (no credit cost), so you can sanity-check whether a specific pivot role is a realistic fit before spending a credit.

3 free generations on signup at cvcl.online.

TL;DR

1. Find one concrete bridge between your old and new roles — not "transferable skills"
2. Reframe your work history in the new industry's vocabulary
3. Add a pivot projects section — real evidence you've started the new work
4. Summary addresses the pivot directly — no pretending
5. Cut ruthlessly — everything that doesn't support the pivot is dead weight
6. Cover letter does real work — not optional for switches
7. First role in the new field is the hardest. Calibrate accordingly.