Skills & career paths
How to Do a Skills Gap Analysis for the Role You Want
6 min read
A skills gap analysis is a simple idea: compare what a role asks for with what you can actually do today, and write down the difference. Done well, it turns a vague feeling of "I'm not ready" or "I'm probably fine" into a short, specific list you can act on. This guide walks through how to assess your skills for a target role, in any field, without guessing.
What a skills gap analysis actually is
Companies run skills gap analyses across teams. You can run one for yourself, and it is simpler. You need three things:
- A clear target role.
- A list of what that role really requires.
- An honest read of where you stand against each item.
The output is not a score to feel good or bad about. It is a ranked list of what is missing, what is partly there, and what you already have and should be showing off.
This works whether you want a promotion, a move into a different function, or a step into a new industry. The method is the same. Only the target changes.
Step 1: Define the role you want, precisely
"Marketing" or "operations" is too wide to measure against. Narrow it to a title and a level, such as a senior financial analyst, an entry-level HR generalist or a mid-level project manager. Seniority matters because the same title asks for different things at different levels. Junior roles ask for execution. Senior roles add judgment, ownership and influence.
If you are torn between two roles, run the analysis twice. Comparing the two lists often tells you which move is closer and which is a longer climb.
Step 2: Build the requirements list from real sources
Do not build the list from memory or from a job title alone. Gather evidence of what the role really asks for:
- Collect several current postings for the exact role and level. Pick ones from different employers so you see the pattern, not one company's wish list.
- Highlight what repeats. Skills, tools, methods and responsibilities that appear in most postings are your core requirements.
- Separate the must-haves from the nice-to-haves. Phrases like "required" and "must have" signal the first group. "Preferred" and "a plus" signal the second.
- Note any credentials. Some fields require a certification or license to practice. Others only mention one as a bonus. Be clear which is which in your field and region.
- Group the items into themes, such as technical skills, tools, domain knowledge, and working-style skills like stakeholder management.
If you can, ask someone already in the role what a normal week involves. Postings describe the ideal. People describe the job.
For a worked example of what this looks like in one field, see the revenue operations career path, which breaks a role into what to learn first.
Step 3: Assess your skills honestly
This is where most self-assessments go wrong. People rate themselves on effort, or on exposure, instead of ability. Use a stricter test. For each requirement, answer with evidence:
