Concepts Overview
Concepts are the building blocks of Beamery's talent intelligence. Each concept represents a standardized entity in the HR domain, enabling consistent understanding across your talent ecosystem.
What are Concepts?
Concepts are standardized representations of HR-related entities stored in Beamery's Knowledge Graph. They provide a common language for describing talent, ensuring consistency and enabling intelligent matching and analysis.
Types of Concepts
- Name
Skills- Type
- concept
- Description
Technical abilities, tools, and competencies (32,000+ concepts)
- Name
Roles- Type
- concept
- Description
Job titles and positions across industries
- Name
Industries- Type
- concept
- Description
Business sectors and verticals
- Name
Organizations- Type
- concept
- Description
Companies and employers
- Name
Organization Sizes- Type
- concept
- Description
Company size classifications
- Name
Seniority- Type
- concept
- Description
Experience levels and career stages
Concept Structure
Every concept in the Knowledge Graph includes rich metadata:
Core Attributes
- Name
id- Type
- string
- Description
Unique identifier for the concept
- Name
labels- Type
- array
- Description
Display names in multiple languages
- Name
descriptions- Type
- array
- Description
Detailed descriptions of the concept
- Name
broader_ids- Type
- array
- Description
Parent concepts in the hierarchy
- Name
narrower_ids- Type
- array
- Description
Child concepts in the hierarchy
- Name
related_ids- Type
- array
- Description
Related concepts across the graph
{
"id": "skill_python_programming",
"labels": [
{
"language": "en",
"value": "Python Programming"
},
{
"language": "es",
"value": "Programación en Python"
}
],
"descriptions": [
{
"language": "en",
"value": "Programming using Python language for software development, data science, and automation"
}
],
"broader_ids": ["skill_programming"],
"narrower_ids": ["skill_django", "skill_flask"],
"related_ids": ["skill_data_science"]
}
Concept Hierarchies
Concepts are organized in hierarchical structures that reflect real-world relationships:
Skills Hierarchy Example
Role Hierarchy Example
Multi-Language Support
Concepts support multiple languages, enabling global talent operations:
Supported Languages
- English (en) - Full coverage
- German (de) - 43% coverage
- French (fr) - 61% coverage
- Spanish (es) - 100% coverage
Language Features
- Preferred labels per language
- Alternate labels and synonyms
- Cultural variations
- Regional differences
{
"id": "skill_project_management",
"labels": [
{
"language": "en",
"value": "Project Management",
"alternates": ["PM", "Project Mgmt"]
},
{
"language": "de",
"value": "Projektmanagement",
"alternates": ["Projektleitung"]
},
{
"language": "fr",
"value": "Gestion de projet",
"alternates": ["GP", "Management de projet"]
}
]
}
Concept Operations
Lookup & Discovery
Find concepts through various methods:
- Direct lookup - Search by ID or exact label
- Fuzzy matching - Handle typos and variations
- Autocomplete - Real-time suggestions as users type
- Browsing - Explore hierarchies and relationships
Reconciliation
Map free-text to standardized concepts:
Input Examples:
- "MS Office" → Microsoft Office
- "React.js" → React
- "People Management" → Team Leadership
- "10+ years" → Senior level
Reconciliation Features:
- Synonym recognition
- Abbreviation handling
- Context awareness
- Confidence scoring
Recommendations
Get AI-powered concept suggestions:
- Skills for roles - What skills does a Software Engineer need?
- Related skills - If someone knows Python, what else might they know?
- Career progression - What roles follow from Senior Analyst?
- Industry standards - Common roles in Financial Services
Taxonomy Types
Canonical Taxonomy
Beamery's global, market-validated taxonomy:
Characteristics:
- Maintained by Beamery
- Updated quarterly
- Industry standards aligned
- Multi-language support
- Market signal driven
Benefits:
- Instant deployment
- Best practices built-in
- Cross-industry mobility
- Continuous improvement
- Global consistency
Customer Taxonomy
Organization-specific concepts:
Use Cases:
- Proprietary skills
- Internal certifications
- Custom job titles
- Company-specific tools
- Unique methodologies
Management:
- Add custom concepts
- Map to canonical
- Set access controls
- Track usage
- Maintain versions
Best Practices
Concept Usage Guidelines
- Use canonical concepts when possible for better interoperability
- Map internal terms to canonical concepts for consistency
- Leverage relationships to find related concepts
- Consider context - skills mean different things in different roles
- Update regularly - Stay current with quarterly taxonomy updates
Common Patterns
Skill Variations
{
"canonical": "JavaScript",
"variations": ["JS", "Javascript", "Java Script", "ECMAScript"],
"contexts": ["Frontend", "Backend", "Full-Stack"]
}
Role Progressions
{
"entry": "Junior Developer",
"mid": "Software Developer",
"senior": "Senior Developer",
"lead": "Lead Developer",
"management": "Engineering Manager"
}
Industry Specificity
{
"concept": "Compliance",
"industry_variants": {
"finance": "Financial Compliance",
"healthcare": "HIPAA Compliance",
"tech": "Data Privacy Compliance"
}
}
Important Considerations
- Concepts evolve - what's relevant today may change
- Context matters - same concept, different meanings
- Languages vary - not all concepts translate directly
- Custom concepts - require ongoing maintenance
- Relationships - can be industry or region specific