What's in an O*NET Occupational Profile - and Why It Matters for Hiring Trades

The Candidate Who Made You Read the Wrong Job Description

You posted a journeyman electrician opening three weeks ago. The résumés came in, you screened a handful, and now you're sitting across from someone who does commercial switchgear work — but your foreman needed residential service calls. Both call themselves electricians. Both are right. Your job description just didn't say what your electrician does.

That gap — between a job title and an actual job — is exactly what an ONET occupational profile is built to close. If you've never pulled one up, you've been writing job descriptions from memory (or copy-pasting from Indeed), pricing offers by gut feel, and hoping the person who shows up matches the role you had in mind. This article walks you through every section of an ONET profile, shows you what to do with each one, and explains how to pair it with wage data so your next posting attracts the right candidate at the right price.

By the end, you'll have a clear map of the profile and a repeatable process for turning it into a job description and an offer — fast.

---

What O*NET Actually Is (and What It Isn't)

O*NET — the Occupational Information Network — is a free database developed by the U.S. Department of Labor, Employment and Training Administration. It currently covers 1,016 occupation titles and codes and contains more than 19,000 task statements describing what workers across those occupations actually do. Think of it as the government's authoritative answer to the question: "What does this job involve?"

Here's the important caveat: O*NET tells you what the job is. It does not tell you what to pay. For wages, you need BLS OEWS data — the two datasets are built to work together, but they live in separate places. (More on that pairing in a moment, and in our skilled trades wage benchmarking guide.)

ONET assigns every occupation a code that maps to the Standard Occupational Classification (SOC) system — the same system the BLS uses for its wage surveys. That shared backbone is what lets you pull an ONET profile and a BLS wage table for the same occupation and know they're describing the same workers. If you want to understand how those codes relate, see our breakdown of O*NET and BLS SOC codes.

---

The Six Sections of an O*NET Occupational Profile

Every O*NET profile is organized into six content domains. Here's what each one contains and what you should do with it.

1. Tasks

The Tasks section lists the specific things a worker in this occupation actually does on the job — the day-to-day activities, not the soft-skill platitudes. For an electrician (SOC 47-2111), tasks include items like installing wiring and fixtures according to specifications, testing electrical systems with testing devices, and planning layouts of electrical conduit.

What to do with it: Paste the top 8–10 tasks into a "What you'll do" section in your job description. You don't need to rewrite them — they're written in plain language already. Strip out any that don't apply to your shop, add one or two that are specific to your workflow (ServiceTitan dispatch, for example), and you're done. The result is a job description that describes your electrician's actual day, not a generic one.

2. Skills

O*NET's Skills section lists the cross-functional competencies required to do the work — things like troubleshooting, active learning, reading comprehension, and critical thinking. These are graded by importance and level, so you can see not just which skills matter but how much they matter for this occupation.

What to do with it: The importance ratings tell you where to focus your interview questions. If troubleshooting ranks near the top — and for most trade roles it does — your technical screen should ask candidates to walk you through how they diagnosed a problem, not just whether they can name the tools. Skills also give you a vocabulary for your job posting that resonates with candidates who actually do the work.

3. Knowledge

The Knowledge section describes the bodies of information a worker needs — for trades, this typically includes building and construction principles, mechanical principles, engineering and technology, and public safety. Like skills, each knowledge domain is rated for importance and level.

What to do with it: The Knowledge section is particularly useful for separating role levels. An entry-level helper and a journeyman both need mechanical knowledge — but the journeyman's knowledge level rating will be substantially higher. If you're hiring for a specific license tier, check that the O*NET knowledge ratings align with what you expect at that level, then use those domains to build your qualification requirements.

4. Abilities

Abilities are stable attributes — things like spatial orientation, manual dexterity, static strength, and near vision. They represent what a person is capable of doing, as opposed to what they've learned (knowledge) or practiced (skills).

What to do with it: Abilities are useful for two things: writing accurate physical requirements (ADA compliance teams will thank you) and thinking through where a role can and can't flex. A sheet metal worker who lacks fine motor precision isn't going to get faster with experience — that's a hiring filter, not a training gap. Be careful here: abilities are descriptors, not screening tools you can apply arbitrarily. Your HR or legal advisor should review any ability-based screening criteria for compliance with applicable employment law.

5. Work Context

Work Context is one of the most underused sections in an O*NET profile — and for trades, it's some of the most valuable. It describes the physical and social environment of the job: how much time the worker spends outdoors, at height, in confined spaces, or in contact with the public; how much decision-making autonomy the role has; what the pace of work looks like; and whether the work is typically done alone or as part of a crew.

What to do with it: Drop the relevant work context items directly into your job description under a "Work environment" heading. Candidates self-select when they know what they're walking into — and that saves you the frustration of a first-week quit because someone didn't expect to spend 60% of their time on a roof. Work context is also a useful differentiator between superficially similar roles: an HVAC installer (SOC 49-9021) and an HVAC service tech have different autonomy and social contact profiles, and those differences show up in Work Context before they show up anywhere else.

6. Job Zone

Job Zone is ONET's shorthand for how much preparation a role typically requires. The system uses five zones, running from Job Zone 1 (little or no preparation needed) to Job Zone 5 (extensive preparation, typically a graduate degree or equivalent). Most journeyman-level trade roles sit in Job Zone 3 — some preparation needed — which ONET defines as occupations requiring vocational training, an apprenticeship, or one to four years of related experience.

What to do with it: Job Zone gives you a one-line summary of the experience bar for a role, which is useful when you're sizing compensation. A Job Zone 3 electrician with a completed apprenticeship (O*NET's own example cites the typical 3–4 years of apprenticeship or several years of vocational training, often plus a licensing exam) is not the same hire as a Job Zone 2 helper. Structuring your offer ranges around Job Zone anchors — and backing those ranges up with BLS percentile data — gives you a defensible, explainable offer. For a deeper look at how Job Zones map to experience expectations and pay, see our guide to O*NET Job Zones for trades.

