Solutions Architect at Cloud Vendors: H-1B Sponsorship at AWS, Google, and Azure 2026

AWS, Google Cloud, and Azure sponsor H-1B visas for solutions architects regularly — here is exactly how to position yourself and get through the process.

You have the technical chops — you've designed distributed systems, navigated AWS or GCP certification exams, and can whiteboard a cloud migration on demand. The role you're targeting is Solutions Architect at one of the three hyperscalers: Amazon Web Services, Google Cloud, or Microsoft Azure. These companies hire hundreds of SAs annually, they sponsor H-1B visas, and they have immigration machinery that runs these petitions at scale.

The challenge is not whether they sponsor. The challenge is understanding how the specialty-occupation analysis applies to a pre-sales engineering role, how to position your background so USCIS sees a clear technical fit, and how to think about the green card path given multi-year backlogs for certain nationalities. This guide covers all of it, from the H-1B mechanics to the specific dynamics of the SA career track at cloud vendors.

What a solutions architect role looks like at a hyperscaler

The SA title covers a wide spectrum, and where your role falls on that spectrum matters for your H-1B petition.

At AWS, Google Cloud, and Azure, the core SA function is technical pre-sales: you partner with an account team to help prospective and existing customers architect solutions on the vendor's platform. The technical work is real — you run architecture design sessions, build proof-of-concept environments, write reference architectures, and sometimes contribute production code during customer engagements.

Beyond pre-sales, hyperscalers also hire enterprise SAs embedded with named accounts, specialist SAs focused on domains like databases, security, or machine learning, migration architects who lead lift-and-shift or re-platforming programs, and partner SAs who support the ISV and GSI ecosystem. All of these can qualify for H-1B sponsorship, though the petition framing differs.

The distinction that matters for your visa: a role weighted toward technical architecture outputs (diagrams, code, design documents, migration assessments) reads better in an I-129 than a role weighted toward "relationship management" or "quota attainment." Make sure your offer letter and job description reflect the engineering reality.

H-1B specialty-occupation analysis for solutions architects

USCIS evaluates H-1B petitions under a two-part test: (1) the role is a specialty occupation, and (2) the beneficiary is qualified for that occupation. The H-1B Modernization Rule (effective January 17, 2025) clarified the specialty-occupation standard — a job qualifies if it normally requires a bachelor's degree or higher in a specific specialty, not just any bachelor's degree.

For SA roles at cloud vendors, the degree field is typically computer science, computer engineering, electrical engineering, information systems, or a closely related technical field. The petition needs to document why those degree fields are necessary for the specific duties — not just that the employer "prefers" degreed candidates.

Strong petition elements for cloud SA roles:

• Evidence that the role requires designing multi-tier distributed systems (maps to CS/engineering curriculum)
• Documentation of cloud certification requirements (AWS SA Professional, GCP Professional Cloud Architect, Azure Solutions Architect Expert) as proxy evidence of specialized knowledge
• Reference to published AWS/Google/Microsoft job postings describing degree requirements
• Declaration from your hiring manager explaining what technical knowledge the role demands day-to-day

USCIS has issued RFEs on SA roles before, primarily when the petition leans too heavily on the "sales" side of pre-sales. If you receive an RFE on specialty occupation, the response playbook is to document the engineering outputs, not the revenue numbers.

How each hyperscaler runs its immigration program

All three hyperscalers use panel immigration law firms and have dedicated in-house immigration coordinators. Once you accept an offer, you are paired with an immigration attorney who manages the LCA filing (DOL requires certification within 7 calendar days of H-1B filing), the I-129 preparation, and the premium processing decision.

Premium processing in 2026 costs $2,965 and guarantees adjudicative action within 15 business days. Large employers like AWS and Google often pay this fee automatically for new hires on H-1B. Confirm this before signing your offer — some companies only offer it at the employee's request.

The OPT-to-H-1B transition at a cloud vendor

If you're on F-1 OPT targeting a hyperscaler SA role, the calendar math is your first constraint. STEM OPT extensions give you up to 24 months beyond the initial 12-month OPT period, but you must be in a role that meets the STEM OPT employer training plan (Form I-983) requirements — which an SA role at a cloud vendor typically satisfies, since these companies are well-versed in I-983 filings.

The 90-day unemployment limit on OPT applies while you're between jobs. If you're interviewing during OPT and the process runs long, track your days carefully. The clock runs from the date your EAD card authorizes you to work, not from your graduation date.

For the H-1B lottery: hyperscaler SA roles are cap-subject. You register in the lottery window (typically March). If selected, your employer files in April for an October 1 start date. If you're on STEM OPT, the cap-gap provision protects your work authorization from the April 1 lottery registration through October 1 — you don't lose the right to work even if your STEM OPT EAD card expires in that window.

The H-1B Modernization Rule extended cap-gap protection through April 1 (previously the protection ran only through the cap-gap period, with some ambiguity). If you're on the STEM OPT extension and your employer registers you in the lottery, consult your DSO immediately on maintaining proper enrollment verification.

