Career Change
The Skills That Travel With You
How to identify the skills and work activities that may carry into another occupation without overlooking knowledge, credentials, tools, and preparation gaps.
October 19, 2026 · Dr. Morgan Reed
A job title is a useful label, but it can hide much of what a person has learned to do.
Someone who says, "I have only worked in administration," may also have experience coordinating schedules, resolving exceptions, maintaining records, communicating with several groups, learning new systems, and keeping work moving under deadlines. Someone who says, "I have only worked in a kitchen," may have trained employees, monitored quality and safety, ordered supplies, estimated costs, and adjusted plans when demand changed.
Those capabilities do not disappear when the job title changes. But they do not automatically qualify someone for every occupation that uses similar skills, either.
The practical task in a career change is translation: identifying what can travel, showing credible evidence of it, and being equally clear about what still needs to be learned.
Start by separating five kinds of career evidence
People often use the word "skill" to cover everything they know, use, or have done. A more precise inventory makes comparison easier.
Transferable skills are learned capabilities that can be applied across different kinds of work. O*NET's current database includes occupation-specific ratings for transferable skills such as communication, problem solving, teamwork, monitoring, and resource management. A label like active listening can appear in many occupations, although the required level and the setting may differ.
Work activities describe broad kinds of action, such as organizing and prioritizing work, getting information, documenting information, coordinating others, or making decisions and solving problems. Activities can reveal a relationship between occupations whose titles look unrelated.
Occupation-specific tasks are more concrete. Scheduling a project meeting, interpreting an employment policy, monitoring sanitation practices, and maintaining payroll records are not interchangeable tasks. They show where a broader skill or activity is being applied.
Domain knowledge and credentials establish what a worker must understand or be authorized to do. Knowledge of employment law, construction sequencing, clinical practice, accounting rules, or food-safety requirements is not captured by saying that someone is a good communicator. A license, degree, certification, or supervised practice requirement may create a real entry boundary.
Tools and software are the systems used to perform the work. Familiarity with one product can help, but the durable capability may be underneath it: maintaining accurate records, building a schedule, analyzing a budget, or learning a new workflow. Product experience and underlying skill are related, not identical.
Keeping these categories separate prevents two common mistakes. The first is assuming that a different title means starting from zero. The second is assuming that one shared skill erases every preparation gap.
Look for verbs and responsibilities, not flattering adjectives
Words such as adaptable, strategic, organized, and collaborative can sound appealing while saying little about what actually happened. Transferable skills become more useful when attached to observable work.
Instead of writing "strong organizational skills," ask:
- What did you organize?
- How many people, deadlines, records, locations, or dependencies were involved?
- What changed because you organized it?
- What did you do when the plan broke?
- Which decisions were yours, and which required approval?
- What evidence could another person verify?
"Coordinated weekly schedules for three field teams and resolved coverage conflicts" is more informative than "excellent coordinator." "Reviewed invoices against purchase records and escalated discrepancies" is more credible than "detail oriented."
The goal is not to inflate routine work. It is to describe the work accurately enough that someone in another field can recognize the capability inside it.
One transition can contain both overlap and a substantial gap
Consider Secretaries and Administrative Assistants, Except Legal, Medical, and Executive and Project Management Specialists.
In JobShift's O*NET 31.0 records, both occupations involve activities such as working with computers, getting information, communicating with colleagues, organizing and prioritizing work, and documenting information. Administrative-assistant tasks may include establishing schedules, tracking daily work, preparing event materials, maintaining payroll information, and helping staff use office technology. Project-management tasks can include developing project plans, monitoring team performance and costs, negotiating for resources, and facilitating meetings.
That overlap provides a reasonable basis for exploration. It does not make the two roles equivalent. Project management adds responsibility for objectives, timelines, budgets, staffing, stakeholders, and delivery. The BLS preparation fields in JobShift list a high school diploma or equivalent as typical entry education for the administrative occupation and a bachelor's degree for project management specialists. Individual employers and applicants vary, but the difference is too important to hide.
The useful transition question is therefore not, "Do these jobs share organizational skills?" They do. It is, "What evidence shows that my coordination experience has expanded toward project scope, and what education, tools, or delivery responsibility would I still need?"
JobShift's reviewed path from administrative assistance to project management makes that distinction visible: overlap is a reason to investigate the path, while the gaps shape the work required to pursue it.
Context changes the meaning of a shared skill
The same skill label can describe very different levels of consequence and complexity.
Active listening matters to a human-resources specialist interviewing an applicant, a nurse gathering information from a patient, a manager responding to a service complaint, and a technician clarifying a reported equipment problem. The label travels. The knowledge, stakes, procedures, and expected response do not travel automatically with it.
Critical thinking works the same way. Identifying a scheduling conflict is not the same as diagnosing a clinical condition or evaluating a regulatory control. Experience in one setting may demonstrate a useful reasoning habit, but a target occupation can require a different evidence base and much deeper subject knowledge.
This is why a list of matching words should never become an eligibility score. O*NET ratings help compare occupations, and its related-occupation method considers what people do, what they know, and what the occupations are called. Even a strong relationship is a research signal, not a hiring promise.
Preparation deserves its own check. O*NET Job Zones group occupations by the education, experience, and training generally needed to perform the work. BLS typical-entry education provides another national occupation-level measure. Neither can decide what a particular employer will accept, but both can reveal when a proposed move requires more than rewriting a resume.
Operational experience can travel upward without becoming management by itself
The reviewed JobShift path from Chefs and Head Cooks to Food Service Managers offers a different kind of example.
Chefs and head cooks may train workers, coordinate food preparation, monitor sanitation, order supplies, inspect quality, and estimate ingredient costs. Food service managers also coordinate people and monitor standards, but their tasks can extend further into staffing, customer complaints, budgets, payroll, records, and overall service operations.
The transferable foundation is real: directing work, maintaining quality, managing supplies, and responding to changing conditions. The gap is also real: being responsible for a station or kitchen process does not necessarily demonstrate control of a full operating budget, employment decisions, customer-service policy, or regulatory administration.
A strong transition case would connect specific experience to the target responsibilities. It might show that the worker already scheduled staff, reduced waste through an inventory process, trained new employees, documented sanitation compliance, or handled vendor issues. It would also acknowledge any financial, personnel, or systems experience still missing.
That is more persuasive than claiming that "leadership" transfers in the abstract.
Build a two-column evidence map
Choose one current occupation and one occupation you want to investigate. Then make two columns: evidence I already have and gaps I need to verify.
For the first column, collect examples under these questions:
- Which tasks have I performed repeatedly?
- Which broader activities appear in both occupations?
- Where have I made decisions, handled exceptions, coordinated people, or checked quality?
- Which results can I describe truthfully and support with records, work samples, or references?
- Which tools have I used, and what underlying process did I learn through them?
For the second column, ask:
- Which target tasks have I never performed?
- What domain knowledge would I need?
- Does the work require a credential, license, degree, portfolio, or supervised experience?
- Are the same skill labels used at a higher level or with greater consequences?
- Which claims would an employer reasonably expect me to prove?
The JobShift Career Explorer can help surface shared skills, work activities, and tasks across published occupations. Its matches are intentionally transparent and should be treated as prompts for investigation. The transferable-skills guide provides a shorter companion exercise.
When you are ready to present the evidence, Resume Kicker can help with the next problem: describing real experience in language that connects to a target role without inventing qualifications.
What this means for you
You do not need to reduce your experience to your current title. Start with the work you can demonstrate. Identify the skills and activities that recur across occupations, then put them back into context: the task, the setting, the level of responsibility, and the result.
After that, examine the gaps with the same care. A missing software product may be learnable relatively quickly. Missing domain knowledge may take longer. A legal credential or license can be a firm requirement. A higher level of decision responsibility may need evidence built through projects, expanded duties, education, or an intermediate role.
A career change often begins by translating experience, not discarding it. The translation is most useful when it says both what travels and what does not travel yet.
Sources and further reading
Keep exploring the evidence
What should I verify before applying this article’s ideas to my own occupation? ↗