Why 26 Competencies, Not 26,000 Skills
Some career platforms catalog hundreds of skills. Enterprise HR systems maintain tens of thousands. Certain workforce data providers index hundreds of thousands. The result is the same: an ever-expanding taxonomy that no professional can navigate and no manager can evaluate against. We took the opposite approach.
Why only 26 competencies?
TailorCV defines 26 competencies — one per job family, each representing a domain of professional practice with a clear L1-to-L10 progression and a C-suite destination. These aren't skills. They're the professional disciplines that skills serve.
What's the difference between a skill and a competency?
A skill is a tool. A competency is how you wield it. "Terraform" is a skill. "IT Operations" is a competency. The skill changes with your employer, your stack, your decade. The competency deepens across every tour of duty in your career.
The industry has a long history of conflating terms that should be precise. Resume and CV are used interchangeably — they're not. Achievement and accomplishment are treated as synonyms — we draw a distinction. Hard skills and soft skills create a false binary that obscures what actually differentiates professionals at senior levels. And skills and competencies are collapsed into one bucket, which is why most skills taxonomies become ungovernable at scale.
We've chosen to be precise about these distinctions because precision is what makes a career framework useful — not scale.
How do competencies and skills work together?
Competencies are the parent. Skills are the children. If your organization tracks "Salesforce CPQ" as a skill, it maps to the Revenue Operations competency. If they track "Figma," that's Design & UX. We don't maintain a skills database because it would be infinitely long and perpetually stale. We maintain the 26 competency frameworks that skills roll up into.
Employers should absolutely define their own skills within these competencies — the skills reflect their specific stack, tools, and operating context. The competencies provide the north star that persists across employers, across tools, and across an entire career. Your resume lists the skills snapshot. Your career record tracks the competency arc.
What about AI skills?
"Prompt engineering" is a skill with an 18-month half-life. "AI-augmented decision making" is a competency-level capability that persists as models, interfaces, and interaction patterns evolve. Every DRS variant includes an "AI as Accelerator" section that describes how AI applies at the competency level — not which tools to use, but how AI changes the way professionals in that domain create leverage. The tools will change. The leverage compounds.
Is this framework the final word on career architecture?
No. It's our best current model — 26 competencies, 167 career areas, 1,537 Digital Role Specifications across 9 seniority levels. We've made it public because career frameworks shouldn't be locked behind enterprise contracts. We welcome feedback from practitioners, HR leaders, and researchers. If your organization defines competencies differently, we want to hear why. The goal isn't to be right — it's to be useful, and to improve in public.