Using O*NET to Build a Competency Framework (Without Starting From Scratch)

The blank-canvas problem every new HR lead knows

You have just inherited the job of building a competency framework. Maybe it is because the engineering team hit twenty people and the founder finally admitted that "you know what good looks like" is not a performance standard. Maybe a manager pulled you aside after a skip-level and said, flatly, that her direct reports have no idea what skills would get them promoted. Maybe you are the first formal HR hire and the spreadsheet you were handed has column headers but no definitions underneath them.

Whatever the trigger, you are now sitting in front of a blank document trying to answer an almost impossible question: what, exactly, does "strong" look like for every role in this company?

Writing competency statements from scratch for even a handful of job families takes weeks. The research alone — what skills matter for a software engineer versus a customer success manager versus a finance analyst — can feel like a part-time job stacked on top of your actual job. And the stakes are not trivial: competencies that are vague, internally inconsistent, or disconnected from actual work undermine the very evaluation process they are supposed to support.

There is a faster starting point. The U.S. Department of Labor maintains a free, continuously updated database of occupational skills, knowledge areas, and work activities for nearly 1,000 occupations. It is called O*NET, and it is the most practical shortcut available to HR practitioners building an O*NET competency framework for the first time — or rebuilding one that has drifted out of shape.

This article walks you through what O*NET contains, how to read it, what to take and what to leave behind, and how to turn a raw export into competency statements your managers can actually use in a review conversation.

---

What O*NET actually is — and what it is not

ONET (the Occupational Information Network) is sponsored by the U.S. Department of Labor / Employment & Training Administration and is freely accessible at onetcenter.org. It covers nearly 1,000 occupations and is built from surveys of workers and occupational analysts — as of the most recent data, ONET has collected responses from more than 42,000 surveys across approximately 923 data-collection occupations (O*NET, 2026). The database is continuously updated as occupations evolve.

For HR purposes, the most useful parts of O*NET are its Content Model categories:

• Skills — cross-occupational abilities like active listening, critical thinking, and written comprehension, rated by importance and level for each occupation.
• Knowledge — subject-matter domains (e.g., customer service, mathematics, economics) rated similarly.
• Work Activities — what people actually do on the job, drawn from a library of more than 19,000 task statements, 2,000+ detailed work activities, 325 intermediate work activities, and 41 generalized work activities (O*NET Resource Center / USDOL-ETA, 2025).
• Abilities — more stable, underlying cognitive and physical capacities.
• Work Styles — personality-adjacent traits (persistence, attention to detail, leadership) rated by importance.
• Job Zones — ONET's preparation scale indicating the level of education, experience, and training typically associated with an occupation. (In late 2025 ONET consolidated the former Job Zones 1 and 2 into a single "Job Zone 1-2," so the current scale runs across four levels — Job Zone 1-2, 3, 4, and 5.)

What ONET does not supply is equally important to understand. ONET describes occupations as they exist in the labor market — it does not define career levels (Associate, Mid, Senior, Staff), it does not build IC versus Manager dual tracks, and it does not construct behavioral rubrics with the 1–5 scoring language your evaluators will use. Those are company-specific judgments that ONET can seed but cannot replace. When you see "O*NET-seeded templates" mentioned as a product feature, that is exactly what it means: ONET provides the raw occupational vocabulary; your company still decides what level-two versus level-four performance looks like. You can read more about that distinction in how competency models differ from full career frameworks.

This article references occupational content from O*NET, sponsored by the U.S. Department of Labor / Employment & Training Administration (onetcenter.org). O*NET data is used under CC BY 4.0.

---

How to find the right occupations for your job families

Start at onetonline.org. The search is straightforward: type a job title or a keyword and O*NET returns a list of matched occupations with similarity scores.

A few practical notes on navigating results:

Map job families, not individual job titles. If your company has a "Software Engineer" job family that spans roles from junior engineer to principal architect, you do not need a separate ONET lookup for each level. Find the best-fit occupation (ONET uses titles like "Software Developers" and "Software Quality Assurance Analysts and Testers") and use its skill profile as the baseline for the whole family. You will differentiate levels yourself through your leveling rubric, not through separate O*NET entries.