Moving between cloud vendors on H-1B

Once you're in H-1B status at AWS and want to move to Google Cloud — or vice versa — you use AC21 portability (same as any other employer-to-employer H-1B transfer). The mechanics are covered in detail in our H-1B transfer playbook, but the hyperscaler-specific points are:

• All three employers are cap-subject, so transferring between them does not require re-entering the lottery. Your existing cap hit travels with you.
• Prior approval deference under the H-1B Modernization Rule means USCIS officers should defer to prior SA petition approvals at similar roles, reducing RFE risk on transfers between hyperscalers.
• LCA wage levels — USCIS and DOL use the Occupational Employment and Wage Statistics (OEWS) data. SA roles at cloud vendors typically come in at Level III or Level IV prevailing wages, meaning your salary must meet a DOL-determined threshold for the geographic area. San Jose and Seattle have higher prevailing wages than Dallas or Atlanta; your employer's compensation team accounts for this.
• Green card clock does not reset. If you have an approved I-140 at AWS and transfer to Google, you keep your priority date from the AWS I-140, though Google will typically file a new I-140 to establish its own sponsorship. The PERM process starts over at Google.

For comparison with other engineering tracks that move between hyperscalers, see our cloud and DevOps H-1B guide and the sales engineer H-1B guide — the pre-sales engineering case is directly relevant to SA roles.

Step-by-step: from offer to H-1B approval at a cloud vendor

1. Accept the offer (Day 1). Notify your current employer if required (two-week notice). Do not resign before you have the offer letter in writing.
2. Immigration intake (Days 1-7). Your employer's immigration team contacts you. Fill out the intake questionnaire: name, birthdate, passport info, degree details, prior visa history, all prior H-1B approvals.
3. LCA filing (Days 7-14). The employer files the Labor Condition Application with DOL. Standard LCA certification takes 7 calendar days. The LCA must be posted at the worksite for 10 business days (physically or electronically).
4. I-129 preparation (Days 14-30). You provide supporting documents: transcripts, diplomas, prior I-94, all prior H-1B approval notices (I-797), paystubs from current employer if on H-1B. Your attorney prepares the specialty-occupation support letter.
5. I-129 filed (Day 30-45). Employer files I-129 with premium processing. You continue working at your current employer (or on OPT) until USCIS receipt.
6. Receipt notice (Day 31-48). USCIS issues I-797C receipt. If you're transferring from another H-1B, you can start work here under AC21 portability.
7. Approval (Day 45-65 with premium). USCIS approves. Your I-797 approval notice shows the authorized period of employment. If your employer filed for October 1 cap-subject start, the approved petition authorizes work from October 1.
8. Status change (if in US on F-1/OPT). If filing as change of status, USCIS approves the change in one petition — no need for consular processing unless you travel outside the US before approval.

If you're outside the US when the H-1B is approved, you'll need to get the H-1B visa stamp at a US consulate before entering. For guidance on stamping logistics, our H-1B stamping guide covers the India consulate process; procedures are similar at other posts.

The green card timeline for cloud vendor SAs

The green card path for most SA roles at hyperscalers runs through employer-sponsored PERM. Here is what to expect:

PERM (Program Electronic Review Management): Your employer recruits on the open market to document that no qualified US worker is available for the role. PERM audits have increased; large employers like AWS and Google are well-practiced at running audit-proof PERM campaigns. The process takes roughly 12-18 months when including the mandatory recruitment period and DOL processing time (which has been running 18-24 months as of 2026 due to backlogs).

I-140 (Immigrant Petition for Alien Workers): Filed after PERM certification. Premium processing is available for I-140 ($2,805 fee) and gets you an answer in 15 business days. Once your I-140 is approved, your priority date is established. You can keep that priority date even if you change employers (your new employer files their own I-140, but you can "port" the earlier date).

Priority date backlog: This is the real obstacle for nationals of India and China. EB-2 India and EB-3 India backlogs stretch decades in current projections. EB-2 and EB-3 China backlogs are also significant. If you are Indian or Chinese national, your priority date at the time of I-140 approval determines when you can file I-485 (adjustment of status). Nationals of most other countries face negligible wait times in EB-2 and EB-3.

A comparison of sponsorship approaches — large employer PERM vs. consulting-firm pathways — is covered in our consulting vs. product company green card guide.

EB-1C alternative: If you become a senior manager or executive at a multinational — plausible after many years at AWS or Microsoft — you may qualify for EB-1C multinational manager/executive, which is current for all countries and skips PERM entirely. This is typically only relevant at the principal architect or director level.

O-1A alternative: SAs who speak at re:Invent, Next, or Ignite, publish widely-cited technical content, or hold leadership positions in professional associations may build an O-1A case. O-1A has no annual cap and can provide status flexibility while PERM is pending. Consult an attorney who has approved O-1A cases for technical roles — the evidence standard is specific.

