employer: same company
- title: Senior Java Developer
+ title: Engineering Lead
- duties: build and test services
+ duties: design services, review code, lead four engineers
worksite: same office
Developers read diffs all day. A promotion on H-1B is a diff too. The question is simple. Is it a safe patch, or a breaking change?
With H-1B, a U.S. company can employ a foreign degree holder in a specialty occupation. Your petition and its wage filing describe one job. When the job changes, the papers may need to change as well.
Aimpex Resources Group LLC wrote this piece. We place Java and .NET engineers, cloud and data people, and quality assurance (QA) engineers. Promotions are good news in our world. This post covers the paperwork side.
Why did HR say "wait for the extension"?
A worker posted on Reddit's r/h1b in April 2026. They had joined their firm about a year earlier as an architectural designer on H-1B. They were up for promotion to "Job Captain" in the May cycle. The duties would be fairly similar, with more ownership and coordination. Human resources (HR) then said the new role needed an H-1B amendment. HR's advice was to wait until the next extension filing. To the worker, it felt like a denied promotion.
Their field is building design, not software. But the rules below are the same for a .NET developer. They are the same for a SAP consultant or a QA lead.
What makes a change "material"?
The key rule is 8 CFR 214.2(h)(2)(i)(E), in the Code of Federal Regulations (CFR). Under it, "any material changes" to your job need an amended or new petition.
For H-1B, that filing includes "a current or new certified labor condition application." That is the Labor Condition Application (LCA). The Department of Labor (DOL) certifies it before the petition is filed.
The rule gives no full list of material changes. So employers and their attorneys compare the old job with the new one. These are the fields they usually check:
- the duties and how much time each takes
- the occupational classification on the LCA
- the worksite and area of work
- the wage
Which LCA fields matter for a promotion?
DOL rule 20 CFR 655.730(c)(4) says each LCA "shall identify the occupational classification." So one LCA covers one type of job.
Think about two moves. A senior developer becomes a lead developer and still writes code. The occupation may stay the same. A developer becomes a people manager who rarely codes. That could fall under a different occupation. An attorney makes that call from the real duties.
The wage rule is 20 CFR 655.731(a). The wage must be "the greater of the actual wage rate" or "the prevailing wage." In plain words, the LCA sets a floor. A promotion with a raise keeps you above that floor. It does not break the wage promise by itself.
Note one limit here. A raise alone does not answer the duties question. Check both.
On what date may the new duties begin?
The rule also sets the timing. An amended petition "must be properly filed before the material change(s) takes place."
After that, H-1B portability can apply. United States Citizenship and Immigration Services (USCIS) explains this on its H-1B page. That page says Form I-129 also covers "a change of employment" inside your current company. You may then work under the new terms "once that petition is filed." A petition can ask for a later start. In that case, the later date wins.
This only works if the filing goes in before your current stay ends and you have not worked without permission. If portability does not apply, the new duties must wait for approval.
So the safe order looks like this:
- The employer reviews the new duties with its attorney.
- The employer gets a new LCA if the job needs one.
- The amended petition goes to USCIS.
- You start the new duties after the filing, or on the requested start date.
Working in the new role before step 3 is the risky part. Do not let a team reorg skip it.
Can the extension carry the change?
This is likely what HR meant. Look at the portability rule in 8 CFR 214.2(h)(2)(i)(H). It covers a petition "with a request to amend or extend."
So one filing can request an amendment and an extension together. Some employers time the promotion to match the extension. That saves one filing. It can also delay a raise or a title, as the Reddit worker found.
The rule does not say an employer must wait for the extension. Waiting is a timing choice. Ask HR which path they picked, and why.
How does this look on a typical tech team?
Here are three common promotions. Treat them as prompts for your HR team, not answers.
- Developer to senior developer. Same stack, same office, bigger scope. Often the occupation and worksite do not change.
- QA engineer to QA lead. More planning and some people leading. The share of time on each duty is worth a careful look.
- Developer to engineering manager. Mostly people work. This is the move most likely to need a fresh look at the occupation.
A move to a new city is a separate trigger. Worksite rules have their own details, so raise it on its own.
What should you ask before you say yes?
- Do the new duties fit the occupation on my current LCA?
- Will my worksite or area of work change?
- Will you file an amended petition, and on what date?
- When may I start the new duties?
- Will the next extension also request the amendment?
Get the answers in writing. Then match the dates against your offer letter.
How does Aimpex handle sponsorship?
Our site lists the people we align. They are "SAP specialists, Java and .NET engineers, cloud practitioners, data professionals and quality engineers." We match them "with clearly defined technical responsibilities." Clear duties are also what a petition needs.
The line "Verified Employer — STEM OPT & H1B Visa Pathways Supported" sits on every page of our site. Decoded, the banner's STEM OPT is Science, Technology, Engineering and Math Optional Practical Training: added student work time. On the careers page you will find: "Our E-Verify employer participation supports consideration of qualified graduates." Our pages name Aimpex a "Direct Vendor for Bank of America." The legal page clarifies this. Candidates are not all placed with that bank. The listing implies no endorsement either.
Limits appear on the careers page as well. "Corporate sponsorship does not guarantee registration selection, petition approval or a particular start date." Sponsorship is never a promise of visa selection or approval.
What is the takeaway?
A title change is metadata. A duties change can be a schema change. Review the diff before you merge it.
Sources
- 8 CFR 214.2, eCFR
- 20 CFR 655.730, eCFR
- 20 CFR 655.731, eCFR
- USCIS: H-1B Specialty Occupations
- Aimpex home, Careers, Legal
Not legal advice from Aimpex Resources Group LLC. Our team staffs engineering roles; we do not judge petitions. Before you accept a new title, have an immigration attorney compare it with your filed petition and LCA. Students on F-1 or STEM OPT have one more contact: the school's Designated School Official (DSO).
Aimpex Resources Group LLC was established in 2025 in Lincoln, NE. We offer Enterprise Resource Planning (ERP) Architecture, Supply Chain Analytics and information technology (IT) Staffing Solutions, described at aimpexresources.com. For engineers weighing a promotion, we support qualified technical resources through active corporate H-1B sponsorship and STEM OPT pathways.
Top comments (0)