When it comes to H-1B and PERM filings, one of the most overlooked — yet most critical — elements is selecting the right Standard Occupational Classification (SOC) code. Get it wrong, and you risk RFEs, wage issues, or even denials. Get it right, and you lay the groundwork for a smooth, compliant filing.
For startups and legal teams, especially those navigating hybrid tech roles and evolving job titles, SOC code selection can be tricky. Here’s how to approach it with clarity and strategy.
1. Understand What an SOC Code Represents
The SOC code system is maintained by the U.S. Department of Labor and classifies all occupations. Each code includes:
A job title
A general job description
Examples of duties
Guidance on education and experience levels
This classification helps determine the prevailing wage and whether a position qualifies for H-1B or PERM sponsorship.
Start with the official SOC website for the full list of codes and their descriptions.
2. Avoid Overly Broad or Mismatched Titles
In tech, it’s common to see titles like “Growth Hacker,” “Software Ninja,” or “Product Rockstar.” But these creative titles don’t match any SOC code. Instead, focus on core responsibilities and map those to established roles like:
15-1252: Software Developers, Applications
15-1241: Computer Network Architects
15-2041: Statisticians or Data Scientists
A good SOC match balances job duties, not just title. ILW.com offers a breakdown of H-1B-specific SOC code strategies that can be useful.
3. Match the Duties — Not Just the Title
It’s tempting to base the SOC code solely on the job title, but the DOL and USCIS focus on actual job duties. For example:
A “Machine Learning Engineer” might fall under either Data Scientist or Software Developer codes depending on the focus.
A “DevOps Engineer” could be categorized under Systems Engineers, Software Developers, or even Network Administrators.
Carefully compare your job description with the duties listed under the potential SOC code. You can also use tools like the O*NET Online system to drill down into occupational data.
4. Consider Wage Implications
Every SOC code is tied to a wage range depending on the level (1 through 4) and work location. Choosing a code with a higher base wage than budgeted can complicate your sponsorship plan.
That’s why startups should:
Compare wage levels across SOC options before deciding
Review FLC wage data for remote/hybrid worksite options
Consult a compliance expert if the role doesn’t fit cleanly into one category
Visit the FLC Data Center to preview wage data for multiple codes.
5. Document Your SOC Code Selection
Once you’ve chosen a code, document the rationale. This helps during audits or in the event of an RFE. A well-prepared justification memo can include:
Job description crosswalk with SOC duties
Comparable codes considered and rejected
Notes on education/experience alignment
TechBridge includes this as part of our standard support for all filings.
The TechBridge Approach
SOC code selection doesn’t have to be a guessing game. At TechBridge Compliance Services, we:
Analyze job descriptions and recommend best-fit codes
Compare wage levels across options
Prepare documentation to support your selection
We work with attorneys and tech leaders to reduce risk and build a compliant foundation for talent sponsorship.
Need Help Choosing the Right SOC Code?
Let’s simplify the process. Book a consult today and we’ll walk through your role, responsibilities, and wage goals to find the most strategic path forward.
