Vance Just Froze PERM at 8 Firms. The Microsoft Pool Is 17,006.
The Oct 8 PERM suspension at Microsoft, Adobe, TCS, Infosys, Wipro, HCL, Cognizant, and Capgemini made tens of thousands of H-1B engineers poachable.
On October 8, 2026, VP JD Vance and Labor Secretary Keith Sonderling suspended Microsoft, Adobe, Cognizant, Infosys, TCS, Wipro, HCL, and Capgemini from the PERM program indefinitely. The green card promise that kept tens of thousands of H-1B engineers from picking up a recruiter's call just evaporated. If you source engineers in the US, you have a window measured in weeks before internal mobility teams at those eight firms get their counter-offer scripts approved.
What actually happened on October 8
The Department of Labor stopped processing all pending PERM applications at eight named employers and will not accept new ones. PERM is the Department of Labor labor-certification step that starts most employer-sponsored green cards, so the suspension doesn't revoke anyone's H-1B status, it kills the pathway from temporary visa to permanent residency at those specific sponsors.
The named firms:
- Microsoft
- Adobe
- Cognizant
- Infosys
- Tata Consultancy Services (TCS)
- Wipro
- HCL
- Capgemini
Vance's framing at the announcement was that the companies' representations to DOL were "fundamentally illegitimate and therefore ultimately illegal." Attorney General Todd Blanche stood next to him, which is the detail that matters for anyone betting on a quiet reversal: DOJ involvement, not just DOL, means this is not getting lobbied away in Q1.
The precedent is Cloudera, suspended in May 2026 through the same ETA process. Cloudera hasn't come back. Treat the Oct 8 list the same way.
The scale of what just got unlocked
Across these eight firms, more than 230,000 H-1B approvals and more than 100,000 PERM certifications have been issued since 2009, and the FY25 numbers alone put the actively exposed population into the tens of thousands. This is not a cohort you need to go find. They are already on LinkedIn with "Senior Software Engineer at Microsoft" in the headline.
Here is the dataset worth building a pipeline against:
| Segment | Count | Source |
|---|---|---|
| US engineers with "Microsoft" in headline (SWE/Sr/Staff/Principal/SDE) | 17,006 | Refolk index |
| US engineers/consultants with "Infosys" in headline | 1,026 | Refolk index |
| TCS FY25 H-1B approvals (continuing employment) | 5,505 | Tribune / NFAP |
| Microsoft FY25 H-1B approvals | 5,189 | Tribune / NFAP |
| Microsoft 2025 PERM filings now frozen | 3,682 | peoplematters.in |
| Infosys FY25 H-1B approvals | 2,004 | Tribune / NFAP |
| Wipro FY25 H-1B approvals | 1,523 | Tribune / NFAP |
| 8-firm H-1B approvals since 2009 | 230,000+ | lhscimmigration.com |
The 17,006 Microsoft figure matters most because of geography. In Refolk's index of professional profiles, that pool concentrates in Seattle, Bellevue, and the Bay Area, which is where Meta, Google, Amazon, and Palantir already run dense in-person recruiting. The commute doesn't change. The badge does.
Why Indian IT services workers are more poachable than Microsoft's
TCS, Infosys, Wipro, HCL, Cognizant, and Capgemini workers are a hotter poach target than Microsoft and Adobe workers, not a colder one. Nasscom's own public line is that the number of employees moving from H-1B to permanent residency through PERM at the Indian IT services firms is "relatively limited." That is a tell. Those firms historically used PERM sparingly, so their H-1B base was already green-card-starved before Oct 8. Now there is zero path.
The pitch to a TCS consultant in New Jersey writes itself: your employer never filed, now they can't file, and a non-suspended sponsor can start your PERM today. Indian nationals account for more than 70% of approved H-1B petitions annually, and the India-born EB-2 and EB-3 backlogs are measured in decades. These workers didn't need a reason to listen. They now have one that overrides inertia.
The internal retention teams at TCS and Infosys know this. They are drafting responses. The sourcing window is the gap between the news breaking and those responses landing in inboxes.
The year-5-and-year-6 cohort is the forced-decision population
The sharpest filter is tenure. The H-1B workers closest to the six-year statutory limit whose employer hasn't filed PERM for them yet face a status cliff in months, not years, which turns a "maybe I'd move" conversation into a "I have to move" conversation.
Three signals to filter on:
- Start date 2020 or 2021 at the named employer. That is year 5 or year 6 on an initial H-1B.
- No LinkedIn hint of a priority date. People with approved I-140s often mention it obliquely ("green card process underway," "EB-2 approved"). Absence is a signal.
- Project-embedded titles at the IT services firms. "Technical Lead," "Consultant," and "Senior Consultant" at Infosys and TCS are the roles most dependent on long-cycle sponsorship. Refolk's index shows the Infosys 1,026 heavily weighted toward exactly those titles.
Describing that intersection in a Boolean string is possible but miserable. Describing it in English and getting a ranked shortlist back is what Refolk is for: ask for "US-based Infosys technical leads who started in 2020 or 2021, in metros with Google or Meta offices," and skip the string.
Microsoft's "80% extensions" defense is a sourcing map
Microsoft's public response to the suspension was that approximately 80% of its H-1B filings in the previous fiscal year involved extensions or status changes for existing employees, not new hires. That number was meant to defuse the "replacing Americans" critique Vance made when he noted Microsoft laid off 6,000 US employees last year while receiving 6,300 H-1B approvals and nearly 3,000 green cards. It also functions as a map of the exact profile competitors want.
If Microsoft's FY25 H-1B volume was 5,189 and 80% were extensions, that is roughly 4,151 tenured engineers:
- Three or more years in seat
- Specialized enough that Microsoft paid to keep them
- Promotable enough that the extension was worth filing
- And as of Oct 8, holding paperwork that won't be processed
Microsoft told the government 80% of its H-1B filings were extensions. It also told every competing recruiter which 4,000 engineers to call first.
Cross-reference that against the 17,006 Microsoft-headlined US engineers in Refolk's index and you get a workable top-of-funnel. The 3.3x ratio between visible engineers and FY25 H-1B approvals is the breathing room: for every H-1B holder you reach, you will see roughly three US citizens or green card holders you can route into other searches.
The pitch is "preserve what you built," not "we'll start your green card"
Nothing in the Oct 8 announcement cancels approved I-140 petitions. Workers past the I-140 stage keep their priority date and can port to a new sponsor under AC21. That means the message to a Microsoft principal engineer with an approved I-140 isn't "come work here and we'll sponsor you from scratch." It's "come work here and your priority date survives."
The segments and the right opening line:
| Segment | Immigration status | Right pitch |
|---|---|---|
| H-1B holder, no PERM filed yet | Full restart needed | "Our sponsor filings are not frozen. We can start PERM in week one." |
| H-1B holder, PERM pending at suspended firm | PERM is dead at current employer | "Your current filing will not be processed. A new sponsor restarts it." |
| H-1B holder, approved I-140 | Priority date portable under AC21 | "Join us and your priority date comes with you." |
| H-1B holder, year 5 or 6, no I-140 | Status cliff approaching | "Six-year clock is running. We can file now." |
Recruiters who send the same template to all four segments will convert the first group and offend the fourth. The AC21 portability pitch in particular only lands if you have actually read up on the mechanics, so brief your team before the first outbound goes out.
Where to look beyond the eight firms
Treat the Oct 8 list as the first wave. Federal investigators are examining nine universities over alleged visa abuse, and the Grassley-Durbin letter to TCS from October 2025 telegraphed this suspension almost exactly a year in advance. The EEOC investigation into TCS over alleged firing of older American workers in favor of newly hired South-Asian H-1B employees is still open. The next list is being drafted.
Which means two things for sourcing operations:
- Build persistent saved searches, not one-off lists. The population of H-1B engineers at suspension-exposed employers will grow, not shrink, through 2026.
- Monitor the ETA newsroom and the DOL enforcement docket. Cloudera got added in May. The next addition will not get the same headline Microsoft got, and the firms that catch it first will have a two-week head start.
What the hiring side of this looks like
The eight suspended firms are not going to stop requisitioning engineers. Microsoft, Adobe, and the IT services firms will keep posting roles while their internal counter-offer teams scramble, and the companies poaching from them will post more. The Seattle, Bay Area, and New York engineering markets are already dense with openings against which the suspended-firm cohort is the warmest candidate pool in a year.
FAQ
How long is this sourcing window actually open?
The acute window is roughly two to six weeks, until internal mobility teams at the suspended firms get HR-approved counter-offer frameworks in place. After that, the pool stays warm for all of 2026, but the easy conversions happen in the first six weeks. Recruiters who have named-account pipelines built by mid-November will capture most of the forced-decision cohort.
Is PERM suspension the same as H-1B revocation?
No. The suspension stops the Department of Labor from processing new or pending PERM labor certifications at the eight named employers, which freezes the first step of most employment-based green card paths. It does not touch anyone's current H-1B visa, and it does not revoke already-approved I-140 petitions. Workers remain legal to work at their current employer and legal to transfer their H-1B to a non-suspended employer.
What is the single highest-conversion filter for outbound?
Join date between early 2020 and late 2021 at any of the eight firms, combined with no public indication of an approved I-140. That is the year-5-to-year-6 cohort with no clear green card path, which is the forced-decision population. Layering a metro filter (Seattle, Bellevue, Bay Area, NJ, Dallas) and a title filter (Senior, Staff, Principal, or Technical Lead at IT services firms) gets you to a few thousand names you can realistically work.
Will the suspension list expand?
Almost certainly. Federal investigators are already examining nine universities, Cloudera was added in May 2026 as a precedent, and the enforcement posture under DOL and DOJ makes additional names likely across 2026. Sourcers should treat the current eight as the baseline for a persistent saved search rather than a one-time list, and should monitor the ETA newsroom for the next additions.
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.