How to Identify Your Transferable Skills (When You Don't Know What Else You Can Do)

You've probably hit this wall. You want to change jobs or change careers, and someone tells you to "identify your transferable skills." You nod, go home, sit at your laptop, and draw a blank. You're an area manager. A teaching assistant. A project coordinator. A chef. What are your transferable skills? Communication? Teamwork? Organisation?

This post is about getting past the generic list and finding the real competencies you carry from job to job. The ones that make a hiring manager think this person can do the work.

What Transferable Skills Actually Are

A transferable skill is a competence you've built in one context that applies in another. The key word is competence. Not a vague trait, not a personality adjective, but an actual ability to do a type of work.

Here's the difference. "Good communication" is a trait. "Can write a project status report that three senior stakeholders sign off without amendments" is a competence. "Teamwork" is a trait. "Can coordinate six people across two time zones to hit a deadline when two of them don't get on" is a competence.

• Stakeholder management: you can keep multiple parties with competing interests informed, aligned, and reasonably happy. This isn't "being good with people." It's project diplomacy. If you've managed a client who wanted things faster while your team wanted more time, that's stakeholder management.
• Operational leadership: you can run a process or a team day-to-day, not just in principle but in the messy reality where people call in sick, systems break, and budgets get cut mid-quarter.
• Data interpretation: you can look at a spreadsheet or a dashboard and extract a decision from it. Not "data analysis" in the sense of knowing Python. The ability to read numbers and say this is going wrong and here's where.
• Process improvement: you've spotted something inefficient and changed it. Whether that's reorganising a stockroom or rewriting an onboarding checklist.
• Crisis management: you can function when things go badly wrong. Not panic, not freeze. Prioritise, act, communicate, recover.
• Cross-functional coordination: you can work across departments that don't naturally talk to each other, translating between them and keeping things moving.

Notice what these have in common. They're all things you did, not things you are. And they all transfer. A retail manager who's handled crisis management during a Christmas rush has a skill that applies in a startup that's just lost its biggest client. A teacher who's coordinated with parents, social workers, and exam boards has a skill that applies in project management.

The problem is that most people never label what they've done in these terms. They label it by job title. And job titles hide competencies.

Why You're Probably Underestimating Yourself

Here's something we see constantly at Forte. People upload a CV that's genuinely impressive, and when we ask them what their strengths are, they say, "I don't really have any special skills. I just did my job."

This isn't false modesty. It's a real cognitive blind spot. Psychologists call it the "curse of knowledge," though it works in reverse here. You're so close to your own work that you can't see it the way an outsider does.

The thing that makes you good at your job, the thing that took you years to learn, is now something you do without thinking. You don't frame it as a skill because it doesn't feel like one. It feels like Tuesday.

A friend of mine spent eight years running a pub. When she decided to change careers, she said she had no transferable skills. "I just ran a pub." When we broke down what "running a pub" actually involved, she'd been doing supplier negotiation, staff scheduling for 15 people, cash handling and reconciliation, inventory management, customer complaint resolution under pressure, and health and safety compliance. She'd also rebuilt the rotas from scratch when she took over, cutting labour costs by 12% without losing service quality.

None of that appeared on her CV. Her CV said, "Pub Manager. Responsible for running the pub."

The point isn't that pub management is impressive in the abstract. The competencies buried inside it, supplier negotiation, cost reduction, staff management, compliance, are things employers in completely different industries need. But you have to dig them out.

Three Methods to Identify Your Transferable Skills

Method 1: Reverse Engineer What You Actually Did

Forget your job title for a moment. Job titles are containers. What matters is what was inside the container.

Take a piece of paper. Write down the last five things you did at work that required effort. Not the routine stuff. The things where you had to think, solve a problem, or make something happen.

For each one, ask: What was the situation? What did I actually do to handle it? What was the result?

Here's how this works in practice. Say you were a receptionist at a GP surgery. One of the five things you write down is: a patient became aggressive at the front desk when told there were no appointments. You calmed them down, found an emergency slot by calling another surgery, and documented the incident for the practice manager.

What's the transferable skill there? It's not "receptionist skills." It's de-escalation under pressure, problem-solving within constraints, and incident documentation. Those apply in customer service, housing officer roles, hospital administration, social work support, and plenty of others.

Do this for all five. You'll start seeing patterns. Maybe three of your examples involve sorting out problems between other people. That's stakeholder management and conflict resolution. Maybe three involve taking something messy and making it orderly. That's process improvement and systems thinking.

The patterns are your transferable skills. Not guessed, not copied from a list. Extracted from what you actually did.

Method 2: Ask Someone Else

Other people can see your competencies more clearly than you can. This isn't a self-help platitude. It's how 360-degree feedback works in corporate environments, and it works because we genuinely cannot see ourselves from the outside.

Pick three people who've worked with you closely. A colleague, a manager if you have one, a customer or client if you deal with them directly. Ask them: "If you had to describe what I'm good at to someone who was thinking of hiring me, what would you say?"

Don't prompt them. Don't give them a list. Just listen and write it down.

You'll notice something. They won't say "communication" or "teamwork." They'll say things like, "You're the person who always knows where the money went," or "You're the one we send to the difficult clients because you don't get rattled," or "You reorganised the whole filing system and now nobody can find anything because you're not there."

Those are competencies. Financial tracking. Client relationship management under difficult conditions. Systems design and implementation. Each one is a real skill you might not have claimed because you were too busy doing it to label it.

Method 3: Notice What Comes Easily to You

This one sounds simple but it's surprisingly effective. The things you're good at are often the things you find easy. And because you find them easy, you assume everyone else does too.

They don't.

If you can walk into a meeting with three arguing departments and come out with an agreed action plan, and you think that's just "basic meeting facilitation," you're wrong. Half the working population cannot do that. They avoid those meetings, or they sit through them and nothing gets decided.

If you can take a 200-line spreadsheet and spot the error in three minutes, and you think that's just "being okay at Excel," you're underestimating yourself. That's data validation and error detection. It matters in finance, operations, quality assurance, and research.

Make a list of things at work that you find easy. Then ask: would someone with no experience in my role find this easy? If the answer is no, it's a skill. The gap between "this is easy for me" and "this is hard for most people" is where your real competencies live.

Technical Skills vs Transferable Competencies

There's a distinction worth getting clear on. Technical skills are the specific tools and methods you know. Excel, Salesforce, Python, forklift operation, patient triage protocols. They're tied to particular jobs or industries.

Transferable competencies are the underlying abilities that let you use those tools effectively. Problem-solving. Prioritisation. Analytical thinking. Cross-team coordination. Decision-making under pressure.

Here's why this matters for your job search. Technical skills get obsolete. The software you learned in 2018 has been replaced. The procedure you were trained on has been updated. But the competency underneath, the ability to learn a new system quickly, to follow a procedure accurately, to adapt when the procedure changes, that persists.

Employers are increasingly aware of this. A 2023 World Economic Forum report found that 44% of workers' core skills would change within five years, and the skills rising fastest were analytical thinking, creative thinking, and resilience. Not specific software packages. Not job titles. Competencies.

This is why a hiring manager looking at two candidates, one with five years of experience in their exact software stack and one with three years in a different stack but clear evidence of fast learning and problem-solving, will often pick the second. The first candidate's skills are a perfect match today. The second candidate's competencies are a match for today and whatever comes next.

When you're identifying your transferable skills, focus on the competencies, not the tools. "I know Salesforce" is a technical skill. "I can learn a CRM system in two weeks and train others on it" is a competency. One ties you to a platform. The other goes anywhere.

How to Put Transferable Skills on Your CV Without Buzzwords

This is where most people stumble. They've identified their skills, but when they write the CV, it comes out as generic mush. "Excellent communication skills." "Strong team player." "Organised and detail-oriented."

These phrases are noise. A hiring manager reading 80 CVs has seen "excellent communication skills" on 70 of them.

The fix is to replace adjectives with evidence. Every transferable skill you claim should come with a concrete example showing how you used it.

Instead of "strong communication skills," write: "Wrote monthly reports for the board of trustees, summarising operational performance and flagging risks. Reports were used directly in quarterly planning decisions."

Instead of "good at teamwork," write: "Coordinated a team of four staff across two offices to deliver a relocation project one week ahead of schedule."

Instead of "organised," write: "Redesigned the appointment booking system, reducing patient wait times from 12 days to 4 days on average."

See the difference. The first version is a claim. The second is a demonstration. One says you have a skill. The other shows you using it.

We've written in more detail about how to match your CV to a specific job description in our post on how to tailor your CV to a job description. The short version: identify what the employer needs, then pull the evidence from your experience that proves you can do it. Your transferable skills are the bridge between what you've done and what they're asking for.

Don't try to list every transferable skill you have. Pick the three or four that matter most for the job you're applying for, and back each one with evidence. A CV with four well-evidenced competencies is stronger than one with twelve unsubstantiated claims.

Common Mistakes That Undermine Your CV

We see the same patterns repeatedly in CVs uploaded to Forte. Here are the ones that do the most damage.

Listing "communication" with no evidence. This is the single most common mistake. "Excellent written and verbal communication" appears on a huge proportion of CVs, and it tells an employer precisely nothing. If communication is one of your transferable skills, prove it. What did you write? Who read it? What happened because of it? A CV that claims communication skills but is written poorly, or is full of vague statements, actively contradicts itself. The way you write your CV is itself evidence of your communication ability.

Using job-title thinking instead of competency thinking. This is the trap we talked about earlier. You describe your work in terms of your role rather than what you did within it. "Marketing Executive" tells someone what box you were in. "Managed a £30,000 annual budget across four campaigns, negotiating directly with three external agencies to deliver below projections" tells them what you can do. The first is a label. The second is a competency. Always write the second.

Copying skill lists from templates. If you've Googled "transferable skills examples" and pasted the results into your CV, stop. Those lists, "leadership, communication, time management, problem-solving," are generic by definition. They're designed to apply to everyone, which means they distinguish no one. Your transferable skills should come from your experience, not from a template.

Overloading with skills. A CV that claims 20 skills is less convincing than one that demonstrates 4. When you list everything, you're saying nothing is a real strength. Pick the competencies that are genuinely yours and that genuinely matter for the role. Depth beats breadth every time.

Ignoring skills from outside work. Transferable skills don't only come from paid employment. Running a community group, organising a school PTA, managing a household budget during a financial squeeze, volunteering on a helpline. All of these build real competencies. If you're early in your career or returning to work after a break, this matters. Don't discount what you've done outside of a job title.

A Quick Summary Before You Start

If you take one thing from this post, take this. Your transferable skills are not a list you find on the internet. They're the competencies buried in what you've already done. Your job is to dig them out, name them accurately, and back them with evidence.

Use the reverse engineer method to find them. Ask people who've worked with you to name them. Pay attention to what you find easy that others find hard. Then write them on your CV as demonstrated abilities, not as adjectives.

This is genuinely difficult to do alone. Not because you lack skills, but because you're too close to your own work to see it clearly. Everyone is. The area manager who thinks they "just did retail" is sitting on stakeholder management, operational leadership, and data interpretation skills they haven't recognised. The teaching assistant who thinks they "just helped the teacher" has behavioural management, individualised communication, and safeguarding competencies that apply in half a dozen other fields.

Let Forte Do the Hard Part

If you're struggling to identify your transferable skills, that's the problem Forte was built to solve. Upload your CV, and our AI doesn't just scan for keywords. It extracts the real competencies underneath your experience, the ones you've been too close to see.

It works the same way a good recruiter does when they read between the lines of your CV, but faster. It identifies what you can actually do, asks you questions to surface strengths you might have missed, and then matches you to live jobs where those competencies are what the employer needs.

You can read more about how this works in our post on AI competency extraction. And when you're ready to put those skills to work in tailored applications, our guide on tailoring your CV to a job description walks you through the next step.

Upload your CV at myforte.online and find out what you're actually good at. It costs $15 per search, one-off, no subscription. No recurring fees, no lock-in. Just a clear picture of your competencies and where they fit.

You might be surprised by what you've been sitting on.