SOC Code Lookup by Job Title: A Practical Guide

Why the SOC Code You Pick Changes the Wage Number You Get

A claimant's resume says "office coordinator." You run a labor market survey, pull a median wage, and build a wage-earning-capacity range around it. Opposing counsel's vocational expert pulls a different median wage for what looks like the same job — because they classified it under a different Standard Occupational Classification (SOC) code. Now two reports built on the same resume disagree by several thousand dollars a year, and the disagreement traces back to one decision made early and quietly: which SOC code the title actually maps to.

This happens constantly with generic titles — "coordinator," "specialist," "associate," "technician" — that could plausibly sit under three or four different SOC codes depending on the actual duties performed. The wage data downstream is only as reliable as the classification upstream. Get the SOC code wrong and every median wage, every percentile, every wage-earning-capacity calculation built on top of it inherits the error.

This guide walks through a repeatable workflow for looking up a SOC code from a job title, resolving the near-matches that cause the most disputes, and connecting the confirmed code to usable wage data — so the classification step holds up if someone checks your work.

The SOC System, Briefly: What You're Actually Looking Up

The Standard Occupational Classification system is the official U.S. federal statistical standard used to classify workers into occupational categories. Every SOC code corresponds to a defined occupation with a title and a scope description — not a job title as written on a resume, but a category of work with consistent duties across employers. That distinction matters: "office coordinator" is a resume title; the SOC code you're looking for describes the actual bundle of tasks behind that title, which might land under general office clerks, executive secretaries and administrative assistants, or something more specific depending on what the person actually did.

ONET — the primary source of occupational information built on the SOC taxonomy — currently covers 900 occupation profiles representing over 55,000 individual jobs, each with detailed task, skill, and requirement data tied to a SOC code (National Center for ONET Development, USDOL/ETA, 2025; ONET content used under CC BY 4.0, ONET is a trademark of USDOL/ETA). That breadth is useful and a trap in equal measure: with 900 profiles to choose from, more than one will look plausible for a vague title, which is exactly why a structured lookup process matters more than a quick guess.

A Step-by-Step SOC Code Lookup by Job Title

1. Start from actual duties, not the title on the resume or job posting. Pull the specific tasks the worker performed — from a job description, an employer statement, or the claimant's own account — before you search. A title tells you almost nothing on its own.

2. Search O*NET OnLine by keyword, not by exact title. O*NET's occupation search matches on task and skill content, not just title strings, so searching the duties themselves ("scheduled patient appointments," "reconciled accounts payable") often surfaces a better match than searching the job title verbatim.

3. Read the occupation summary against your source material, task by task. Don't stop at the title match — open the profile and compare its task list to what the worker actually did. A title that matches perfectly but a task list that matches poorly is the wrong code.

4. If your source document uses a DOT title instead of a modern job title, route through a DOT-to-O*NET/SOC crosswalk rather than guessing at a modern equivalent. Older case files, historical vocational reports, and some fee-schedule documentation still reference Dictionary of Occupational Titles codes, and the mapping from DOT to the current SOC structure isn't always a clean one-to-one; see our full explainer on how that crosswalk works before treating a DOT title as automatically equivalent to one modern SOC code.

5. Confirm the SOC code, not just the O*NET occupation code. O*NET occupation codes map to SOC codes but display extra digits; the wage data you need downstream is published at the SOC level, so confirm you have the SOC code itself before moving to wage lookup.

Resolving Near-Matches and Ambiguous Titles

Most classification disputes don't come from obviously wrong codes — they come from two or three codes that all look defensible. A few patterns show up repeatedly:

• Supervisory scope is unclear. "Team lead" or "senior associate" titles often sit at the boundary between a first-line-supervisor code and the underlying worker code. Resolve it by checking whether the person had authority to hire, discipline, or set schedules — not just seniority in title.
• Industry-specific titles hide a generic function. A "patient access representative" and a "customer service representative" may perform nearly identical tasks under different industry labels. If the task list overlaps heavily, the generic code is often the more defensible choice unless industry-specific duties are documented.
• Blended roles split across two codes. Some jobs genuinely combine two occupations — an office manager who also does bookkeeping, for instance. When duties split roughly evenly, document both candidate codes and the reasoning for the one you selected, rather than picking silently and leaving no trail.

In every ambiguous case, the fix is the same: go back to the documented task list, not the title, and write down why the chosen code fits better than the runner-up. That written reasoning is what survives a challenge later.

From SOC Code to Wage Data: Closing the Loop

Once the SOC code is confirmed, the wage lookup itself is mechanical — but it's worth understanding what's behind the numbers. The Bureau of Labor Statistics' Occupational Employment and Wage Statistics (OEWS) program publishes wage estimates by SOC code, built from a probability sample of roughly 1.1 million establishments surveyed in semiannual panels of about 186,000 to 189,000 each (BLS OEWS Technical Note, 2024/2025). That sample size is part of why OEWS wage data is treated as a credible baseline in vocational and wage-earning-capacity work — it isn't a handful of job postings, it's a large, ongoing federal survey.

From the confirmed SOC code, the next steps are to pull BLS OEWS wage data for that code and, where the analysis calls for it, narrow the wage estimate to a specific geography rather than relying on the national figure alone — OEWS publishes wage data at national, state, and metropolitan-area levels, and local labor market conditions can differ meaningfully from the national median. A SOC code confirmed against the wrong duties, or a wage pulled at the wrong geographic level, produces a wage-earning-capacity figure that's technically sourced but practically wrong.

Documenting the Lookup So It Holds Up

A SOC code lookup that isn't documented is a lookup that can't be defended. At minimum, keep a record of: the source task list you classified against, the candidate codes you considered, the one you selected and why, and the O*NET or crosswalk version you used, since occupational classifications are periodically revised. This is estimating and case-organizing work, not a certified opinion — the credentialed practitioner's judgment in resolving the near-matches is what makes the final classification defensible, not the lookup tool alone.

If you're running this workflow regularly across a caseload, a structured worksheet saves the re-keying that causes errors in the first place. The Wage-Earning-Capacity Calculator Workbook gives you a template to carry the confirmed SOC code straight through to a documented wage-earning-capacity range, with the classification reasoning captured alongside the math instead of living in a separate note you might not find again six months later. Download the template and build the habit into your next file.