A high school counselor in Portland, Oregon uses O*NET to guide her students. A counselor in Brussels uses ESCO. Both are counseling the same demographic—16-18 year olds exploring career options.
But they're using fundamentally different job classification systems.
When a student moves from Portland to Brussels (or vice versa), their entire career plan becomes incompatible. The job titles don't align. The skill requirements look different. The career pathways have no bridge.
This is the hidden problem with single-taxonomy career tools: they create invisible borders around career guidance.
The Taxonomy Problem
Career guidance systems depend on occupational taxonomies—standardized lists of "what jobs exist" and "how they're structured."
Two major taxonomies dominate:
O*NET (Occupational Information Network)
-
Source: US Department of Labor
-
Coverage: 1,016 occupations, primarily US-focused
-
Strength: Extraordinarily detailed job analysis (wages, education, tasks, work values, interests)
-
Weakness: US-centric wage data and career progression assumptions
-
Use: Primary system in North America, increasingly global due to data richness
ESCO (European Skills, Competences, Occupations)
-
Source: European Commission
-
Coverage: 3,039 occupations across EU and EFTA countries
-
Strength: Multilingual (published in all EU official languages), explicit skills mapping, explicit broader/narrower relationships
-
Weakness: Less granular wage data, less individual work value detail
-
Use: Mandatory for EU education and employment policy, required for Europass credentials
The Coverage Gap: Why Both Taxonomies
Here's where single-taxonomy systems fail: they create blind spots. NexPath links the two taxonomies to reduce them.
Example 1: The Missing "Data Analyst"
-
In O*NET: "Operations Research Analyst" is the closest match (but emphasizes mathematical modeling, not business intelligence)
-
In ESCO: "Business Intelligence Analyst" exists explicitly
-
Reality: These are related but different career paths with different education requirements
A student using only ONET might be steered toward operations research (mathematics-heavy) when they'd be better suited to business intelligence (SQL + Python + business acumen). The ESCO taxonomy knows this distinction; ONET doesn't structure it clearly.
Example 2: The European Apprenticeship Problem
- In O*NET: Apprenticeships barely exist (US apprenticeship numbers are tiny)
- In ESCO: Apprenticeships are explicitly classified with dual-track progression (apprenticeship → technician → professional engineer)
- Reality: In Germany, Switzerland, and Austria, apprenticeships are the primary career path—roughly 65% of secondary school graduates. An O*NET-only system would suggest these students lack viable options.
Example 3: The "Nursing" Ambiguity
-
In O*NET: Registered Nurse (RN) is one massive category
-
In ESCO: Nursing is stratified into: Auxiliary nurse, Enrolled nurse (2-3 years), Registered nurse (3-4 years), Nurse specialist, Nurse manager
-
Reality: Career progression is radically different. An 18-year-old might choose a 2-year pathway (auxiliary) vs a 4-year pathway (registered). These aren't the same job; they're career entry points.
Years of Mapping Work
NexPath's research team spent years mapping ESCO and O*NET occupations, bridging these systems comprehensively.
The result: a mapping across the ESCO occupations.
Our mapping links ESCO occupations to O*NET occupations or occupational families. Where a role has no equivalent, we leave it blank.
-
ESCO-specific: European-specific regulations (EU Regulation enforcement officer), apprenticeship-specific roles, social care roles that don't exist in US structure
-
O*NET-specific: Some US military occupational specialties, some specialized technical roles specific to US labor markets, some state-regulated professions
Why Dual-Taxonomy is Essential
For Students
-
Flexibility: Career paths work whether you're moving to Finland or California
-
Depth: Access to US wage data (O*NET) AND EU career progression (ESCO)
-
Clarity: Understand that "Data Analyst" in Europe might be different from the US version—and here's exactly how
For Counselors
-
Richer guidance: Recommend apprenticeship pathways (ESCO strength) AND detailed work values alignment (O*NET strength)
-
Wide coverage across both taxonomies
-
Cross-border guidance: Confidently advise students considering migration
For Systems
-
Global scale: Same system works in Boston and Brussels without dual infrastructure
-
Future-proof: New occupations added to either taxonomy automatically expand coverage
How NexPath Maps ESCO to O*NET
The methodology:
- Direct name matching — Where "Software Developer (O*NET)" = "Software Developer (ESCO)"
- Concept mapping — Where jobs describe the same work but use different terminology
- Hierarchy traversal — For O*NET's 1,016 roles, find the ESCO equivalent at the right seniority level
- Conflict resolution — When a mapping was ambiguous, we documented the ambiguity
What Single-Taxonomy Systems Are Missing
If you're using a career guidance tool today, ask:
- Which taxonomy does it use? If it's only O*NET or only ESCO, you have blind spots.
- What happens to unmapped occupations? Do they disappear from the system? That's a missing career path.
- Can international students use it? Or does it break when they move?
- Are apprenticeships included? If not, you're excluding 500K+ European students annually.
What's Next: Occupational Evolution
Taxonomies aren't static. New occupations emerge constantly:
- "AI Prompt Engineer" (didn't exist 3 years ago)
- "Renewable Energy Technician" (consolidating older renewable roles)
- "Data Ethicist" (emerging profession)
Single-taxonomy systems struggle to keep up because changes in one taxonomy don't automatically flow to applications built on them.
Dual-taxonomy systems create a bridge: when ESCO adds "AI Prompt Engineer," the mapping system immediately considers how it relates to O*NET's emerging roles. This creates consistency, not chaos.
The hidden problem with single-taxonomy tools: your students' career options are artificially limited by someone else's classification system.
NexPath's dual-taxonomy approach removes that ceiling.