Specialty occupation RFEs account for the majority of H-1B denials. This guide breaks down exactly what USCIS is looking for, how to build a response that wins, and the specific evidence that makes the difference.
A specialty occupation RFE is USCIS questioning whether the offered position requires, in the normal course of work, the theoretical and practical application of a body of highly specialized knowledge. The INA definition has four prongs — USCIS needs you to satisfy at least one:
Prong 1: A baccalaureate or higher degree in a specific specialty (or equivalent) is the normal minimum for entry into the occupation in the US. Prong 2: The degree requirement is common to the industry in parallel positions among similar organizations. Prong 3: The employer normally requires the degree for the position. Prong 4: The nature of the specific duties is so specialized and complex that knowledge required to perform them is usually associated with the attainment of a baccalaureate or higher degree.
The most common USCIS objection in 2026 is that the position does not require a degree in a specific specialty — accepting any bachelor's degree (or business + computer science + engineering) is not sufficient. USCIS wants to see that the position requires a degree in a particular field, not merely a degree of any kind.
The second most common objection targets IT consulting placements where USCIS argues the consulting firm has no control over the end-client work assignment, and therefore cannot demonstrate what specific duties the beneficiary will perform. This is the "specialty occupation + employer-employee relationship" double challenge that trips up staffing-model H-1B cases.
1. Detailed position description with specific duty mapping. The support letter or position description must enumerate specific duties and explain — for each — why it requires specialized degree knowledge. Generic descriptions like "analyze data" or "develop software" are insufficient. USCIS expects language like: "perform eigenvalue decomposition and singular value decomposition to identify latent factors in large-scale recommendation systems, requiring a degree in Computer Science or Applied Mathematics with coursework in linear algebra and machine learning theory."
2. OES/BLS occupational data and expert opinion letters. The Bureau of Labor Statistics Occupational Employment Statistics (OES) data, O*NET, and the Occupational Outlook Handbook all provide data on typical education requirements for specific roles. Expert opinion letters from academics, senior practitioners, or professional associations confirming that the specific degree field is the industry standard for the role are highly effective — especially for newer roles (ML engineers, data scientists, cloud architects) where OES data may lag industry practice.
3. Job postings for similar positions from comparable employers. Collect 5–10 current job postings for the same or similar role from competitors, Fortune 500 companies, or industry-recognized employers. If every posting requires a CS degree, that is evidence the degree is "common to the industry." Use LinkedIn, Indeed, and Glassdoor. Print or PDF the postings with URLs and access dates. This evidence is highly persuasive and often decisive.
4. Employer's own historical hiring practices. If the petitioning employer has filled the same or similar positions exclusively with degree holders in the specific field, submit evidence of this: prior approved petitions for the same role, organizational charts showing education levels of comparable employees, or an HR declaration confirming the company's degree requirement policy and rationale.
IT consulting and staffing company H-1B cases face a specific challenge: USCIS often argues that because the beneficiary is placed at a client site, the consulting firm cannot demonstrate (a) what specific duties will be performed, and (b) employer-employee control over those duties.
Winning this challenge requires: specific project documentation (SOW, MSA, or detailed project description) showing the actual work to be performed at the client site; the beneficiary's specific role in that project (not just "software developer" but "architect the microservices migration from monolith to Kubernetes-based containers for the client's payment processing system"); and the client's confirmation (through a client letter) of the specific role and degree requirement.
The ITServe Alliance v. Cissna (2019) court ruling and USCIS's subsequent policy update provide some protection for IT consulting cases — USCIS cannot deny solely because the work is at a third-party site, and must evaluate whether the specific duties constitute specialty occupation. Reference this precedent in RFE responses for consulting placement cases.
If you do not have a specific project identified at RFE response time, you face a harder challenge. You can respond with a general description of the types of projects the beneficiary will work on, supported by the employer's portfolio of work, prior similar placements, and client relationship documentation — but this is weaker than specific project evidence.
An effective specialty occupation RFE response has a clear structure. Follow this framework:
Section 1: Overview and roadmap. One page maximum. State which prong(s) you are relying on. Provide a summary of the key evidence. Give the adjudicator a roadmap so they know what to look for.
Section 2: Detailed position analysis. Take each of USCIS's specific objections from the RFE and address them directly and explicitly. Do not ignore any objection. Do not rephrase the objection — quote it, then answer it with evidence.
Section 3: Evidence exhibit index. Number every exhibit, state what it is, and cite it by exhibit number throughout your brief. USCIS adjudicators appreciate organized submissions — disorganized evidence is often overlooked.
Section 4: Legal authority. Cite Matter of Michael Hertz Associates, Matter of Simeio Solutions, and relevant AAO non-precedent decisions that support your position. The Matter of Simeio Solutions AAO decision is the primary authority on specialty occupation for IT cases.
Length: most strong specialty occupation RFE responses are 20–40 pages including exhibits. Do not pad with irrelevant material — every page should address a specific USCIS concern with specific evidence.
If the specialty occupation RFE response results in denial, you have several options. Each has a hard deadline — missing it forecloses that path. Act immediately upon receiving the denial notice.
Motion to Reopen (MTR): filed with the same USCIS service center within 30 days of the denial. Requires new facts or evidence not available at the time of the response. If you have additional evidence that would change the outcome, this is the fastest path to reopening the case without starting over.
Motion to Reconsider (MTC): filed within 30 days of denial. Argues that the denial was legally erroneous based on the existing record — no new evidence, just a legal argument that USCIS misapplied the law. Harder to win than MTR but available when the denial has clear legal errors.
AAO Appeal (Form I-290B): filed within 30 days of denial or simultaneously with MTR/MTC. AAO reviews the record de novo. AAO decisions take 6–24 months. A concurrent MTR/appeal is a common strategy — if the service center grants the MTR, the AAO appeal is mooted; if not, the AAO appeal proceeds.
Refile new petition: for cases where the factual situation has changed (new client, new project, amended job description), refiling a new H-1B petition with improved evidence is often the cleanest path. No deadline constraints, but the beneficiary must maintain valid status in the interim.
David Kim is an immigration attorney specializing in H-1B petitions and RFE responses. He has handled hundreds of specialty occupation challenges for tech companies, IT consulting firms, and Fortune 500 employers.