Career change: how to structure your CV when you switch fields

You're switching careers and sending out a classic chronological CV. The recruiter sees "French teacher for 8 years" at the top of the page and doesn't read further. Yet you've completed a developer bootcamp, built side projects, and have exactly the skills they're looking for. The problem isn't your background — it's the way your CV tells the story. Here's how to structure a career-change CV that opens doors.

Why the classic reverse-chronological CV sabotages you

The reverse-chronological CV — the one we all learn to write — is designed for linear careers. You read from most recent to oldest, and logically the current role aligns with the target role.

For a career changer, this structure does the opposite: the first thing the recruiter sees is your former field. If you're applying to a UX designer role and your CV opens with "Senior Accountant — KPMG", the cognitive filter fires within 3 seconds.

Three classic pitfalls of going chronological during a career change:

1. Transferable skills buried inside bullets from your old role, where nobody looks for them.
2. Vague summary like "Currently in career transition toward X" — sounds defensive instead of assertive.
3. Recent training poorly placed: your fresh certification sits on page 2, after your 2005 initial degree, like a footnote.

The solution: skills-based or hybrid format

Two structures work for career changers. Pick based on your profile.

Skills-based CV (for radical changes)

Best when the old and new fields share nothing on the surface (teacher → developer, military → coach, doctor → consultant). Structure:

1. Target role title + a 1-sentence headline (avoid "career changer").
2. Skills block instead of an Experience block: 3-4 core competencies, each followed by 2-3 lines proving them with examples from varied sources (professional, personal, training).
3. Condensed work experience: just titles + companies + dates, no detailed bullets.
4. Education: most recent first (notably your certification or bootcamp), with some detail (key modules, projects).

Hybrid CV (for adjacent transitions)

Best when the new field uses part of the previous one (accountant → financial controller, IT project manager → product manager). Structure:

1. Target role title + headline.
2. Key Skills block (4-6 skills listed simply, no paragraph).
3. Standard reverse-chronological work experience, but rewritten to align past responsibilities with the new field's vocabulary.
4. Education with the new certification prominently featured.

The headline: 2-3 sentences that frame the project

This is the most critical element of a career-change CV. Badly written, it sabotages everything else. Well written, it opens the whole read.

What to avoid:

"After 10 years in teaching, I'm transitioning into web development. Motivated and rigorous, I'm looking for my first opportunity."

Three problems: your former field first (defensive reflex), "transitioning" sounds fragile, and "first opportunity" puts you in a weak position.

What works:

"Front-end developer trained at General Assembly, with 3 shipped React projects and 8 years of teaching experience that taught me how to explain complex systems to non-technical audiences. Looking for a product team that values internal pedagogy."

You lead with what you are now (developer), reframe your old field as a differentiating asset (pedagogy), and state what you want.

Transferable skills: the goldmine to mine

The classic career-change mistake is thinking you need to erase your past. Quite the opposite: your former field contains skills that "native" candidates in the new field don't have.

Concrete examples

Teacher → developer:

• Technical communication (explaining abstract concepts simply).
• Patience with errors (debugging = correcting student work on loop).
• Managing a diverse group (equivalent to code review, mentoring juniors).

Accountant → UX designer:

• Structural rigour (information architecture, taxonomies).
• Reading numbers (analytics, A/B testing).
• Working within regulatory constraints (GDPR, accessibility, SOX).

Military → project manager:

• Crisis management.
• Multi-team coordination under pressure.
• Concise hierarchical reporting.

List these skills explicitly in your dedicated block. Don't count on the recruiter to bridge the gap for you — they won't.

What to keep from the old field, what to trim

Keep what serves the new project. Trim the rest.

Keep:

• Quantified achievements showing impact (any sector).
• Cross-functional skills clearly named.
• Recent experiences (last 5-7 years), even in the former field.

Trim or reduce:

• Technical details of the old field that don't interest the new one (specific accounting frameworks if you're targeting design).
• Detailed tenure beyond 10-15 years: one line is enough.
• Very old degrees unrelated to the new field (unless prestigious school, keep it short).

US vs UK considerations for career changers

Most of the rules above apply equally to US and UK markets, but two specifics:

• US (Resume): keep length to 1 page even as a career changer. American recruiters expect a tight document and read fast. Maximise quantification on transferable skills.
• UK (CV): 2 pages standard is fine for career changers — gives you room to explain the transition properly via the Personal Statement and the skills block. UK recruiters tolerate slightly more context.

In both markets, drop the photo, date of birth, and any French-style fields. The new identity you're claiming needs to read cleanly to local norms.

Case studies

Teacher → developer

A maths teacher in secondary school (10 years) finishing a Le Wagon bootcamp. Old CV: "Mathematics Teacher — State School System, 2014-2024" at the top.

New CV (skills-based):

• Title: Front-end React Developer
• Headline: shipped React projects + pedagogy as an asset
• Skills: React/TypeScript (with projects), Technical pedagogy (with examples), Structured problem-solving (with maths + code examples)
• Condensed experience: 2 lines for teaching + 1 paragraph for bootcamp projects
• Education: Le Wagon 2024 prominently featured

Result: interviews landed within 6 weeks.

Accountant → UX designer

An accountant with 12 years of experience completing the Google UX Design certificate. Hybrid format:

• Title: Junior UX Designer
• Headline: certification + 12 years structuring complex data for easy reading
• Key skills: Figma, user research, wireframing, accessibility, data analysis, regulatory rigour
• Experience: accountant role rephrased to highlight "information structuring" and "interface between technical and non-technical stakeholders"
• Education: Google UX Design 2024 + ACCA 2012

In practice with ShotCV

Building a skills-based CV from an existing chronological one isn't trivial: you need to detect buried skills, group them, rephrase them, and pick the right headline. ShotCV's guided builder offers a "Career Change" persona that:

• automatically detects transferable skills from your existing background,
• proposes an assertive headline leveraging your project,
• switches to skills-based or hybrid format based on your profile,
• keeps you in control at every step (nothing is invented: you validate or modify).

And if you're already targeting specific postings, the refit adapts this base CV to each opportunity. For cover letters, the cover letter generator applies the same transferable-skills logic.

Conclusion

A career change doesn't sell with a classic chronological CV. Switch to skills-based or hybrid format, put the new field in your title, turn your former path into a differentiating asset via transferable skills, and put your recent training front and centre. The recruiter will read your CV for who you are now — not who you were yesterday.