---

Pairing the O*NET Profile With Wage Data

An O*NET occupational profile is powerful, but it has one deliberate gap: no pay numbers. To turn a profile into an offer, you need BLS OEWS data alongside it.

Here's how the pairing works in practice. Take a journeyman electrician hire. The O*NET profile (SOC 47-2111) tells you the tasks, skills, and Job Zone. The BLS OEWS data for the same SOC code tells you that the national median wage was $62,350/year as of May 2024 (BLS, May 2024 — confirm your local rate at bls.gov/oes, because your metro may be meaningfully above or below this). Together, they let you anchor the offer: the profile tells you who you're hiring; the wage data tells you what the market pays that person.

A simple worked example: if you want to anchor a journeyman electrician offer at the national median and add a 15% spread below and above it, your band looks like this —

• Min: $62,350 × 0.85 = ~$53,000
• Midpoint: $62,350
• Max: $62,350 × 1.15 = ~$71,700

That's an illustrative model — your actual band should be anchored on your metro's OEWS figure (pull it from bls.gov/oes) and adjusted for your experience expectations and any local market pressure. The point is that the profile defines who sits in the band; the OEWS data defines where the band sits.

For a full walkthrough of band methodology, see our skilled trades wage benchmarking guide. And if you want to understand how O*NET OnLine compares to a purpose-built wage tool for this kind of workflow, we break that down in O*NET OnLine vs. a trade wage tool.

---

From Profile to Job Description: A Repeatable Process

Once you understand what an O*NET profile contains, the job description workflow becomes formulaic — in the best way.

1. Look up the SOC code for the role you're hiring. (Not sure which one applies? See our explainer on O*NET and BLS SOC codes.)
2. Pull the O*NET profile. Tasks → "What you'll do." Knowledge + Skills → "What you'll bring." Work Context → "Work environment." Job Zone → "Experience requirements."
3. Pull the OEWS wage data for your state or metro (bls.gov/oes). Set your band. Add it to the posting if your state requires pay transparency disclosure — and check with your employment counsel if you're unsure whether your state does.
4. Write your own intro paragraph. The one thing O*NET won't give you is what makes your shop worth working for — that's your paragraph to write.

If you want a head start, our Trade Job Description Pack gives you pre-built, O*NET-sourced templates for the most common specialty trade roles — electricians, plumbers, HVAC techs, welders, carpenters, and more — with the profile sections already mapped in and blank fields for your BLS wage data and company-specific details. They're designed to cut the first draft from an afternoon to about fifteen minutes.

For a broader look at what makes trade job descriptions work — and the mistakes that cause the best candidates to scroll past — see how to write trade job descriptions.

---

Stop Describing a Generic Tradesperson

The electrician who does commercial switchgear and the one who handles residential service calls both show up when you post "Electrician — Journeyman." O*NET exists so you don't have to find that out in the first week.

Every section of the profile — tasks, skills, knowledge, abilities, work context, Job Zone — gives you language that's accurate, specific, and already written. Your job is to edit it for your context, pair it with real wage data, and post something that actually describes the work. Candidates who are wrong for the role will self-select out. Candidates who are right will recognize themselves in the description.

That's a better outcome than three weeks of résumé screening, and it starts with a free government database most trade employers have never opened.

Download the Trade Job Description Pack — O*NET-mapped templates for the trades you hire most, ready to drop your BLS wage data into. Or explore our pricing plans if you want the full wage-benchmarking workflow alongside the templates.

---

This article includes information from O*NET OnLine, developed by the U.S. Department of Labor, Employment and Training Administration. O*NET is a registered trademark of the U.S. Department of Labor, Employment and Training Administration.