Master prompt
H-1B RFE response — specialty occupation challenge
Rebuts USCIS specialty-occupation RFE on Wage Level I, generic SOC, or "any degree" job-posting concerns. Four-prong 8 CFR §214.2(h)(4)(iii)(A) framework.
USARFEH-1BSpecialty Occupation8 CFR 214.2(h)Defensor
H-1B specialty occupation RFEs are the highest-volume USCIS RFE category. Officer typically challenges the petition on one or more of:
(a) Wage Level I appearance contradicts specialty occupation (entry-level role doesn't require specialized degree)
(b) SOC code permits "any bachelor's degree" — fails specific-specialty requirement
(c) Job duties recited generically without showing specialty
(d) End-client arrangement — Defensor v. Meissner right-to-control failure when beneficiary placed at third-party site
8 CFR §214.2(h)(4)(iii)(A) — position must meet at least ONE of four prongs:
(1) Bachelor's or higher in specific specialty normally required
(2) Degree requirement common to industry in parallel positions OR position so complex/unique that performance requires degree
(3) Employer normally requires degree for position
(4) Nature of specific duties so specialized + complex that knowledge required is associated with bachelor's or higher
Draft an RFE response for [EMPLOYER_NAME] sponsoring [BENEFICIARY_NAME] as [POSITION_TITLE] (SOC [SOC_CODE], Wage Level [WAGE_LEVEL]).
§1 — RFE DECODE (100-130 words)
Quote each concern verbatim from [RFE_CONCERNS] and map to:
(a) Underlying regulatory standard (which prong of §214.2(h)(4)(iii)(A))
(b) Officer's implicit doubt
(c) Required rebuttal element
Common officer suspicion patterns:
• "Beneficiary's degree is too generalist" → Prong 1 challenge
• "SOC [code] accepts multiple degrees" → Prong 1 + Prong 2 challenge
• "Wage Level I incompatible with specialty" → All-prong challenge (Wage Level I = "entry-level" which officers read as not specialty)
• "Job duties stated generically" → Prong 4 (specific duties)
• "Right to control unclear at client site" → Defensor challenge (separate from specialty but often paired)
§2 — POSITION COMPLEXITY EVIDENCE — PRONG 4 (180-220 words)
Strongest single rebuttal element. Demonstrate that [JOB_DUTIES] are so specialized and complex that they require specific-specialty knowledge.
Build evidence:
□ Detailed duties breakdown with percentages — granular (40% of duties involve X technical task, 25% involves Y, etc.) — from [JOB_DUTIES]
□ For each major duty: map to specific course content / technical skills from a [DEGREE_FIELD] curriculum
□ Letter from [BENEFICIARY_NAME]'s university registrar or department chair confirming specific courses + their relevance to [POSITION_TITLE] duties
□ Industry-standard job descriptions from O*NET / BLS for comparable roles
□ Project documentation showing past beneficiary work product (architecture diagrams, technical specifications, code samples — redacted as needed) demonstrating specialty
□ Internal training requirements — if beneficiary required to complete employer-specific specialty training, document
□ Tools / methodologies used (specific software, programming languages, statistical methods, etc.) requiring specialty knowledge
For [POSITION_TITLE] = Software Developer / Engineer (most common in Indian H-1B cohort):
Don't rely on generic O*NET language. USCIS officers see thousands of generic SDE petitions; differentiate via:
• Specific tech stack + complexity
• Production code responsibility (vs trainee)
• Architectural / design responsibilities
• Code review + mentoring responsibilities
§3 — INDUSTRY EVIDENCE — PRONG 2 (150-180 words)
Show degree requirement is common across industry in parallel positions:
□ Job postings from 8-12 similar employers for same role:
- Companies of comparable size + industry to [EMPLOYER_NAME]
- Postings dated within last 6-12 months
- Highlight: "Required: Bachelor's degree in [specific field]" language
□ Expert opinion letter:
- From academic in relevant field OR industry consultant with credentials
- Address each duty + map to required degree-level knowledge
- Cite peer-reviewed sources or industry standards
□ Industry publications + position papers (IEEE, ACM, Bureau of Labor Statistics narrative descriptions)
□ Trade association requirements (if applicable — e.g. CFA for finance, FAA license for aviation)
For complex/unique alternative under Prong 2:
If [POSITION_TITLE] involves uniqueness (e.g. cutting-edge technology, novel business model), build complexity narrative:
• Why generic equivalents don't suffice
• Specialty knowledge required to perform
• Risk of harm / business failure if performed by non-specialist
§4 — EMPLOYER HISTORY — PRONG 3 (80-100 words)
Show [EMPLOYER_NAME] normally requires the degree for [POSITION_TITLE]:
□ Historical hiring data for [POSITION_TITLE] — employees in the role with their degrees + universities
□ Job posting archive showing degree-required language
□ Internal HR policy / job description database showing degree requirement
□ Affidavit from HR director / hiring manager confirming standard practice
Caveat: Prong 3 is weak as standalone — courts have rejected "employer policy" alone as creating specialty (Royal Siam Corp v. Chertoff, 484 F.3d 139 (1st Cir. 2007)). Pair with Prong 1, 2, or 4.
§5 — WAGE LEVEL I REBUTTAL (100-130 words)
If [WAGE_LEVEL] = Level I and RFE flags this:
Wage Level I = "entry-level" but does NOT mean non-specialty. Argue:
• Level I reflects experience tier within the specialty — not whether specialty exists
• [BENEFICIARY_NAME] is entry-level WITHIN the specialty (e.g. recent graduate of [DEGREE_FIELD] program); position itself still requires the specialty degree
• DOL prevailing wage levels measure experience + responsibility within a specialty, not the existence of specialty
• Cite Inter-Coast Junior Coll. v. INS, 12 F. Supp. 2d 1097 (D. Or. 1998) line: entry-level position can still require specialty knowledge
• Caltech, Stanford, MIT recent graduates routinely accept Level I positions that nonetheless require their specialty PhDs
For Level I + recent graduate beneficiary: include curriculum + program info showing specialty depth.
§6 — DEFENSOR / RIGHT-TO-CONTROL (FOR CLIENT-SITE PLACEMENTS) (130-160 words)
If [CLIENT_SITE] = Third-party client site:
Defensor v. Meissner, 201 F.3d 384 (5th Cir. 2000) — petitioner must demonstrate:
(a) End-client position itself qualifies as specialty occupation
(b) Petitioner retains right to control beneficiary's work
(c) Itinerary detail of work location + duration
Required submission:
□ End-client letter from [client_name] confirming:
- The position they need filled is specialty
- The job duties at the client site
- The required qualifications match
- Duration of placement
□ Statement of Work (SOW) or Master Services Agreement (MSA) excerpts between petitioner + client showing scope
□ Reporting structure: who manages [BENEFICIARY_NAME] (petitioner manager vs client manager)
□ Performance evaluations (who conducts; client or petitioner)
□ Equipment / tools provided by petitioner (laptop, software licenses)
□ Detailed itinerary if work at multiple sites
For Indian-IT-services pattern (Wipro, TCS, Infosys, HCL, Tech Mahindra, etc.): expect extra scrutiny. End-client documentation must be specific, dated, signed. Generic "engagement letters" insufficient.
§7 — RESPONSE PACKAGE STRUCTURE (60-80 words)
Final assembly:
□ Cover memo (counsel signed) — 5-8 page legal argument addressing each RFE concern
□ Updated I-129 if material changes
□ Updated LCA if wage / location changed
□ Evidence index with tabs (A1, A2, ... per category)
□ Expert opinion letter (if relied upon)
□ End-client documentation (if applicable)
□ Beneficiary qualifications package
□ Employer documentation
□ Response deadline: typically 87 days from RFE issuance — DO NOT MISS
End with: "DRAFT H-1B SPECIALTY OCCUPATION RFE RESPONSE — for licensed US immigration attorney review. Substantive RFE response preparation involves legal argumentation + strategic evidence selection — this is attorney work under state UPL rules + 8 CFR §292.1. Defensor right-to-control documentation is highly fact-specific. Verify current AAO + Federal Court precedent on specialty occupation challenges before finalizing."Unlock the vault to see the full prompt