You identify transferable skills by breaking your past work into specific tasks and results, then matching those tasks to the requirements in postings for the role you want. Start with what you did, not your job title, translate it into plain verbs and outcomes, and keep only the skills a target employer would care about. The process takes a few hours and produces a document you can reuse in your resume, interviews, and networking conversations.
Many career changers underestimate what they bring. They look at their old title, see no match to the new field, and conclude they are starting from zero. Most jobs contain a mix of skills that move well between fields and knowledge that does not. The work is to separate the two honestly, without overselling or undervaluing yourself.
What counts as a transferable skill
A transferable skill is something you can do that is useful in more than one setting. They usually fall into three groups.
- Working-with-people skills. Communicating, persuading, training, resolving conflict, managing stakeholders, leading a team.
- Working-with-information skills. Researching, analyzing, writing, organizing records, tracking data, spotting errors.
- Working-with-process skills. Planning, prioritizing, coordinating schedules, managing budgets, improving a workflow, meeting deadlines.
Technical skills can transfer too, such as spreadsheet modeling or writing procedures, but only when the new role uses the same or a similar tool or method. “Good communicator” appears on every resume and says little. “Wrote weekly status reports for a 12-person team and presented them to senior managers” says a lot.
Step 1: Inventory what you actually did
Go through each role in the last 8 to 10 years and write a plain list of tasks, including the informal things you ended up doing. Do not edit yet.

Ask:
- What did I do every week?
- What did people come to me for?
- What did I fix, build, or improve?
- What did I train others to do?
- What problems did I solve that were not in my job description?
Capture each task as a verb plus an object, such as “scheduled 30 appointments a day,” “trained new hires on the order system,” or “reconciled monthly invoices against the ledger.” Use real numbers where you know them, such as team size or volume, and leave them out where you do not. Do not guess.
Step 2: Turn tasks into skills and evidence
Take each task and ask what skill it demonstrates and what evidence you can point to.
| Task | Underlying skill | Evidence |
|---|---|---|
| Handled escalated customer complaints | Conflict resolution, active listening | Cases resolved, follow-up feedback you received |
| Built a weekly inventory spreadsheet | Data organization, basic analysis | Ordering errors reduced, time saved |
| Trained three new hires | Teaching, documentation | New hires working independently |
| Coordinated a store reopening | Project coordination, vendor management | Opened on the planned date |
If a row has no evidence at all, treat the skill as weaker and do not lead with it. If you are unsure what the evidence is, ask a former colleague what they remember you doing well.
Step 3: Read the target role like a buyer
Collect 15 to 25 postings for the role you want and copy the requirements and responsibilities into a document. Count how often skills repeat. Those that appear in most postings are the core of the job. Group them into themes such as “stakeholder communication,” “project coordination,” or “reporting and analysis.” Then label each requirement:
- Direct matches. Skills you have and can prove.
- Close matches. Skills you have used under a different name or in a different setting.
- Gaps. Skills you have not used at all.
The result is a map of where you are strong, where you need to reframe, and where you need to learn. It also keeps you from applying where the gaps are too large for your timeline.
You can cross-check with O*NET OnLine, which lists the tasks, skills, and work activities for each occupation and offers a Skills Search that ranks occupations by how closely they match skills you select. Use it as a prompt for vocabulary and ideas, then confirm with real postings.
Step 4: Translate your language into theirs
Different fields use different words for the same activity. A teacher “differentiates instruction,” while a corporate trainer “tailors learning to audience needs.” A retail manager “ran the floor,” while an operations coordinator “managed daily workflow and staffing.” Use the vocabulary from target postings when it honestly describes what you did.
Before: “Responsible for helping customers and handling returns.” After: “Resolved customer issues across phone and in-person channels and flagged recurring problems to the manager.”
Before: “Planned lessons and graded student work.” After: “Designed and delivered structured learning programs for groups, using assessment results to adjust content.”
Check that every translated line is true. If you did not recommend changes, do not claim it. Interviewers tend to probe, and an overstated claim can sink an otherwise good candidate. When you are ready to put these lines in a resume, see writing a career-change resume without looking scattered.
Step 5: Test your list with real people
Your own view is biased in both directions, so get outside input.
- Ask two or three former colleagues: “What would you say I am best at? What did you rely on me for?” The answers often reveal skills you take for granted.
- Ask someone in the target field to read your list and say which items sound relevant and which sound off.
- Try a small task that uses the skills, such as a sample report or project plan, and see whether it feels natural.
I am moving from [old field] into [new field]. I put together a short list of skills I think carry over. Would you be willing to look at it for ten minutes and tell me what rings true and what sounds like a stretch?
If you need help finding people to ask, see networking during a career change without feeling fake.
Common mistakes
- Listing soft skills with no proof. “Team player” and “strong work ethic” are not evidence.
- Assuming the old title is the skill. Titles are not portable. Tasks are.
- Ignoring real gaps. If most postings require a tool or method you have never used, you may need to learn it first. The question of whether to upskill or reposition can help you decide how much learning to add.
- Using insider jargon. If a recruiter outside your field cannot understand a bullet, rewrite it in plain terms.
- Trying to claim everything. A focused list of five to seven skills tied to the target role is stronger than twenty loosely related ones.
A worked example
Suppose you coordinated front-desk operations at a busy clinic for six years and want to move into project coordination. Your inventory might include “scheduled 40 to 60 appointments a day across four providers,” “trained five new staff on the booking system,” and “rebuilt the check-in process after a recurring bottleneck.” Underneath are scheduling under constraints, training, and process improvement. A project coordination posting that asks for timeline management, onboarding team members, and improving workflows matches all three. The skills were already there. The work was noticing them and describing them in the new vocabulary, with evidence attached.
Keep the document alive. Add a line after each project, course, or volunteer task, and update it after each interview with the skills interviewers asked about, since those show what the employer values.
To work through it on paper, use the transferable skills worksheet.
Where this comes from
The description of ONET OnLine’s Skills Search and its task and activity listings comes from ONET’s own tool descriptions. The five-step method is a practical framework based on common career-counseling practice, not a study, and it makes no promise about outcomes. Job requirements and terminology change and vary by employer and location, so check current postings in your target field.