E-3 Specialty Occupation: How Consuls Actually Decide

Reviewed 11 May 2026 by Kelvin Tran, attorney licensed in New York and also admitted to practice law in Australia (Supreme Court of Victoria, High Court of Australia); not licensed in California; practice limited to federal immigration law.

The most important question in any E-3 case is not whether you’re qualified for the job. It’s whether the job itself qualifies as a specialty occupation. An applicant with a perfect resumé can be refused if the offered role doesn’t meet the specialty-occupation test. A more junior applicant in a clearly qualifying role will usually sail through.

This is the part of the E-3 framework most poorly understood by applicants and even by some employers. The regulation is short. The actual analysis a consular officer performs to apply it is not. This article walks through how the test works in practice, where roles fall in the safe zone, and where the borderline cases are — particularly marketing, sales, and project-management roles, which produce a disproportionate share of E-3 refusals and Requests for Evidence.

In this article

• E-3 Specialty Occupation: How Consuls Actually Decide
  • In this article
  • The legal definition (and why it matters less than how it’s applied) {#the-definition}
  • The four-factor test: how consuls actually decide {#the-four-factor-test}
  • The role of O*NET in specialty-occupation analysis {#onet}
  • What “clearly qualifying” looks like {#clearly-qualifying}
  • The borderline cases {#borderline-cases}
    • Marketing and market research analyst roles {#marketing}
      • The Market Research Analyst saga
      • Other marketing roles
    • Sales roles {#sales}
    • Project and program management {#project-management}
    • Operations, business analyst, and “generalist” titles {#operations}
  • How to build a defensible specialty-occupation case {#how-to-build-the-case}
  • What gets your file refused {#what-gets-refused}
  • A note on how this is changing
  • Where this article ends and case-specific advice begins
    • Related reading

The legal definition (and why it matters less than how it’s applied) {#the-definition}

The statutory definition is at INA § 214(i)(1). A specialty occupation is one that requires:

(A) theoretical and practical application of a body of highly specialized knowledge, and (B) attainment of a bachelor’s or higher degree in the specific specialty (or its equivalent) as a minimum for entry into the occupation in the United States.

The implementing regulation at 8 CFR § 214.2(h)(4)(ii) restates this and adds a four-factor test that has become the operative framework. State Department guidance for E-3 cases at 9 FAM 402.9 cross-references this same regulatory framework — the E-3 specialty-occupation standard is statutorily identical to the H-1B standard, and the same body of decisional law applies.

The procedural path, however, is usually different. Most E-3 applications are decided by consular officers abroad without a prior USCIS petition, so officers apply the standard through State Department/FAM practice rather than through USCIS petition adjudication. In practice, that consular posture is often more flexible than USCIS’s historical RFE-driven process, even though the underlying legal test is the same.

The legal definition is short. Reading only the statute, you might conclude that any job calling for a bachelor’s degree qualifies. That is emphatically not how the test is applied, and it is the single most common mistake made by applicants and employers self-filing.

The four-factor test: how consuls actually decide {#the-four-factor-test}

Under 8 CFR § 214.2(h)(4)(iii)(A), a position qualifies as a specialty occupation if it meets at least one of four criteria:

1. A bachelor’s or higher degree in the specific specialty (or its equivalent) is normally the minimum requirement for entry into the particular position;
2. The degree requirement is common to the industry in parallel positions among similar organisations or, in the alternative, the position is so complex or unique that it can be performed only by an individual with a degree;
3. The employer normally requires a degree or its equivalent for the position;
4. The nature of the specific duties is so specialized and complex that knowledge required to perform the duties is usually associated with the attainment of a bachelor’s or higher degree.

The critical phrase across these four criteria — and the one that does the actual work of refusing applications — is “in the specific specialty.” A bachelor’s degree, in general, is not enough. The role must require a degree in a specific field that is reasonably related to the actual duties.

This is why an “Analyst” role described in vague terms can be refused even where the employer requires a degree. A bachelor’s degree in anything doesn’t satisfy the test. A bachelor’s degree in finance, economics, accounting, or a closely related field can — if the duties match.

The leading case interpreting this language is Royal Siam Corp. v. Chertoff, 484 F.3d 139 (1st Cir. 2007), where the First Circuit upheld USCIS’s denial of an H-1B petition for a restaurant manager. The court explained that the agency was entitled to require that the degree be “in a specific specialty” closely related to the duties:

“The mere fact that a position calls for a baccalaureate degree does not, standing alone, demonstrate that the position qualifies as a specialty occupation.”

That sentence is doing more work in E-3 adjudications than any other line of decisional law. It is the answer to “but the job ad says bachelor’s required” — yes, it does, and that alone isn’t sufficient.

The role of O*NET in specialty-occupation analysis {#onet}

Consular officers and USCIS adjudicators rely heavily on the Occupational Information Network (O*NET) — the Department of Labor’s database describing the typical educational and experiential requirements for thousands of occupations identified by Standard Occupational Classification (SOC) codes.

The way this works in practice is mechanical:

1. The Labor Condition Application identifies the SOC code under which the role is being filed (e.g., 15-1252 for Software Developers).
2. The officer pulls the O*NET profile for that SOC code.
3. The officer reads the Job Zone rating and the Education Required distribution.
4. The officer compares this to the duties described in the offer letter and supporting documents.

O*NET classifies every occupation into one of five Job Zones based on preparation needed:

• Job Zone 1: Little or no preparation needed
• Job Zone 2: Some preparation needed (typically high school plus on-the-job training)
• Job Zone 3: Medium preparation needed (typically associate’s degree or vocational training)
• Job Zone 4: Considerable preparation needed (typically bachelor’s degree)
• Job Zone 5: Extensive preparation needed (typically graduate degree)

A role classified in Job Zone 4 or 5 with a strong bachelor’s-degree requirement in O*NET is in good position. A role in Job Zone 3 or below faces a significant headwind — the officer is now looking at a position that the Department of Labor itself characterises as not normally requiring a bachelor’s degree.

For each occupation, O*NET also publishes the percentage of incumbents holding each level of education. The relevant data point is the percentage holding a bachelor’s degree or higher. When that percentage is high (75%+), the first criterion of the four-factor test is essentially satisfied. When it’s low (under 50%), the application needs to win on a different theory — usually the third or fourth criterion, requiring more substantial documentation.

A practical consequence: the SOC code on the LCA is one of the most consequential strategic choices in an E-3 application. Filing a marketing manager role under SOC 11-2021 (Marketing Managers — Job Zone 4, strong bachelor’s expectation) versus 13-1161 (Market Research Analysts — Job Zone 4, but with a different educational profile) versus 41-9099 (Sales and Related, All Other — Job Zone 3, lower bachelor’s expectation) produces materially different outcomes for the same actual job. Employers self-filing without legal advice often pick the wrong SOC code and create a problem the rest of the file has to fight uphill against.

What “clearly qualifying” looks like {#clearly-qualifying}

Some roles are essentially never refused on specialty-occupation grounds. The pattern is consistent: the job sits in a clearly degreed profession, the SOC code maps cleanly to a recognised specialty, the duties demonstrably require theoretical knowledge from a specific discipline, and O*NET’s data confirms that the occupation is overwhelmingly held by degree-holders in that field.

Examples that consistently qualify without controversy:

• Software Engineer / Software Developer (SOC 15-1252): Computer science, software engineering, or closely related degree. Job Zone 4. ~80% bachelor’s or higher.
• Data Scientist (SOC 15-2051): Statistics, mathematics, computer science, or related degree. Job Zone 5.
• Mechanical / Electrical / Civil Engineer (SOC 17-2141 / 17-2071 / 17-2051): Engineering degree in the relevant discipline. Job Zone 4. Universally degreed profession.
• Financial Analyst (SOC 13-2051): Finance, economics, accounting, or related degree. Job Zone 4.
• Accountant / Auditor (SOC 13-2011): Accounting degree. Job Zone 4. Often regulated.
• Architect (SOC 17-1011): Architecture degree. Job Zone 5.
• Physician, Dentist, Pharmacist, Veterinarian: Professional degrees. Job Zone 5. Licensed.
• Lawyer (SOC 23-1011): JD. Job Zone 5. Licensed.
• Statistician, Actuary, Economist: Closely-tied academic disciplines. Job Zone 5.
• Research Scientist in a defined discipline: Specialty PhD typically required.

What these have in common: a specialty-specific degree path, a regulated or near-regulated professional identity, duties that are recognisable as the practice of the profession, and O*NET data showing high degree concentration.

If your offered role and your degree both sit cleanly in one of these categories, specialty occupation is rarely the issue in your E-3 case — other elements of the file (degree equivalency, LCA accuracy, intent) are more likely to surface.

The borderline cases {#borderline-cases}

The interesting cases — and the ones that produce a disproportionate share of refusals — are roles where the link between the duties and a specific academic discipline is contestable.

Marketing and market research analyst roles {#marketing}

Marketing roles are among the most refused borderline categories — and the case law explaining why is unusually well developed for one specific marketing sub-occupation: Market Research Analyst.

The reason is that “marketing” is not, taxonomically, a single occupation — it spans roles with very different educational profiles. A Marketing Manager at a Fortune 500 directing strategy with a substantial budget, working from quantitative customer-analytics data, is a different job from a “Marketing Coordinator” running social media. Both might appear in a job ad as “marketing.” Only one of them clearly requires a bachelor’s degree in a specific discipline.

The Market Research Analyst saga

The single most litigated specialty-occupation classification in H-1B history is the Market Research Analyst (SOC 13-1161, O*NET profile here). Because E-3 adjudications draw on the same body of specialty-occupation analysis, this litigation directly shapes how Market Research Analyst E-3 cases are evaluated.

The dispute traces to USCIS’s reading of the Department of Labor’s Occupational Outlook Handbook (OOH) entry for Market Research Analyst. The OOH lists multiple acceptable degree fields — marketing, statistics, business administration, communications, social sciences, and others — and USCIS treated this list as evidence that the occupation does not normally require a bachelor’s in a specific specialty.

The first major rebuke came in Residential Finance Corporation v. USCIS, 839 F. Supp. 2d 985 (S.D. Ohio 2012), where the Southern District of Ohio rejected USCIS’s narrow OOH interpretation. The court held that:

“The knowledge and not the title of the degree is what is important. Diplomas rarely come bearing occupation-specific majors. What is required is an occupation that requires highly specialized knowledge and a prospective employee who has attained the credentialing indicating possession of that knowledge.”

Despite Residential Finance, USCIS continued to deny Market Research Analyst petitions on similar grounds. This produced MadKudu Inc. v. USCIS, a class action filed in the Northern District of California in April 2020, alleging a pattern and practice of arbitrary denials.

The parties reached a settlement on 20 August 2021. Under the settlement, USCIS conceded that the OOH description of Market Research Analyst does satisfy the first regulatory criterion — that a bachelor’s or higher degree in a specific specialty is normally the minimum requirement. USCIS also agreed to allow employers whose petitions had been denied between 1 January 2019 and 19 October 2021 to file motions to reopen.

The practical takeaway for E-3 applicants: a Market Research Analyst role, properly documented, should satisfy the specialty-occupation test today. But the file still has to do meaningful work. The settlement doesn’t grant automatic approval — it requires USCIS to apply the specialty-occupation test correctly, not to skip it. Per the settlement’s terms, USCIS may still issue an RFE where the employer accepts a wider range of degrees (e.g., business administration without a specific specialisation in market research), and the employer must show the additional fields are necessary for the duties.

Other marketing roles

Beyond Market Research Analyst, the risk pattern in marketing applications:

• Generic “Marketing Specialist” or “Marketing Coordinator” roles, especially in small companies, often look more like generalist execution work than specialty work.
• Digital marketing roles can involve substantial technical work (analytics, SEO, marketing-automation platforms, A/B testing, attribution modelling) that genuinely requires theoretical knowledge — but the job description has to actually describe that work in those terms. A description that reads “manage social media accounts and create engaging content” will not, no matter how complex the underlying work actually is.
• Brand marketing at established consumer companies often involves consumer-research methodologies, market-research analysis, and product-strategy work that maps to a specialty. Again — only if described that way.

The strategic move in marketing cases: file under the SOC code that best reflects the substantive work, write the job description so that it foregrounds the analytical and theoretical content of the role, and where possible identify the specific specialty-related discipline (marketing, advertising, consumer research, or — increasingly common — quantitative business disciplines like statistics or data analytics) from which the requisite knowledge derives.

Sales roles {#sales}

Sales is the hardest category. Most “sales” jobs are not specialty occupations, full stop. The Bureau of Labor Statistics and O*NET typically classify sales roles in lower Job Zones, and there is rarely a “specific specialty” degree associated with sales.

There are real exceptions. Sales Engineers (SOC 41-9031, Job Zone 4) sell technical products and need engineering knowledge to do so credibly. Pharmaceutical Sales Representatives in some configurations require a science background. Enterprise software sales to technical buyers can require deep domain knowledge.

But the line between a Sales Engineer and a “Senior Account Executive at a tech company” is often non-obvious to a consular officer reading the file, and the burden is on the applicant to make the case. Documentation matters: technical product literature the candidate actually uses, customer-facing technical work product the candidate has produced, certifications, the educational backgrounds of incumbents in similar roles at the company.

A sales role with a generic “B2B sales” description, no technical product specificity, and a degree requirement that reads as “we prefer college graduates” is going to struggle on E-3 review even if the candidate is exceptional and the compensation is high.

Project and program management {#project-management}

Project management is another heavily-scrutinised borderline category, and for the same reason as marketing: the title is not the job. There are highly technical project-management roles in engineering, construction, software, and pharma that demonstrably require specific specialty knowledge to perform — and there are project-coordinator roles that are essentially Gantt-chart maintenance and stakeholder updates.

The doctrinal complication for project management is the same one that produced the Market Research Analyst litigation: USCIS has historically taken the position that an occupation accepting degrees from multiple fields fails the “specific specialty” requirement. As one practitioner noted of the trend, “even if a position is shown that it requires a bachelor’s degree, it must be in a specific field related to the position. In other words, proving that a position normally requires a bachelor’s degree is not enough; rather, it must be shown that the position requires a bachelor’s degree in a specific field or a very narrow list of fields.”

The specific complications:

• “Project Management Specialist” (SOC 13-1082) is in Job Zone 4 and does typically require a bachelor’s degree per O*NET, but the educational profile is broad — degrees in business, engineering, computer science, and many others all appear in the data. This makes the “specific specialty” part of the four-factor test harder to satisfy.
• “Program Manager” is even more variable. At one large tech company the title might mean a senior individual contributor running a multi-million-dollar product line; at another it might mean a junior coordinator.
• Construction Project Managers with engineering or architecture backgrounds operating on technical projects do well.
• Technical Program Managers at software companies — handling cross-team execution that requires CS knowledge to be credible — can do well, but the case has to be built. A useful approach is to file under SOC 15-1299.09 (Information Technology Project Managers) where the duties support it, rather than under the general project-manager SOC.

The successful project-management case ties the management duties to a specific technical or scientific discipline, identifies the duties that require theoretical knowledge from that discipline, and shows that the company requires (and incumbents hold) degrees in that specific specialty.

Operations, business analyst, and “generalist” titles {#operations}

The last cluster of borderline cases involves titles like Operations Manager, Business Analyst, Business Operations, Strategy Associate, Chief of Staff, and similar generalist roles common at startups and consulting firms.

These roles often involve genuinely complex analytical work — quantitative analysis, financial modelling, strategy development. The challenge is that the degree requirement is typically structural (“bachelor’s degree, ideally in a quantitative field, or equivalent experience”) rather than a strict specialty requirement. O*NET classifications for general business roles tend to show educational profiles too broad to satisfy the “specific specialty” test cleanly.

These cases can succeed when:

• The duties demonstrably require quantitative or analytical methods drawn from a specific discipline (financial modelling from finance/economics; statistical analysis from statistics or data science; operations research methods from industrial engineering);
• The applicant’s degree is in that discipline;
• The job description is written to foreground that specialty-knowledge dimension rather than the generalist-coordinator dimension;
• The SOC code chosen on the LCA reflects the specialty character of the role.

Strategy and consulting roles are particularly worth thinking through carefully. Big-firm consulting analyst and associate roles have, over the years, mostly been treated as specialty occupations in finance/economics-driven contexts, but the analysis is fact-specific, and a consultant role at a less well-known firm or in a less-quantitative practice area can face scrutiny.

How to build a defensible specialty-occupation case {#how-to-build-the-case}

The successful approach has the same architecture in almost every case:

1. Pick the right SOC code. This is a strategic decision, not a clerical one. The SOC code on the LCA effectively tells the consular officer which O*NET profile to consult and frames the entire educational analysis. A wrong SOC code creates problems no other element of the file can fix.

2. Write the job description to foreground specialty content. Job descriptions written for HR purposes are often the worst possible documents for E-3 purposes. They describe responsibilities in generic terms (“liaise with stakeholders,” “drive outcomes”) rather than describing the theoretical and analytical content of the work. The E-3 file should include a job description that explicitly identifies the bodies of specialised knowledge the role draws on, the specific methodologies used, the analytical techniques applied, and the educational background that prepares someone to perform them.

3. Tie the candidate’s specific degree to the specific duties. A computer science degree applied to a software engineering role is self-evident. A finance degree applied to a financial analyst role is self-evident. A psychology degree applied to a UX designer role needs the connection drawn out — and it can be drawn out, but the file has to do it. The specialty-occupation memorandum should walk through specific course content and tie it to specific job duties.

4. Document the employer’s degree requirement. Internal job posting, recruiting materials, prior hires for the same role, written job specifications. The third criterion (“the employer normally requires a degree or its equivalent for the position”) is satisfied by evidence that this isn’t a one-off requirement created for the visa.

5. Document industry practice. For roles where the second criterion is the strongest argument (degree common to the industry in parallel positions), supporting evidence includes job postings from peer employers, industry-association educational standards, and where available, academic or industry literature describing the role.

6. Consider an expert opinion letter for borderline cases. For roles where the connection between degree and duties needs explication, a written opinion from a US academic in the relevant field, walking through the theoretical knowledge required and connecting it to the duties, is genuinely persuasive. These are the same letters used in degree-equivalency cases (see our 3-year-degree article) but written to a different question.

What gets your file refused {#what-gets-refused}

Reading the published guidance and the appellate decisions on H-1B specialty-occupation refusals (which apply to E-3 by analogy), the patterns are consistent:

• Vague duty descriptions. “Responsible for marketing initiatives.” “Will manage projects.” “Will oversee operations.” These tell the officer nothing about the theoretical content of the work and provide no basis for a specialty-occupation conclusion.

• Generic degree requirements. “Bachelor’s degree required” without specifying a field. The officer cannot evaluate whether the degree is in the specific specialty if no specialty is identified.

• Mismatch between duties and SOC code. A role described as digital strategy filed under a sales SOC. A role described as software architecture filed under a project-management SOC. The misalignment alone creates a credibility problem.

• Mismatch between candidate’s degree and offered role. A history degree for a software engineering role. A music degree for a financial analyst role. These can sometimes be saved through the three-for-one rule (see our 3-year-degree article), but the case has to be built explicitly and supported with substantial work-experience documentation.

• O*NET data pointing the wrong way. A role filed under a SOC code where O*NET shows that most incumbents do not hold a bachelor’s degree, without strong supporting documentation under criteria 3 or 4 of the four-factor test.

• No internal documentation of the degree requirement. The employer says they require a degree, but no job posting, internal description, or prior-hire pattern supports the claim.

• Reliance on “specialty occupation” language without substance. A specialty-occupation memorandum that recites the legal standard but doesn’t apply it to the specific facts is read as a template and discounted accordingly.

A note on how this is changing

The State Department and USCIS approach to specialty-occupation analysis has tightened materially over the last decade, particularly for roles outside the traditional STEM and finance disciplines. H-1B denial rates — a useful proxy for specialty-occupation scrutiny generally, and directly relevant to E-3 because the standards are statutorily identical — illustrate the swings. According to Pew Research Center analysis of USCIS data, denial rates peaked at 15% in fiscal 2018 (24% for new initial-employment petitions), driven in part by tighter interpretations of “specialty occupation” under the Buy American, Hire American executive order. Following litigation including ITServe Alliance v. Cissna (D.D.C. 2020) and the MadKudu settlement, denial rates fell back below 4% under the Biden administration.

The story for E-3 specialty-occupation scrutiny tracks the H-1B story, with a lag and some independence — consular officers don’t apply USCIS’s interpretive memos directly, but State Department training and the underlying body of decisional law follow the same arc. Recent USCIS policy guidance has emphasised the “specific specialty” element more strongly, and consular officers have followed that emphasis in adjudicating E-3 applications. The result is that cases that would have been straightforward five or ten years ago — generalist business roles, marketing roles in small companies, sales roles in technology — now require more careful documentation than they used to.

Policy direction in 2025 and 2026 may push these standards further. The September 2025 Presidential Proclamation imposing significant restrictions on H-1B issuance signals renewed scrutiny of specialty-occupation classifications generally. The E-3 visa is statutorily distinct and not directly subject to those restrictions, but adjudicative culture is contagious — applicants and counsel should plan for the more rigorous environment, not the more permissive one.

The good news is that the framework is stable and the analysis is doable. The cases that fail today fail for documentation reasons, not because the role is intrinsically unqualifying. The bad news is that more roles need real legal work than employers (or applicants self-filing) typically expect.

---

Where this article ends and case-specific advice begins

Everything above is general information about how the legal framework operates. It is not advice on any particular role’s qualification as a specialty occupation, and it shouldn’t be treated as a substitute for consultation with an immigration lawyer who has reviewed your specific job description, duties, employer documentation, and educational background.

If you have an offer in one of the borderline categories — marketing, sales, project management, operations, generalist business — and want a real assessment of whether the role qualifies, book a free 20-minute eligibility call and we’ll tell you what we’d do in your shoes.

---

Related reading

• The complete E-3 visa guide for Australians
• The 3-year Australian bachelor’s degree problem
• The Labor Condition Application (LCA) for E-3 visas
• E-3 visa refusals: why they happen and what to do next

---

Attorney Advertising. The information on this website is for general informational purposes only and does not constitute legal advice. Use of this website does not create an attorney-client relationship. Communications with the firm are not protected as confidential until a written engagement letter has been signed by both parties. Prior results do not guarantee a similar outcome. Last reviewed 11 May 2026.