Data source

Data from U.S. Department of Labor, O*NET Center, delivered clean.

3 datasets pulled from U.S. Department of Labor, O*NET Center's releases, checked field by field and shipped the way you want them — daily, weekly, or hourly, your call.

  • 3 datasets
  • 1 industry
  • Real rows on request

What Datadory delivers from U.S. Department of Labor, O*NET Center

3
Human Resource & Employment Services United States - the O*NET-SOC taxonomy spans… · Current edition O*NET 30.3

O*NET Database (downloadable)

Human Resource & Employment Services United States: nation · Annual estimates with a May reference date

BLS Occupational Employment and Wage Statistics (OEWS)

Human Resource Employment Services Worldwide (all U.S. federal vacancies · Currently open announcements plus a historica…

USAJOBS API Data

Pick a catch, see the rows.

Name any U.S. Department of Labor, O*NET Center dataset and we send real rows from it — not a screenshot of rows. 1,744 datasets. Pick your catch.

Get a sample

API, files, or your warehouse. Daily, weekly, or hourly.

Straight answers about U.S. Department of Labor, O*NET Center data

How many occupations does the O*NET Database describe?

Roughly 1,016 occupations sit in the Occupation Data file of the current edition, coded to the O*NET-SOC taxonomy that spans the entire U.S. economy. Each carries a code, a title and a summary description, and that same code reappears as the join key in every other file - tasks, ratings, abilities, interests and job zones.

What do the rating counts look like in practice?

Large enough to model on and granular enough to trust: 297,676 Work Context ratings, 161,559 Task Ratings, 92,976 Abilities descriptors, 59,004 Knowledge elements and 37,422 Work Styles, beside 18,796 task statements and 57,543 job-title records. Each rating carries its scale, value, and where published a sample size and standard error.

Can one O*NET-SOC code pull a whole occupational profile together?

Yes - that is the point of the key structure. One code joins the occupation's description, its task statements, every descriptor rating by element and scale, its RIASEC interest profile and its Job Zone into a single record, which is why posting matchers, wage panels and competency maps converge on these codes.

Is one edition of O*NET enough for trend work?

Not by itself. Archived editions run back to O*NET 98/2000, which makes longitudinal work possible, but the taxonomy itself is revised between editions as occupation lines merge, split and retitle. Pin your crosswalks before comparing across decades, and treat edition boundaries as part of the schema rather than noise.