Negotiating immigration support into your offer

Large employers have established immigration programs, but you can still negotiate for specifics:

• Premium processing paid by employer. Confirm in writing. Most hyperscalers pay it for new H-1B petitions; some require the employee to pay for transfers and amendments.
• PERM timeline commitment. Ask when the employer typically starts PERM sponsorship (often after 1 year of employment, but policies vary). Get it in writing if possible. See our guide on negotiating green card sponsorship into your offer for language to use.
• Immigration attorney access. Confirm you have direct access to the immigration attorney, not just the HR coordinator. For complex situations (pending I-140, multiple prior H-1Bs, cap-gap complications), you need to talk to the lawyer.

Common mistakes

Treating the SA role as "sales" in your petition. USCIS does not sponsor sales roles. If your I-129 or support letter emphasizes quota, pipeline, or account growth without grounding it in technical engineering duties, expect an RFE or denial. The petition must tell an engineering story.

Assuming all SA specializations get treated identically. A cloud migration architect role is a different petition than a developer relations SA or a partner management role. Make sure your attorney understands which SA track you're on and frames the specialty occupation accordingly.

Skipping the prevailing-wage check before accepting an offer. If the offer is below the DOL prevailing wage for the SA role in your city, your employer cannot file the LCA at that wage level. In practice, hyperscaler compensation is typically well above prevailing wage — but it's worth confirming, especially for roles in high-cost metros.

Not keeping your I-797 approval notices from every prior H-1B. Each time you transfer employers or renew your H-1B, the new petition packages your prior approval history. If you can't produce prior approval notices, get copies from your prior employer's immigration team or via a FOIA request to USCIS before you need them.

Treating your priority date as lost when you change cloud vendors. Your priority date from an approved I-140 does not disappear when you transfer employers. Notify your new employer's immigration team about any approved I-140s from prior employers, and make sure they port the earliest available priority date when filing a new I-140.

Relying on a small staffing firm to place you at a hyperscaler. In-house SA roles at AWS, Google, and Azure mean the hyperscaler is your direct employer and files your H-1B directly. A staffing firm placing you as a contractor at a cloud vendor is a different setup — the staffing firm is the H-1B petitioner, which introduces additional USCIS scrutiny around the employer-employee relationship. In-house is simpler from an immigration standpoint. Our guide on staffing agency vs. direct employer H-1B covers this distinction.

Frequently asked questions

Do AWS, Google Cloud, and Azure actually sponsor H-1B visas for solutions architects?

Yes, all three hyperscalers are among the most active H-1B sponsors in the US each year. Solutions architect roles at these companies consistently qualify as specialty occupations under USCIS criteria because the role requires at minimum a bachelor's degree in a relevant technical field such as computer science, engineering, or information systems. Your I-129 petition needs to demonstrate that the specific duties align with that academic background.

Does a solutions architect role qualify as a specialty occupation for H-1B purposes?

In most cases yes, but the answer depends on how the role is defined in the petition. USCIS looks for theoretical and practical application of highly specialized knowledge. An SA role framed around enterprise cloud architecture, distributed systems design, and technical pre-sales engineering meets this bar more clearly than one framed primarily around PowerPoint and demos. The H-1B Modernization Rule effective January 2025 clarified the specialty-occupation standard and strengthened deference to prior approvals, which benefits SAs transferring between cloud vendors.

How does the pre-sales nature of a solutions architect role affect the H-1B specialty-occupation analysis?

Pre-sales work has historically prompted USCIS scrutiny because examiners sometimes characterize it as sales rather than engineering. The strongest petitions document the technical depth of the role — architecture design sessions, proof-of-concept builds, migration assessments, and code reviews — and tie each duty back to degree-level technical knowledge. If your offer letter describes your job primarily as "supporting account executives," work with your attorney to reframe it around the engineering outputs you produce.

Can I move from one cloud vendor to another on H-1B without re-entering the lottery?

Yes. Lateral transfers between cap-subject employers use AC21 portability. As long as you are in valid H-1B status when the new petition is filed, the new employer files a fresh I-129 and you can start the day USCIS receives it. You do not re-enter the H-1B lottery. Priority dates from any pending I-140 also travel with you.

What is the green card path for solutions architects at cloud vendors?

The most common path is employer-sponsored PERM followed by EB-2 or EB-3. AWS, Google, and Microsoft all have established immigration programs and run PERM regularly for SA roles. Indian and Chinese nationals face multi-year waits in the EB-2 and EB-3 India/China queues; EB-2 NIW self-petition is rarely a shortcut for SA roles since the national-interest prong is harder to establish for commercial pre-sales work than for research. O-1A is a viable alternative for SAs with a strong publication, speaking, or open-source record.

Working through an SA job search at a hyperscaler or navigating the immigration paperwork after an offer? F1Jobs — we help international professionals run this process every week.