How to translate experience to a field you haven't worked in
You don't have zero experience in the new field. You have twenty years of transferable experience that nobody, including you, has bothered to translate yet.
Elena has 12 years as a high school biology teacher. She wants to move into corporate learning and development at a pharmaceutical company. On paper, she has zero years of "L&D experience." In reality, she has run 2,400 lessons, designed 38 curriculum units, trained 14 student teachers, managed parent stakeholders with conflicting demands, and measurably improved test scores across four cohorts.
She is not entering L&D with zero experience. She's entering with more experience than most people with the job title. She just hasn't translated it yet.
This is the core skill of a career change: taking work you actually did and describing it in the language of the field you're moving into. Most people are terrible at this, which is why they end up feeling like they're starting from scratch at 38.
The translation move in one sentence
Describe what you did using the nouns and verbs of the target field, not your current one.
That's it. That's the whole trick. But it's harder than it sounds, because the nouns and verbs of your current field are so familiar you can't see them as jargon anymore.
A teacher says "lesson planning." An L&D professional says "instructional design." Same activity. Different language. If Elena writes "lesson planning" on her CV, an L&D hiring manager will unconsciously score her as a teacher applying for a non-teaching job. If she writes "instructional design," she becomes an instructional designer who happens to have worked in a classroom.
This is not dishonesty. It's translation.
How to find the right words
Go find 15 job descriptions in the target field. Read them carefully. Make two lists.
On the left: every verb that appears more than twice. On the right: every noun and piece of jargon that appears more than twice.
For L&D roles, the left-hand list might look like: design, facilitate, evaluate, iterate, roll out, measure. The right-hand list: learning objectives, competency framework, stakeholder alignment, LMS, KPIs, needs analysis, blended learning.
Now, for each thing you've actually done in your current job, ask: can I describe this using one verb from the left and one noun from the right? If yes, you've just translated a line.
Elena's "I taught a new cell biology unit to 11th graders" becomes "Designed and facilitated a 6-week learning module, iterating based on formative assessment data." Same activity. Different audience.
Three kinds of translation that actually work
Scale translation. You managed 30 teenagers daily. That's stakeholder management, group facilitation, and conflict resolution. Don't downplay it because it was kids. Anyone who has held attention in a 30-person room for 45 minutes has skills that a lot of corporate professionals lack.
Outcome translation. You improved student test scores by 18%. That's a measurable training outcome. Any L&D team would recognize it as exactly the kind of thing they try to do. Lead with the number.
Tool translation. You used Google Classroom, ran summative assessments, did parent-teacher conferences. In corporate terms: LMS administration, KPI reporting, stakeholder reviews. Same workflow. Different vocabulary.
A concrete before-and-after
Here's Elena's old CV bullet:
"Taught AP Biology to 11th and 12th grade students; created lesson plans and assessments."
Here's the translated version:
"Designed and delivered a year-long learning program for 140 adult-adjacent learners, including needs analysis, content development, formative and summative evaluation, and iteration based on learning outcomes data. Program outcomes exceeded district benchmarks by 18% over three consecutive cohorts."
Nothing in that sentence is untrue. It's the same job. But a hiring manager reading it sees an instructional designer, not a biology teacher who's lost.
The "adjacent language" trap
One warning. If you over-translate, you'll sound like you're hiding something or using buzzwords. The goal is to describe what you actually did using the target field's language — not to pretend you did something you didn't.
If you've never used an LMS, don't write "LMS administration." Write "managed course materials and student progress tracking across digital tools," which is honest, and happens to be transferable. Any L&D team will read between the lines and know you can learn their specific platform in a week.
The test: could someone who saw you do the actual work read the translated bullet and nod? If yes, you're fine. If they'd cringe, you've gone too far.
Where to use the translation
Three places, in order of importance:
- Your opening line in any introduction conversation. "I'm a teacher moving into L&D" positions you as a beginner. "I'm a learning designer with 12 years of classroom experience moving into corporate" positions you as a lateral hire.
- Your CV summary and bullet points.
- Your LinkedIn headline and About section.
Most people get #1 wrong, which means every later step is uphill. Spend an hour writing your new opening line and saying it out loud until it stops feeling like a lie. It's not a lie. It's a more accurate description of what you've done.
The takeaway: you don't have less experience than the other candidates. You have different experience, described in the wrong language. Spend a weekend relearning to describe your last decade in the vocabulary of the next one, and you'll stop feeling like a beginner.