Check the Job Zone. Before committing to an occupation, look at its Job Zone. A Job Zone 4 occupation ("considerable preparation needed") typically requires a four-year degree and several years of experience. If that matches the realistic profile of mid-level hires in your job family, you are in the right neighborhood. An occupation in the lower "Job Zone 1-2" band (little to some preparation needed) would be a poor anchor for a role your company treats as professional-track.

Cross-reference two or three related occupations. For hybrid or emerging roles that do not map cleanly to one O*NET title — a "Growth Engineer" or a "Revenue Operations Manager" — pull the skill profiles for two or three adjacent occupations and look for the intersection. Skills that appear with high importance ratings across all three are almost certainly relevant; skills unique to one are candidate additions to discuss with your subject-matter experts (typically a senior practitioner in that job family).

Use the "Bright Outlook" and "Green Economy" flags selectively. These are useful labor-market signals, but they are not competency inputs. You can note them for workforce planning; ignore them when building the framework itself.

---

Reading the skill ratings — and deciding what to keep

Every O*NET skill entry comes with two numerical ratings: importance (how critical is this skill to the occupation?) and level (how much of this skill is needed?). Both are on a 0–100 scale in the underlying data, though the website displays them on a 1–5 scale with anchors.

A practical filter for framework-building: start with skills rated important or higher (roughly the top half of the importance distribution for that occupation). This typically yields eight to fifteen skills — a workable set. You are not trying to be exhaustive; you are trying to identify the skills that, if weak, would cause visible performance problems.

From that filtered set, group by theme. O*NET organizes skills into clusters — basic skills (content and process), social skills, complex problem-solving skills, technical skills, systems skills, and resource management skills. Those cluster labels give you a natural way to organize your competency framework into domains, which makes review conversations more coherent than a flat alphabetical list.

What you will almost always need to remove or adapt:

• Abilities (as distinct from skills) are usually too granular for a behavioral competency framework. "Oral Comprehension" as an O*NET ability becomes "communicates ideas clearly in spoken and written form" as a company competency statement — the translation is yours to make.
• Physical Demands and Environmental Conditions are important for certain roles (field operations, facilities) but are not competency content for most professional job families.
• Tasks are often too specific and operational for a framework — they describe what someone does, not the underlying capability. Use them as a sanity check ("does this competency actually show up in the work?") rather than as direct copy.

For a worked example of how to turn an O*NET skill descriptor into a usable behavioral competency statement, see writing competency statements that work in a review conversation.

---

Translating O*NET language into company-ready competency statements

Raw O*NET language is precise and neutral — written for labor economists and workforce analysts, not for a manager scoring a mid-year review. Before the content is usable in a framework, it needs two passes of editing.

Pass one: make it behavioral. An ONET skill descriptor like "Active Listening — giving full attention to what other people are saying, taking time to understand the points being made, asking questions as appropriate" is a good definition. A competency statement your managers can score needs behavioral indicators: what does an employee at this level visibly do or produce that demonstrates active listening? The ONET text gives you the "what"; you add the "how it shows up here."

Pass two: calibrate to your levels. The same underlying skill should read differently at level two and level four of your career ladder. At level two, a "written communication" competency might be: drafts clear emails and Slack messages with minimal revision needed. At level four, it becomes: authors proposals and technical documentation that are adopted without significant redraft; anticipates audience questions and addresses them proactively. O*NET provides one profile per occupation; the leveled differentiation is entirely your work. The career ladder templates hub has examples of level-differentiated rubrics across several job families if you want a structural reference.

A few drafting principles that apply regardless of the source material:

• One competency, one capability. If a statement requires "and" to hold together, split it.
• Avoid adverbs as the only differentiator. "Communicates clearly" versus "communicates very clearly" is not a meaningful level distinction. Behavioral evidence is.
• Test against a real case. After drafting, ask a senior practitioner in the role: "Could you point to something a specific employee did last quarter that would score a 4 on this?" If they cannot, the statement needs revision.

---

What a practical O*NET-seeded workflow looks like end to end

Here is the sequence in plain terms, from first search to a framework ready for its first evaluation cycle:

