How to Create an H-1B Role Description That Won’t Trigger an RFE

TechBridge recruits top developers and places them with the businesses that need their expertise.

If you’ve ever submitted an H-1B petition and gotten hit with a dreaded RFE (Request for Evidence), chances are the issue wasn’t with the candidate. It was with the job description.

Poorly written or misaligned job descriptions are one of the most common reasons USCIS challenges H-1B petitions. For startups and small employers without dedicated immigration teams, this can feel frustrating, confusing, and costly.

So how do you craft a job description that supports your petition, satisfies USCIS expectations, and avoids red flags? It comes down to structure, language, and internal alignment around the SOC code and wage level.

Let’s break it down.

What USCIS Looks for in H-1B Job Descriptions

At its core, an H-1B job description must demonstrate that the role qualifies as a “specialty occupation,” meaning it requires a bachelor’s degree or higher in a specific field.

That means USCIS is reviewing your job description for three main criteria:

1. Level of specificity: Are the duties clear and narrowly defined, or vague and overly broad?
2. Skill and complexity: Do the tasks require specialized knowledge, or could they be done by a generalist?
3. Degree relevance: Is there a direct link between the required degree and the tasks described?

If your description reads like a generic posting or includes unrelated duties, it increases the likelihood of scrutiny.

📘 Source: USCIS Policy Manual – Specialty Occupation Definition

Common Triggers That Lead to RFEs

Even well-intentioned job descriptions can trigger an RFE if they contain these red flags:

1. Mismatch Between Title and SOC Code

Example: You assign the SOC code for “Software Developers” (15-1252), but the title is “Data Analyst” and the duties don’t include software development.

Why it’s a problem: USCIS flags inconsistencies between job title, duties, and SOC code, assuming it may be a misclassified or non-specialty role.

✅ How to avoid it: Use O*NET OnLine to review SOC code responsibilities and ensure your title/duties align.

2. Entry-Level Language in Mid-Level Roles

Example: The job duties include phrases like “assist with projects,” “provide general support,” or “learn and develop under supervision,” even though you’re filing at Wage Level 2 or 3.

Why it’s a problem: Wage levels are tied to complexity, independence, and supervision. If the duties sound junior but the wage level is high, USCIS will ask for justification.

✅ How to avoid it: Align your wage level with the description’s complexity. Our Wage Level Planning Checklist can help with this.

3. Missing Degree Justification

Example: You require a “Bachelor’s in Computer Science, Engineering, or related field,” but the job duties include basic data entry and scheduling.

Why it’s a problem: USCIS wants to see a clear connection between the degree and the job’s responsibilities. If that link is missing, your petition may be denied.

✅ How to avoid it: Describe tasks that clearly require academic training, such as algorithm development, system architecture, or application design.

Crafting a Role That Aligns with Wage Level & SOC Code

Here’s how to build an H-1B job description that not only avoids RFEs but sets your petition up for success.

1. Start with the SOC Code, Not the Title

Many employers write a job title first and try to make everything fit around it. That’s backwards. You should begin with the SOC code that most accurately reflects the job duties, and build from there.

For example, if your candidate will spend 70% of their time developing APIs, debugging applications, and managing deployments, a role under “Software Developers” is probably a better fit than “Business Analysts.”

Use O*NET to:

• Compare several SOC codes side by side
• Identify required tasks and tools
• Review required knowledge and education levels

📘 O*NET Online: Compare Occupations

2. Write Duties That Match the Wage Level

The DOL wage level system ranges from Level 1 (entry-level) to Level 4 (expert). Each level comes with expectations around supervision, responsibility, and complexity.

Use this framework when writing your duties:

Pro Tip: Avoid mixing Level 1 and Level 4 language in the same job description. It causes confusion and undermines your wage justification.

3. Include Keywords Without Overstuffing

If you’re submitting a Software Engineer role, include language like:

• “Writes production-level code in JavaScript and Python”
• “Collaborates on RESTful API development”
• “Conducts unit testing and performance tuning”

Avoid vague, non-technical phrases like “assists with technical duties” or “works with engineers.” Be specific, but don’t keyword-stuff. It should read naturally.

4. Justify the Degree Requirement

Every job description should explain why a bachelor’s degree in a specific field is essential. You can do this in one or two sentences, such as:

“This role requires a Bachelor’s in Computer Science to understand the architecture of multi-tiered systems, apply software engineering principles, and build scalable applications.”

Make sure the duties reflect tasks that couldn’t reasonably be performed by someone without that degree.

Bonus Resource: Wage Level Planning Checklist

If you want to build a system that ensures role descriptions align with wage levels and SOC codes, our Wage Level Planning Checklist walks you through:

✔️ Mapping duties to the correct SOC
✔️ Choosing the right wage level
✔️ Avoiding language that triggers RFEs
✔️ Best practices for compliance documentation

📥 Download the Checklist Here

Final Thoughts

A strong job description does more than attract candidates—it protects your H-1B petition from unnecessary RFEs.

By aligning SOC codes, wage levels, and job duties with USCIS expectations, you reduce the risk of delays, save legal costs, and increase the likelihood of approval.

Whether you’re an attorney advising startups or an in-house People Ops leader handling your first H-1B, building a repeatable process for job description alignment is key.

And if you’re unsure where to start? Grab our free Wage Level Planning Checklist to audit your descriptions before you file.