Every H-1B petition rests on one question: does this specific job require, as a practical matter, someone with a bachelor's degree or higher in a particular field? Not a job that would benefit from a degree. Not a job where a degree is nice to have. A job where the degree is the actual entry requirement.
If you are mid-transfer, mid-extension, or watching your employer draft a role description for your next PERM-track position, this distinction matters more than almost anything else in the file. Adjudicators do not evaluate your resume in isolation. They evaluate whether the position itself, as described, meets the legal definition of a specialty occupation.
This article walks through that definition, the criteria officers apply, and what a well-built role description looks like for a data or platform engineering position. It is general information, not legal advice — confirm your specific case with a licensed immigration attorney before relying on anything here.
The Statutory and Regulatory Definition
The starting point is INA 214(i)(1). A specialty occupation is one that requires theoretical and practical application of a body of highly specialized knowledge, and attainment of a bachelor's degree or higher in the specific specialty, or its equivalent, as a minimum requirement for entry into the occupation.
USCIS implements that statute at 8 CFR 214.2(h)(4)(ii), which defines specialty occupation in similar terms and ties it to the regulatory criteria discussed below. The core idea does not change year to year: the degree has to be the normal, baseline credential for the job — not a credential the employer happens to prefer.
The Four Regulatory Criteria
A position qualifies as a specialty occupation if it satisfies at least one of four criteria set out at 8 CFR 214.2(h)(4)(iii)(A). Meeting just one is sufficient, but strong petitions typically speak to more than one.
| Criterion | What it means in practice |
|---|---|
| Degree normally required for the position | A bachelor's or higher in a specific field is typically the minimum entry credential across the occupation, not just at this employer |
| Degree common to the industry, or the role is unusually complex or unique | Parallel positions at similar organizations require the degree, or the employer demonstrates the duties are too complex or specialized for someone without one |
| Employer normally requires a degree for this position | The company's own hiring history for this role shows a consistent pattern of requiring the degree |
| Duties so specialized and complex that the knowledge needed is usually associated with a degree | The actual day-to-day work — not the title — demands theoretical knowledge typically gained through a bachelor's-level or higher program |
Notice what is not on this list: job title, years of experience alone, or a generic statement that the role is technical. Officers look past the label to the substance.
What the 2025 H-1B Modernization Rule Clarified
DHS's H-1B modernization final rule, effective January 17, 2025, amended the regulatory text at 8 CFR 214.2(h)(4)(ii) and related provisions to resolve two recurring points of dispute.
First, it codified that the word normally, as used in the specialty occupation definition and criteria, does not mean always. A position can still qualify even if the employer can point to limited exceptions in hiring history or industry practice, as long as the degree requirement is the general norm for the role.
Second, the rule reinforced a direct-relationship standard for positions where the employer accepts a range of degree fields. If a job description lists several acceptable majors — for example, computer science, data engineering, or information systems — each of those fields must have a logical and direct connection to the actual duties of the role. USCIS cannot deny a petition solely because more than one degree field qualifies, but the employer does need to show the connection between each accepted field and the work being performed.
Because DHS rules and USCIS policy guidance are revised periodically, verify the current regulatory text at 8 CFR 214.2(h)(4) and any related USCIS Policy Manual updates before filing, or ask your attorney to confirm the version in effect for your filing date.
Why Generic Job Descriptions Draw Questions
A one-paragraph job description that says the consultant will develop and maintain software applications using modern technologies gives an officer nothing to evaluate against the four criteria. It does not show industry norms, does not show complexity, and does not show a direct line from a degree field to specific duties.
This is precisely the gap that leads to a Request for Evidence asking the employer to establish specialty occupation status. If you want the full mechanics of responding to that kind of RFE — evidence types, timing, and attorney coordination — that is covered in our dedicated RFE response article. This piece focuses on preventing the question from arising in the first place, by building the role description correctly before filing.
A Well-Documented Role: Data or Platform Engineering Example
Strong petitions do not rely on adjectives. They rely on structure. For a data engineering or platform engineering role, a well-documented position typically includes:
- A duty list broken into discrete, substantive tasks — for example, designing distributed data pipeline architecture, implementing schema evolution strategies, building fault-tolerant streaming ingestion, and optimizing query performance against petabyte-scale warehouses
- A clear statement of the percentage of time spent on each major duty category
- An explicit link between each duty and the theoretical knowledge it draws on, such as distributed systems theory, database normalization principles, or statistical modeling taught in a computer science or data science curriculum
- A statement of the minimum degree requirement and the accepted degree fields, each tied to specific duties rather than listed as a loose menu
- Evidence of industry norms — job postings from comparable employers, professional association standards, or an expert opinion letter where the role is especially novel
- Evidence of the employer's own hiring pattern for the position, if this is not the first time the role has been filled
None of this requires exaggeration. It requires precision. The goal is a description an officer with no background in your field can read and understand exactly why a degree in a specific discipline is the baseline, not a bonus.
Where This Shows Up Across Your Case
The specialty occupation analysis is not a one-time hurdle at initial filing. It resurfaces at extension, at amendment if duties or worksite change materially, and often again if the case later moves toward PERM and I-140, where the employer must again show the position's actual minimum requirements match what was represented. Keeping the role description accurate and consistent across all of these filings — rather than rewriting it loosely each time — reduces friction at every stage.
The Josh Pros LLC team works with technology consultants through exactly these transitions — H-1B transfers, extensions, amendments, and the PERM process that follows. If you want a second set of eyes on a role description before it goes into a filing, reach out at contact@joshpros.com or visit https://joshpros.com.
#SpecialtyOccupation #H1BVisa #H1BDegreeRequirement #WorkAuthorization #ImmigrationLaw #TechConsultants #H1BTransfer #ITStaffing #PERMProcess #USCIS #H1BModernizationRule #DataEngineering #PlatformEngineering #ImmigrationCompliance
This is general information, not legal advice. Immigration rules change and outcomes depend on your individual circumstances. Confirm anything that affects your case with a licensed immigration attorney.
Talk to a real recruiter, not a bot.
We'll tell you the rate, the client, and the terms before you interview. And if we're not the right fit, we'll say so.