Skill-to-competency mapping
Skill-to-Competency Mapping
Learn how to convert the raw skills listed in a job description into clear, measurable competencies, and map each one to real evidence so your interview preparation becomes precise and powerful.
Introduction
A job description gives you a list of skills. But a list of skills, on its own, is not a preparation plan. To prepare effectively, you need to convert those skills into competencies — the observable, measurable abilities the employer will actually assess — and then connect each competency to real evidence from your experience.
This process is called skill-to-competency mapping. It is the bridge between "here is what the job wants" and "here is how I will prove I have it." Once you master it, you will never walk into an interview wondering what to prepare.
Learning Objectives
- Explain the difference between a skill and a competency.
- Convert listed job skills into measurable competencies.
- Group competencies into meaningful categories.
- Map each competency to concrete evidence from your experience.
- Build a personal competency map for any role.
Why Skill-to-Competency Mapping Matters
Interviewers rarely ask, "Do you know Python?" Instead, they ask you to solve a problem, explain your reasoning, or describe a past situation. In other words, they test the competency behind the skill, not just whether the skill appears on your résumé.
Mapping skills to competencies helps you prepare for how you will actually be assessed. It reveals exactly which examples to prepare and exposes gaps before the interviewer does.
Skill vs Competency: The Key Difference
People often use "skill" and "competency" interchangeably, but they are different. A skill is a specific ability. A competency is the broader, observable capability to apply that skill effectively in real situations.
| Aspect | Skill | Competency |
|---|---|---|
| Definition | A specific learned ability. | The proven ability to apply skills effectively. |
| Focus | What you can do. | How well you do it in practice. |
| Example | Knowing SQL. | Solving a real data problem using SQL. |
| How It's Tested | Presence on a résumé. | Behaviour, examples, and problem-solving. |
| Scope | Narrow and specific. | Broader and behavioural. |
Think of Driving
Knowing how to change gears is a skill. Safely driving through busy traffic to reach your destination is a competency. An employer wants to know you can complete the journey, not just operate the controls.
Types of Competencies
When mapping, it helps to group competencies into categories. Most roles require a mix of the three types below.
Technical Competencies
Role-specific, job-related abilities.
These come from technical skills: programming, databases, tools, analysis, or domain knowledge. Example: "Can design and query a relational database."
Behavioural Competencies
How you work with others and handle situations.
These include teamwork, communication, adaptability, and problem-solving. Example: "Can resolve a disagreement within a team constructively."
Foundational Competencies
Broad qualities that support everything else.
These include learning agility, work ethic, and reliability. Example: "Can quickly learn a new tool and apply it to a task."
How to Map Skills to Competencies
Follow this repeatable process to turn any list of job skills into a personal competency map.
List the Skills from the JD
Extract every skill and requirement from the job description.
Convert Each Skill Into a Competency
Rewrite each skill as an observable ability. Ask, "What would someone do to prove this skill?"
Group Related Competencies
Cluster them into technical, behavioural, and foundational categories to see the full picture.
Map Evidence to Each Competency
For every competency, attach a project, task, or experience that proves you have it.
Identify and Close Gaps
Any competency with no evidence is a gap. Prepare an example, learn the basics, or plan how you will address it.
Worked Example: Mapping a Software Role
Suppose a job description lists these skills:
Here is the completed skill-to-competency map:
| Skill (from JD) | Competency (Observable Ability) | Your Evidence |
|---|---|---|
| Programming language | Can write and debug working code. | Final-year project built in Java. |
| Databases | Can design tables and query data. | Designed the database for an attendance system. |
| Teamwork | Can collaborate and resolve conflict. | Coordinated testing across a 4-person team. |
| Willingness to learn | Can quickly pick up new tools. | Self-learned Git for the project in one week. |
What to Do About Gaps
Every honest map reveals gaps — competencies where you have little or no evidence. Gaps are not failures; they are a to-do list.
Weak Response to a Gap
- Ignoring it and hoping it won't come up.
- Pretending to have experience you don't.
- Panicking and giving up on the role.
Strong Response to a Gap
- Build a small example or mini-project.
- Learn the fundamentals before the interview.
- Honestly show related experience and eagerness to learn.
Best Practices for Competency Mapping
- Rewrite every skill as an action you can demonstrate.
- Attach at least one real example to each competency.
- Group competencies into technical, behavioural, and foundational.
- Prepare your evidence using the STAR structure.
- Treat every gap as a preparation task, not a dead end.
- Reuse your map to tailor your résumé keywords.
Common Mistakes
Avoid These
- Listing skills without defining the ability behind them.
- Preparing skills but not examples.
- Ignoring behavioural competencies.
- Leaving gaps unaddressed.
- Using one generic example for everything.
Do These Instead
- Turn each skill into an observable competency.
- Map a specific example to each one.
- Cover technical and behavioural competencies.
- Plan how to close every gap.
- Prepare distinct, relevant examples.
Real-World Use Cases
Fresher Interview Prep
A student maps every JD skill to a competency and a project, walking into the interview with a ready example for each likely question.
Résumé Tailoring
The map reveals which competencies to feature, so the candidate highlights the matching evidence at the top of the résumé.
Spotting Weak Areas Early
A candidate discovers they have no evidence for "teamwork," so they prepare a group-project example before the interview.
Frequently Asked Questions
What is the difference between a skill and a competency?
A skill is a specific ability, such as knowing SQL. A competency is the proven ability to apply that skill effectively, such as solving a real data problem with SQL.
Why not just prepare the skills directly?
Because interviews test how well you apply skills, not just whether you have them. Mapping to competencies prepares you for the way you will actually be assessed.
What if I have a gap with no evidence?
Treat it as a task. Build a small example, learn the fundamentals, or honestly show related experience and your willingness to learn.
How many competencies should I map for one role?
Focus on the most important ones, usually five to seven. This keeps your preparation targeted on what the interview is most likely to test.
Can I reuse a competency map for other jobs?
Partly. Your evidence stays the same, but you should re-map for each role because different jobs prioritize different competencies.
Conclusion
Skill-to-competency mapping transforms a plain list of job requirements into a focused, evidence-based preparation plan. By converting each skill into an observable competency and attaching real examples, you prepare for how interviews actually work — through problem-solving, behaviour, and demonstrated ability.
The map also exposes your gaps early, while you still have time to close them. Build one for every role you pursue, and you will walk into each interview knowing exactly what will be tested and exactly how you will prove it.
Key Takeaways
A skill is what you can do; a competency is how well you apply it. Convert each JD skill into an observable competency, map it to real evidence, group them into technical, behavioural, and foundational types, and turn every gap into a preparation task.