What is a SOC code?
The Standard Occupational Classification is the US government's official taxonomy of every job. Each role has a 6-digit SOC code; labor market data, H-1B prevailing wages, and PERM filings reference it.
What a SOC code is
SOC stands for Standard Occupational Classification — the official US taxonomy of every occupation. Each job has a 6-digit SOC code (formatted as 15-1252 for Software Developers, for example). The Bureau of Labor Statistics maintains the system, and federal agencies use it for labor market data, wage surveys, immigration filings, and occupational licensing.
There are roughly 867 detailed occupations in the current (2018) SOC structure, organized into 23 major groups.
Why it exists
Before SOC, every agency tracked occupations differently. The Census Bureau counted workers one way, the Department of Labor counted them another, state agencies did their own thing. Labor market data was incoherent across sources.
SOC consolidates it. If you want to know how many software developers work in Seattle and what they earn, BLS publishes the number using SOC 15-1252. If an employer wants to file an H-1B petition, they reference the same code. If a state workforce agency publishes job projections, same code again.
The code is infrastructure that keeps government labor data consistent.
How the structure works
The 6-digit code is hierarchical:
- First 2 digits — Major group. 23 high-level categories. "15" = Computer and Mathematical.
- Next digit — Minor group. "15-1" = Computer Occupations.
- Next digit — Broad occupation. "15-12" = Computer Occupations, sub-grouped.
- Final 2 digits — Detailed occupation. "15-1252" = Software Developers specifically.
Some examples:
- 11-1021 — General and Operations Managers
- 15-1252 — Software Developers
- 15-1254 — Web Developers
- 29-1141 — Registered Nurses
- 41-3031 — Securities, Commodities, and Financial Services Sales Agents
- 43-6014 — Secretaries and Administrative Assistants
You can look up any occupation at bls.gov/soc.
Where you'll actually encounter a SOC code
Most US workers never see one. The situations where they matter:
1. H-1B and employment-based visa petitions
Every H-1B Labor Condition Application (LCA) specifies a SOC code. The Department of Labor publishes prevailing wage data by SOC code and geographic area — the employer must pay at least that prevailing wage to satisfy the H-1B requirement.
If you're being sponsored for an H-1B, your offer letter often references a SOC code, and you can look up the prevailing wage yourself to verify the offer meets the floor.
2. PERM labor certification (green card)
Same mechanism as H-1B, different purpose. The employer files a PERM certification specifying the SOC code, geographic area, and wage. The Department of Labor uses the code to determine prevailing wage.
3. Federal job postings (USAJobs)
Federal government job postings on USAJobs usually reference the OPM occupational series (a separate federal taxonomy), but many also cross-reference the SOC code for context.
4. State workforce and unemployment data
Every state labor department publishes job projections and wage data by SOC. If you're researching which occupations are growing in your state, SOC is the lens.
5. Some private job postings
Rare, but some employers — especially those that hire H-1B workers regularly — will list the SOC code in the posting to signal the classification. You'll see it more often in tech, pharma, and research roles.
SOC vs. O*NET
People confuse these. They're related but distinct:
- SOC is the classification system. 867 occupations. Used for statistics, wages, and visa filings.
- O*NET is the occupation information system. More detailed. Describes tasks, tools, skills, knowledge, and work context for each occupation. Built on top of SOC codes, but expanded to ~1,000+ occupations for finer resolution.
If you're doing labor market research, use SOC for the counts and wages. Use O*NET for the job content and skill requirements.
Finding your SOC code
Three easy ways:
- BLS Occupational Outlook Handbook (bls.gov/ooh). Search your job title; each entry lists the SOC code at the top.
- BLS wage database (bls.gov/oes). Search by occupation or by area.
- O*NET Online (onetonline.org). Search your title; O*NET codes extend SOC codes with two extra digits after a decimal.
Why it matters for job seekers (rarely, but concretely)
- H-1B and green card candidates: verify the SOC code on your LCA or PERM filing matches your actual job. Misclassification has real consequences.
- Salary research: BLS wage data by SOC is the most reliable public-sector salary benchmark. More trustworthy than Glassdoor for some occupations.
- Career research: understanding your SOC code lets you look up growth projections, related occupations, and typical entry requirements.
- Resume writing: SOC titles are formal, not marketing-speak. Don't rewrite your resume to match them. But if your job title is non-standard, knowing the SOC title helps you translate for ATS systems and recruiters.
SOC 2018 vs. earlier versions
The current system is the 2018 SOC. It replaced 2010, which replaced 2000. BLS updates the system roughly every 10 years to reflect occupational change. 2028 will be the next major revision, already in planning.
If you see an older 6-digit code (e.g., 15-1131 for Software Developers from the 2010 SOC), know that the 2018 code for the same role is 15-1252. Federal agencies are still transitioning old data to the new structure.
The bottom line
SOC codes are the US government's official job taxonomy. You'll rarely see one unless you're on an H-1B, filing for a green card, or doing labor market research. When you do see one, it has real consequences — particularly for prevailing wages. Look yours up on BLS before signing an offer that involves sponsorship.
Want us to handle the whole thing?
We build tailored résumés and cover letters, verify every posting, and deliver each application as a ready-to-send package. You click Apply — we do the prep.
See how it works →