1. List your job families. Start with the five to eight families that cover the most employees or have the most active promotion conversations. You do not need to build every family before launching.
2. Find the best-fit O*NET occupation for each family. Use ONET Online's keyword search; note the ONET-SOC code for your records.
3. Export or copy the top-rated skills for each occupation. Focus on the importance-filtered set (important or above). Note which skills cluster together.
4. Draft competency domains. Group the filtered skills into three to six thematic domains per job family (e.g., Technical Execution, Communication, Collaboration, Problem Solving, Domain Knowledge). These become the headers in your framework.
5. Write behavioral indicators for each level. For each competency within each domain, draft two to four sentences describing what strong performance at each career level looks like. This is the hardest step and the one where internal subject-matter expertise is irreplaceable.
6. Validate with practitioners. Share the draft with two or three senior practitioners and one or two managers. Ask them to red-flag anything that does not reflect actual work. Expect one revision cycle.
7. Load into your evaluation system. A structured tool makes the framework operational — employees see the criteria before the review, managers score against them with evidence notes, and gaps surface automatically. Career Ladder Builder's features were built around exactly this workflow: framework definition, structured evaluation, and automated gap reporting on a scheduled cycle.

If you are early in this process and want to move quickly without staring at a blank spreadsheet, the Competency Library Starter Kit gives you 50 pre-written competency statements across five job families, drawn from O*NET occupational content and already formatted for a behavioral rubric — a faster path to step five than building from the raw database.

For a fuller treatment of the broader framework-building process, including how to set career levels and structure IC versus Manager tracks, see how to build a career ladder.

---

A note on what O*NET does not solve — and where HR judgment takes over

O*NET is an exceptionally useful starting point. It is not a substitute for the internal work that makes a framework credible to the people being evaluated against it.

The skills ONET surfaces reflect occupational norms across the U.S. labor market as a whole. Your company may weight certain capabilities differently — a customer-facing engineering team at a professional-services firm places a different emphasis on client communication than a product engineering team at a venture-backed startup, even if both map to the same ONET occupation. O*NET gives you the vocabulary; your organization's values and operating model tell you the weights.

Similarly, O*NET will not tell you how many levels your ladder should have, whether your senior individual contributors should top out at the same level as entry-level managers, or how to handle a Principal Engineer who manages no direct reports but mentors a dozen. Those are architectural decisions about your career framework — the distinction between a competency model and a career framework matters here — and they belong to your team.

"Employees who feel their organization invests in their development stay dramatically longer — and the path to that investment starts with making the criteria for growth legible." — Career Ladder Builder editorial team, synthesizing findings from LinkedIn's 2024 Workplace Learning Report and the broader career-development literature.

One final, practical note on compliance: competency frameworks anchored in observable, job-relevant behaviors — the kind O*NET helps you build — tend to be more defensible in the event of a promotion dispute or an EEOC inquiry than frameworks based on subjective managerial impression. That said, whether your specific framework design, evaluation process, or promotion criteria meet applicable legal standards in your jurisdiction is a question for qualified employment counsel, not for an article like this one.

---

Start with O*NET — then make it yours

The blank canvas is the hardest part. An O*NET competency framework gives you a research-backed, professionally curated starting vocabulary for nearly any job family in your organization — for free, with proper attribution under a CC BY 4.0 license from the U.S. Department of Labor.

The work that follows — leveling, behavioral translation, internal validation, and loading into a structured evaluation system — is real, and it is yours. But it is considerably more tractable when you are editing a solid draft rather than writing the first word.

Next steps:

• Browse the Competency Library Starter Kit for 50 pre-written, O*NET-sourced competency statements across five job families — ready to adapt and load.
• Explore Career Ladder Builder's features to see how a defined framework connects to structured evaluations, gap reports, and development action items on a scheduled cycle.
• Start a 14-day free trial to load your first job family and run a practice evaluation cycle — no per-user pricing, no headcount penalty as you grow.
• When you are ready to run your first cycle, this guide walks you through it in 30 minutes or less.

This article references occupational content from O*NET, sponsored by the U.S. Department of Labor / Employment & Training Administration (onetcenter.org). O*NET data is used under CC BY 4.0.