SOC codes: the Standard Occupational Classification, explained (2026)

A SOC code is a six-digit identifier from the Standard Occupational Classification, the US federal system for grouping every job in the economy into 867 detailed occupations. If you have ever looked up a wage statistic, filed an H-1B petition, requested a prevailing wage determination, or filled in a government workforce survey, a SOC code was doing the work underneath. It is also, quietly, the spine of the entire labor market data industry: BLS wage series, O*NET occupation profiles and most commercial analytics are keyed to it.

This page covers how the system works, the current codes for the roles people actually search for, and the honest answer to the most common question - what to do when your job title has no code of its own.

How the system works

The format is XX-YYYY. The first two digits are one of 23 major groups - 11 is management, 15 is computer and mathematical, 29 is healthcare practitioners,53 is transportation. The remaining digits narrow to a minor group, a broad occupation, and finally the detailed occupation. So 15-1252 reads: computer and mathematical (15), software developers (1252).

The current revision is the 2018 SOC, and the revision matters: codes move. The most-searched dead code is 15-1132 (Software Developers, Applications), a 2010-SOC code that the 2018 revision merged into 15-1252. Documents and tutorials citing 15-1132 are using a code that no longer exists. One more trap for international readers: the UK has its own, entirely different SOC (ONS SOC 2020) used for Skilled Worker visa eligibility - a UK SOC code and a US SOC code share nothing but the acronym.

SOC codes for common tech roles

The roles with no code of their own

Half the searches that land on a page like this are for titles the SOC does not contain, because the taxonomy revises roughly once a decade and job titles do not. The honest mappings employers and attorneys actually use:

Data engineer has no dedicated code; filings typically use 15-1252 (software developers) or 15-1243 (database architects), depending on where the role leans. Data analyst likewise: 15-2051 (data scientists) for statistical work, 13-1161 (market research analysts) for business-facing work. DevOps engineer splits between 15-1252 and 15-1244. Product manager is the messiest of all - commonly filed under 13-1082 (project management specialists) or 11-2021 (marketing managers), neither of which describes the job. The choice is not cosmetic: in immigration filings the code sets the prevailing wage, so the mapping is worth getting right with counsel rather than a blog post - this one included.

This decade-scale lag is the structural weakness of every official taxonomy, and it is why posting-level data matters: job postings show what employers call the work now. Our job title hierarchy reference covers the seniority axis the SOC ignores entirely.

Where SOC codes show up in data work

Three places, if you build with labor market data. BLS wage statistics (the OEWS series) publish medians and percentiles per SOC per metro - the free baseline every salary product benchmarks against. O*NET extends each SOC code with skills, tasks and technologies, using an O*NET-SOC variant that adds a decimal suffix (15-1252.00) for finer splits. And classifiers in every commercial pipeline map raw postings to SOC so they can join against those official series - the approaches and vendors are covered in labor market data sources.

That last join is where the work is. A posting titled “Platform Wizard” or “Growth Ninja” carries no SOC code; someone has to infer it from the title and description. If you are building that pipeline, the input that decides your accuracy is clean, current, deduplicated postings - which is the layer a jobs API supplies.