O*NET is the single most useful free resource in US workforce data, and it's underused by most HR teams. The database, funded by the Department of Labor and maintained by the O*NET Consortium, contains structured data on nearly 1,000 occupations: the tasks performed, the skills and knowledge required, the education and training typical for entry, the work activities and context, and related occupations. When a recruiter is drafting a job description, a compensation analyst is benchmarking a role, or a workforce planner is mapping transferable skills across an organization, O*NET is the starting point that replaces hours of primary research with a five-minute lookup.
What O*NET Actually Contains Every occupation in O*NET gets a six-digit code and a structured profile covering more than 250 descriptors. The profile starts with tasks (specific activities the worker performs), then builds out through skills, knowledge, abilities, work activities, work context, work styles, tools and technology, and education and training requirements. The database also includes data on wages (pulled from BLS), projected growth, and related occupations.
Each descriptor is rated on frequency and importance based on surveys of people actually performing the job. That's what separates O*NET from a static job glossary: the data reflects what workers do now, not what the role looked like two decades ago when someone wrote the original definition.
How HR Teams Use O*NET in Practice Four use cases cover most of the HR application. Job description drafting: starting from the O*NET profile for the occupation that best matches the role, then tailoring the specific tasks and requirements to the company's needs. Job leveling and evaluation: comparing the task complexity and required knowledge in the O*NET profile against similar internal roles to validate leveling decisions. Career pathing: using the 'related occupations' feature to identify lateral moves and natural career progressions for current employees. Workforce planning: mapping the skills in the O*NET profiles against the skills present in the current workforce to identify gaps and training needs.
How Often Is O*NET Updated? The database is updated annually, with a rolling schedule across occupations. A subset of occupations gets re-surveyed each year, so individual profiles can reflect data gathered within the last 12 to 24 months, while others may reflect the previous cycle's data. New occupations are added as the labor market evolves, and obsolete ones are consolidated or retired.
Where O*NET Fits (and Doesn't) in Compensation Work For compensation, O*NET is useful for anchoring the occupation definition but not sufficient for market pricing. The BLS wage data in O*NET is national-median level and doesn't reflect the local market, company size, or industry premium that drives compensation benchmarking. Most compensation teams pair O*NET with a compensation survey (Mercer, Radford, WTW, Payscale) for the pricing work. O*NET defines the role; the survey sets the price.
Getting the Most Out of O*NET for Workforce Planning Four practices separate teams that get real value from O*NET from teams that reference it once and forget it. Start every job description redraft from the current O*NET profile rather than the previous internal version, which imports any drift that's accumulated. Use the skills and knowledge descriptors to standardize the language across related roles so internal mobility moves become cleaner. Build the O*NET codes into the HRIS so reporting can roll up to standardized occupation categories. And cross-reference the BLS projected growth and wage data to inform longer-term workforce planning decisions. The official starting point is onetonline.org , with supporting Bureau of Labor Statistics context at bls.gov/ooh . Pair O*NET work with clear compensation benchmarks so the job description ties to the pay band, and use it during onboarding conversations to orient new hires to the actual scope of their role.
.svg)
.svg)
