What Google H1B Employees Should Do After the Layoffs

USCIS gives H1B workers up to 60 consecutive days (or until your I-94 expiration, whichever is shorter) of authorized stay after your last day of employment. The clock starts on your last day of work as listed on your termination letter — not your notice date, not your severance end date, not the day your badge stops working. This is a critical distinction, because Google's severance packages for affected Cloud employees typically include several weeks of pay, but paid severance does not extend your H1B status. If your last working day is the day the manager broke the news, that's day zero.

During those 60 days you must do one of four things: (1) get a new H1B employer to file a transfer petition, (2) change to a different visa status (H4, B2, F1, O1, etc.), (3) take steps toward leaving the U.S., or (4) have an I-140-based path that allows you to remain. You cannot legally work for anyone during the grace period until a new H1B transfer is filed — filing receipt, not approval, is what gives you work authorization under AC21 portability.

If your I-94 expires before 60 days are up, your grace period ends with the I-94. Pull your most recent I-94 from the CBP website today and write down the date. Don't rely on memory or your old visa stamp.

Your situation is actually better than most laid-off H1B workers, for one specific reason: Google sponsors aggressively, and most of you already have approved I-140s. That changes the math significantly.

H1B transfer (most common path): Any cap-exempt transfer is unlimited and year-round. AWS, Azure, Oracle Cloud, Snowflake, Databricks, Cloudflare, and the entire cloud-adjacent ecosystem actively hire ex-Googlers. Once a new employer files the H1B transfer petition with a receipt notice, you can start work immediately under AC21 portability — you don't need approval. Premium processing ($2,805) gets a decision in 15 business days.

I-140 portability (the underused superpower): If your I-140 was approved more than 180 days ago, you keep your priority date forever, even if Google withdraws the petition. Google's standard practice has historically been to not withdraw I-140s after layoffs, but verify this in writing through your immigration team contact before you leave. With a retained priority date, your next employer can file a new PERM/I-140 and port your old date — meaning you don't restart the green card line. For Indian and Chinese nationals stuck in EB-2/EB-3 backlogs, this is everything.

O-1 visa: Realistic for senior staff, principal engineers, and PMs with patents, published talks at KubeCon/re:Invent, open-source contributions, or significant press. Less paperwork friction than H1B and not subject to the cap. Several immigration firms specialize in tech O-1s and can assess your profile in a 30-minute call.

EB-1A / EB-2 NIW self-petition: If you've led significant infrastructure projects at Google, have GitHub traction, or published, talk to a lawyer about self-petitioning. NIW doesn't require an employer and can be filed concurrently with an H1B job.

H4 with EAD: If your spouse is on H1B with an approved I-140, switching to H4 buys you stability and work authorization while you job hunt at your own pace.

Concurrent H1B / part-time: You can be on H1B with multiple employers simultaneously. A friend's startup filing a part-time H1B is a legitimate backstop while you negotiate with bigger companies.

Day 1-2: - Confirm your exact last day of employment in writing (email HR, get it documented). - Download your I-94 from i94.cbp.dhs.gov. - Request copies of all your immigration documents from Google's immigration team: I-797 approval notices for every H1B, your approved I-140, LCA copies, and PERM documents. They are legally required to provide these and access usually disappears fast after offboarding. - Confirm in writing whether Google will withdraw your I-140.

Day 3-5: - Update LinkedIn but don't broadcast "laid off from Google" — recruiters target the #opentowork tag aggressively, and you'll get higher-quality inbound by signaling "exploring next opportunity in cloud infrastructure." - Reach out to your strongest 10 contacts personally. Most ex-Google Cloud roles get filled through warm intros within 2-3 weeks of a layoff wave. - Apply to companies that have publicly announced they're hiring ex-Googlers — Cloudflare, Databricks, Snowflake, and several mid-stage AI infra startups have run targeted campaigns after every prior Google wave.

Day 6-7: - Get on a call with an immigration attorney, not just your new employer's. Many firms offer free 20-30 minute layoff consults. You want independent advice, especially if you're considering O-1 or NIW. - If you have an Indian or Chinese priority date from 2019 or earlier, this consultation is non-negotiable.

By week 3-4 you should have either a signed offer with a filed H1B transfer, or a clear backup plan in motion. If you're at week 4 with nothing filed, escalate: premium processing, broaden geography, accept a part-time concurrent H1B as a bridge, or prepare a B2 change-of-status application as a safety net (B2 buys 6 months but blocks work — file before day 60).

This is also the month to make harder decisions: Is staying in the U.S. worth a 20% pay cut? Would a Canadian role under the Global Talent Stream (2-week processing) preserve optionality while you wait out the market? Several ex-Google Cloud engineers in the 2024 and 2025 waves took Toronto or Vancouver roles at Shopify, AWS Canada, and Cohere as a 12-month bridge before re-entering the U.S. on L-1.

Don't ignore taxes and benefits. COBRA is expensive; ACA marketplace plans often cost 40-60% less for the same coverage. Roll over your 401(k) within 60 days to avoid forced distribution. If you have unvested GSUs, ask whether your severance includes any acceleration — it usually doesn't, but it's worth confirming.

Miscounting the grace period. It's 60 days from your last day of work, not from when severance ends. People routinely lose 2-4 weeks assuming severance extends status.

Waiting for the "right" job. Holding out for a Staff+ role at another FAANG can burn your 60 days. A filed H1B transfer at a Series C startup preserves your status and can be transferred again later. Status first, optimal job second.

Letting the I-140 get withdrawn. Always confirm in writing what your employer will do. Some companies withdraw automatically after 180 days post-termination. If yours might, file something — anything — that locks in your retained priority date before then.

Traveling internationally during the grace period. Reentering on an H1B without an active employer is risky and CBP officers have wide discretion. Don't leave the country until your new H1B transfer is at least filed, ideally approved.

Not pulling documents before offboarding. Once your Google account is shut off, getting LCA copies and old I-797s becomes a slow, painful process. Pull everything to personal email and cloud storage before your last day.

Forgetting dependents. Your spouse's H4 status and your kids' H4 status depend on yours. Their grace period ends when yours does. If your spouse has an H4 EAD, it stops being valid when your H1B ends.

Rumors have been circulating about further Cloud cuts. If you're in a team that feels exposed, start preparing now while you still have leverage and access:

• Download every immigration document to personal storage today.
• Quietly take recruiter calls. Having an offer in hand the day you're notified compresses your 60-day timeline to a 2-week timeline.
• Get the H1B transfer paperwork pre-staged with a prospective employer's immigration team — many will draft and hold a petition ready to file the moment you're affected.
• Do not resign. Severance, COBRA contributions, and unemployment eligibility all hinge on involuntary termination. A voluntary resignation also eliminates the 60-day grace period entirely under the strict reading of the rule.