Skills Taxonomy
Beamery's Skills Taxonomy is a carefully curated, hierarchical classification system that brings order to the chaos of skills data. With over 32,000 preferred terms and 186,000+ variations, it provides the semantic foundation for all talent intelligence operations.
Taxonomy Structure
Our taxonomy is designed as a directed acyclic graph (DAG) where skills can have multiple relationships and contexts. This structure enables nuanced understanding beyond simple hierarchies.
Core Components
Preferred Terms
- Single canonical representation
- Language-specific preferred labels
- Consistent across the platform
- Used for standardization
Alternate Terms
- Synonyms and variations
- Abbreviations and acronyms
- Regional differences
- Legacy terminology
{
"id": "skill_react_js",
"preferred_labels": {
"en": "React",
"de": "React",
"fr": "React",
"es": "React"
},
"alternate_labels": {
"en": ["ReactJS", "React.js", "React JavaScript", "Facebook React"],
"de": ["ReactJS", "React.js"],
"fr": ["ReactJS", "React.js"],
"es": ["ReactJS", "React.js"]
},
"skill_type": "software_tool",
"created": "2015-03-01",
"last_updated": "2024-01-15"
}
Metadata Richness
Each skill in our taxonomy includes:
- Name
Unique Identifier- Type
- string
- Description
Stable ID that never changes (e.g.,
skill_python_programming)
- Name
Multi-language Labels- Type
- object
- Description
Translations across supported languages
- Name
Skill Type- Type
- enum
- Description
Behavioral, Natural Language, Product, Software Tool, or Topic
- Name
Relationship Mappings- Type
- array
- Description
Broader, narrower, and related concepts
- Name
Usage Context- Type
- object
- Description
Industries, roles, and seniority levels where skill appears
- Name
Temporal Information- Type
- object
- Description
When added, last updated, deprecation status
Skill Categories
1. Behavioral Skills
Soft skills and competencies essential for workplace success:
Leadership & Management
- Team Leadership
- Strategic Planning
- Change Management
- Stakeholder Management
- Performance Management
Communication
- Written Communication
- Verbal Communication
- Presentation Skills
- Active Listening
- Cross-cultural Communication
Problem Solving
- Critical Thinking
- Analytical Thinking
- Creative Problem Solving
- Decision Making
- Root Cause Analysis
Collaboration
- Teamwork
- Conflict Resolution
- Negotiation
- Facilitation
- Mentoring
2. Technical Skills
Hard skills related to specific tools, technologies, and methodologies:
Programming Languages
Programming
├── Object-Oriented
│ ├── Java
│ ├── C++
│ └── C#
├── Functional
│ ├── Haskell
│ ├── Scala
│ └── Clojure
└── Scripting
├── Python
├── JavaScript
└── Ruby
Data & Analytics
Data Science
├── Machine Learning
│ ├── Supervised Learning
│ ├── Deep Learning
│ └── NLP
├── Data Engineering
│ ├── ETL
│ ├── Data Pipelines
│ └── Big Data
└── Analytics
├── Business Intelligence
├── Statistical Analysis
└── Data Visualization
3. Product Skills
Commercial platforms and enterprise software:
- CRM Systems: Salesforce, HubSpot, Microsoft Dynamics
- ERP Systems: SAP, Oracle, NetSuite
- Marketing Tools: Adobe Creative Suite, Marketo, Google Analytics
- Productivity: Microsoft Office, Google Workspace, Slack
4. Natural Languages
Spoken and written languages with proficiency indicators:
{
"skill_type": "natural_language",
"language": "Spanish",
"proficiency_levels": [
"Basic",
"Conversational",
"Professional Working",
"Full Professional",
"Native/Bilingual"
],
"variants": [
"Spanish (Latin America)",
"Spanish (Spain)",
"Business Spanish"
]
}
5. Topic Skills
Broader domains of knowledge and expertise:
- Industries: Healthcare, Finance, Retail, Technology
- Functions: Marketing, Sales, Operations, HR
- Domains: Cybersecurity, Sustainability, Digital Transformation
- Methodologies: Agile, Six Sigma, Design Thinking
Hierarchies & Relationships
Broader/Narrower Concepts
Skills are organized in logical hierarchies:
Related Skills
Skills are connected through semantic relationships:
Complementary Skills
Skills that are often used together:
- React → Redux, JavaScript, CSS
- Data Analysis → SQL, Excel, Python
- Project Management → Agile, Scrum, JIRA
Progressive Skills
Skills that represent career progression:
- Junior Developer → Senior Developer → Tech Lead
- Analyst → Senior Analyst → Analytics Manager
- Individual Contributor → Team Lead → Director
Cross-Domain Mappings
Skills can belong to multiple domains:
{
"skill": "Python Programming",
"domains": [
{
"domain": "Web Development",
"frameworks": ["Django", "Flask"],
"use_case": "Backend APIs"
},
{
"domain": "Data Science",
"libraries": ["Pandas", "NumPy", "Scikit-learn"],
"use_case": "Analysis and ML"
},
{
"domain": "DevOps",
"tools": ["Ansible", "Fabric"],
"use_case": "Automation"
}
]
}
Taxonomy Management
Update Process
Our taxonomy evolves through a sophisticated process:
-
Signal Collection
- 3M+ job descriptions monthly
- Candidate profile updates
- Customer feedback
- Industry reports
-
AI Analysis
- Emerging skill detection
- Usage pattern analysis
- Semantic clustering
- Trend identification
-
Human Validation
- Knowledge engineer review
- Industry expert consultation
- Customer advisory input
- Quality assurance
-
Deployment
- Quarterly releases
- Non-breaking updates
- Version control
- Migration support
Quality Assurance
Automated Checks
- Duplicate detection
- Circular reference prevention
- Coverage analysis
- Consistency validation
Manual Review
- Semantic accuracy
- Industry relevance
- Cultural sensitivity
- Business value
Customer Extensions
Organizations can extend the taxonomy:
{
"taxonomy_type": "customer",
"customer_id": "your-company",
"custom_skills": [
{
"id": "skill_proprietary_platform",
"name": "ACME Platform",
"type": "product",
"parent": "skill_enterprise_software",
"internal_only": true
},
{
"id": "skill_company_methodology",
"name": "ACME Way",
"type": "topic",
"related_to": ["skill_agile", "skill_lean"]
}
]
}
Examples & Patterns
Common Patterns
Technology Versioning
{
"preferred": "Java",
"versions": [
"Java 8", "Java 11", "Java 17", "Java 21"
],
"pattern": "All map to preferred term"
}
Role-Specific Context
{
"skill": "Excel",
"contexts": [
{"role": "Analyst", "focus": "Pivot Tables, VBA"},
{"role": "Accountant", "focus": "Financial Modeling"},
{"role": "HR", "focus": "Data Management"}
]
}
Geographic Variations
{
"skill": "Labor Law",
"variations": [
"US Employment Law",
"UK Employment Law",
"EU Labor Regulations",
"APAC Compliance"
]
}
Industry Terminology
{
"concept": "Customer Management",
"industry_terms": {
"tech": "User Success",
"retail": "Client Services",
"healthcare": "Patient Relations",
"finance": "Wealth Management"
}
}
Best Practices
Taxonomy Usage Guidelines
- Always use preferred terms for standardization
- Include alternate terms in searches for better recall
- Consider context when interpreting skills
- Leverage relationships for comprehensive matching
- Stay current with quarterly updates
Taxonomy Considerations
- Skills can have multiple valid interpretations
- Context is crucial for accurate matching
- Not all skills fit neatly into hierarchies
- Regional and industry differences matter
- Regular updates may require remapping