The Career-Change CV Translation Problem Nobody Warns You About

A primary school teacher with eleven years of experience sends her CV to a product manager role at a fintech and gets nothing back. Not a rejection, not a recruiter call, not a polite no. She is, by every honest measure, an extremely competent operator — she has run multi-stakeholder projects under tight deadlines, written instructional content read by hundreds of people every week, and managed a room of thirty humans with conflicting needs for a decade. The CV she sent describes none of this in language a product manager can recognise.

This is the career-change translation problem, and nobody warns you about it before you start applying. The verbs that earned you credibility in your old industry — differentiated instruction, briefed counsel, cared for patient cohorts — are completely inert to a hiring manager who has never worked in your field. They are not bad verbs. They are simply foreign currency. The reader cannot exchange them for anything.

Why the translation problem is real

Hiring managers do not read CVs charitably. They read them quickly. A widely cited Ladders 2018 eye-tracking study found recruiters spend an average of 7.4 seconds on a first-pass scan. When they hit a phrase they don’t recognise in that window, they don’t pause to puzzle it out — they skim past, and your experience evaporates. A teacher’s CV that mentions “formative assessment cycles” looks, to a SaaS hiring manager, like noise. The same teacher saying “weekly feedback loops with thirty users to refine the next iteration” looks like product instinct.

The mistake most career-changers make is assuming the reader will see through the surface language to the underlying skill. They won’t. They have forty other CVs. The translation is your job — and the same logic applies further down the page, where most candidates leave their skills section full of old-industry shorthand.

The two ends of the translation spine

Every translation has two ends — the verb and the noun. The verb describes what you did. The noun describes what you did it to. The trick is that one end stays fixed and the other moves.

Keep the verb concrete. Move the noun.

If you taught a class, you taught — that’s the concrete verb. The noun (“a class”) needs to be translatable in context, so the reader understands the scope and difficulty without you having to claim you ran a sprint when you didn’t. “Taught thirty-two Year 5 students across literacy, maths, and science, including five with statemented additional needs” gives a product manager a much richer picture of stakeholder management than “implemented agile delivery cycles across diverse user cohorts.”

The “after” doesn’t translate teaching into product. It describes teaching in language a product reader can recognise as planning, iteration, and feedback loops — without forcing the analogy. That’s the move.

Translations that work, in two directions

The same logic applies if you’re coming from law into ops, from clinical work into health-tech, from journalism into content, from the military into project management. The pattern is identical: describe what you actually did, in concrete terms, using nouns the new reader can place.

The legal version is full of verbs a lawyer immediately respects — drafted, briefed, managing matter timelines — but a startup ops lead glazes over by the second clause. The translated version uses the same underlying truth (writing under deadline, coordinating specialists, tracking many parallel workstreams) in nouns and numbers the ops reader can place against their own work.

The four translation rules

The rules that hold up across hundreds of real career-change CVs compress to four:

• Keep the verb concrete. Taught, wrote, ran, coordinated, built, repaired, treated, audited. Verbs that name a physical action survive any industry. Avoid abstractions like "leveraged," "facilitated," "enabled."
• Translate the noun, not the verb. Don't say you "implemented sprints" — say you "ran a weekly planning cycle for a team of six." The shape is sprint-like; the noun is honest.
• Add scope numbers. Thirty-two pupils. Twelve live matters. Two-thousand-bed hospital. Numbers travel across industries; jargon doesn't.
• Use the new industry's noun for the thing you actually had. A primary school class is a "user group of mixed ability." A legal matter is a "workstream." A patient cohort is a "recurring user base." One noun shift, not a full impersonation.

Notice that none of these rules let you claim something you didn’t do. Translation is a re-description, not a promotion.

Mapping the common moves

Some pairings come up so often it’s worth seeing them laid out. These aren’t formulas — they’re rough analogies you can adapt to your specific roles.

Teaching into product:

• Lesson planning ≈ sprint planning
• Classroom management ≈ stakeholder management
• Formative assessment ≈ user research feedback loops
• Differentiation ≈ designing for different user segments
• Parents’ evening ≈ external stakeholder review

Law into operations:

• Drafting briefs ≈ writing internal documentation
• Managing matter timelines ≈ project management with external dependencies
• Client advisory ≈ stakeholder navigation under ambiguity
• Due diligence ≈ pre-mortem and risk review
• Bundling and disclosure ≈ documentation and handover

Clinical work into health-tech or operations:

• Triage ≈ prioritisation under pressure
• Care planning ≈ structured planning for individuals at scale
• Handover ≈ async documentation across shifts
• Multidisciplinary team meetings ≈ cross-functional coordination

The analogy is never perfect. It does not need to be. It needs to be close enough that the reader places you somewhere on their mental map of “people who could do this job.”

The trap of over-translation

The danger of learning to translate is that you over-do it. There is a recognisable point where a CV stops describing what someone did and starts impersonating someone from the new industry — and hiring managers smell it immediately.

The pattern that holds up under examination is this: the over-translated CV is worse than the un-translated one. A hiring manager can place a teacher who sounds like a teacher and decide whether to interview. They cannot place a teacher who is performing the part of the product manager they want to become — and they will usually default to a candidate who already does the role.

The principle is counter-intuitive but consistent: under-translation costs you the open; over-translation costs you the interview. The middle, where you describe real work in clean nouns and concrete verbs, is where career-changers land. The same logic that governs verb choice in this piece is the broader case made in our guide to action verbs that actually land.

What to do with this on Sunday night

If you are sending a CV into a new industry this week, the rewrite job is smaller than you think. Open the most recent role on your CV. Look at the verbs. Cross out anything that is specific to your old industry’s vocabulary — briefed, differentiated, clerked, triaged, deployed (if military), ran a service. Replace each with the concrete physical action underneath: wrote, taught, organised, prioritised, ran. Now look at the nouns. Translate them once, gently, into the new industry’s terms. Add one number per bullet. Don’t claim a single thing you didn’t do.

You will end up with a CV that reads like a competent operator from another field who has done their homework. That is, in fact, what you are. That is what hiring managers in your new industry are willing to interview. If you’re switching late — and most career-changers are — our piece on career change at 40 covers the cover-letter side of the same move, and the non-linear career story framing helps when your last three roles don’t connect on the page.