Changing careers? Find the experience you can carry with you

Start with tasks, not adjectives

“I am organised, resilient and a good communicator” may be true. It does not show what you can do in a different setting.

Describe a piece of work instead: coordinating a launch across several teams, resolving a recurring customer problem, producing a forecast, teaching colleagues a process or managing a supplier handover. Identify the decisions you owned and the limits of your responsibility.

O*NET^[1] groups transferable skills that can be used across occupations, including problem solving and resource management. Such a vocabulary can help you spot connections. It is not a certificate that you are qualified for every role using the same skill.

Handling a difficult customer and negotiating a complex enterprise contract both involve communication. That does not make them interchangeable. Scale, technical knowledge, commercial responsibility and consequences matter.

Build a comparison that can disagree with you

Take a few current adverts for one target role. Note recurring tasks, but keep the differences visible. A title can cover several kinds of job, and copying requirements from unrelated vacancies can create an imaginary position that no employer is hiring for.

For each important task, write four short entries: what the employer needs, your closest example, what changes in the new context and what evidence is still missing.

In a fictional example, Leila manages operations for training events and wants to move into project coordination for a software company. She has planned delivery dates, coordinated suppliers and resolved last-minute changes. Those are relevant experiences. She has not managed a software backlog or worked through a technical release.

Her comparison might say: “Coordinate dependencies: I planned trainer, venue and materials readiness across events. New context: engineering dependencies and release constraints. Gap: I need to understand how this team identifies and tracks a blocked delivery.”

That is more credible than “My event experience is basically project management in tech”. It gives a hiring manager something specific to evaluate.

Distinguish an evidence gap from an entry requirement

An evidence gap means you may have the capability, but have not demonstrated it clearly. A knowledge gap means there is something you genuinely need to learn. An entry requirement may mean a particular qualification, licence or experience is mandatory for that employer or occupation.

Do not spend money on training until you know which problem it addresses. A certificate will not necessarily replace required experience. Equally, an appealing personal project cannot substitute for a legally required professional qualification.

Check requirements with the relevant official professional body or employer where needed. O*NET is a US occupational reference, so it should not be treated as proof of entry requirements in your country.

For Leila, the next step could be asking someone in a target team how project coordinators work with technical specialists. She might then practise tracking dependencies in a clearly labelled fictional project. The exercise is evidence of learning, not a claim that she has delivered a commercial software release.

The right next step is sometimes a conversation or supervised exposure, not another course. Sometimes it really is a recognised qualification. Your comparison should help you tell the difference.

Write a bridge sentence without disguising your history

A bridge sentence connects your actual background with the target work: “I coordinate multi-party training delivery, including schedules, dependencies and changes. I am now looking for project-coordination roles where that delivery experience is relevant, while building my understanding of software release processes.”

Keep your real job titles in your experience history. You can explain the work beneath them without renaming your previous role into the job you want.

For a CV or interview, choose two examples that demonstrate the connection. Explain the scale, the problem, your contribution and the outcome you can support. Do not rely on the bridge sentence to do the work of evidence.

Be equally clear about what you have not done. “I have not owned a technical release. My closest experience is coordinating several delivery dependencies, and here is how I approached it” is a useful starting point for an honest conversation.

Consider a move that changes fewer things at once

You may not need to change function, industry, seniority and employment type in a single leap. A similar role in the target industry could help you learn its context. A different function in your current organisation could make your existing knowledge useful while you build experience.

These are options, not universally better routes. An internal move may be unavailable, and a supposedly adjacent role may still be a poor fit. Compare the actual work, support, pay and learning opportunity rather than assuming a familiar employer makes a move safe.

Also decide what you are not willing or able to trade away. A route that requires an unaffordable income drop is not practical simply because it sounds like a good career story.

Your next move

Choose one target role and complete the four-entry comparison for three important tasks. Finish by naming one piece of existing evidence and one gap that needs checking.

You do not need to persuade yourself that everything transfers. You need a clear account of what does, what does not, and what the next step would teach you.

To make your examples clearer, turn responsibilities into CV evidence without inventing numbers. Before paying to close a skills gap, try the task you want a course to teach you.

About this guide

O*NET OnLine: Browse by transferable skills. Provides an occupational skills vocabulary. The comparison exercise and Leila's story are original CareerFood guidance and a fictional example. Skill overlap is not proof of suitability, hiring demand or professional eligibility.