Nike's Beaverton-or-Bangalore Cut: The 730 US Engineers to Source
Nike's 2026 two-hub consolidation forces US engineers to relocate or leave. Here's the 730-profile pool and the sourcing angle recruiters miss.
Nike is cutting roughly 1,400 Global Operations roles in 2026, most of them in technology, and consolidating everything that survives into two hubs: the Philip H. Knight Campus in Beaverton and the Nike India Technology Center. That is a binary choice for every US-based engineer on the team, and the "won't relocate" side of that choice is where the sourcing edge lives.
What Nike actually announced
Nike is laying off ~1,400 people across Global Operations (just under 2% of the global workforce), with the majority hitting the technology division, and centralizing all surviving tech into Beaverton, Oregon and the Nike India Technology Center. That is per COO Venkatesh Alagirisamy's internal memo, reported by Fox Business and WWD. It is the second cut of 2026, following ~775 roles eliminated earlier in the year, on top of the ~800 US distribution roles Nike disclosed in January across Tennessee and Mississippi facilities. The financial backdrop: Q3 FY2026 net income fell 35% to $520M, EPS to $0.35 from $0.54, and net sales dropped 3% currency-neutral to $11.3B.
CEO Elliott Hill, in the seat since 2024, is refocusing on running and soccer. Non-core platform, materials, and supply-chain tech teams are the ones being cut.
Why "won't relocate" is the actual filter, not "was laid off"
The sourcing edge is not the layoff list. It is the geography filter, because the Nike India Technology Center already exists, which means this restructuring is not offshoring jobs so much as forcing US engineers into a relocation ultimatum most will refuse. Bengaluru is not a lateral move for a Staff engineer in San Jose with a mortgage and a school-age kid. Beaverton itself is a stretch for someone Nike hired remote in 2021.
That is why the standard sourcing move (pull the WARN list, blast InMails) leaves most of the value on the table. The real pool includes:
- Engineers formally on a WARN drop.
- Engineers offered relocation to Beaverton who quietly decline over the following 60 days.
- Engineers offered India relocation whose visa or family situation makes it a non-starter.
- Remote-hired ICs outside Oregon who never had "onsite Beaverton" in their offer letter.
Only the first bucket shows up on public layoff trackers. The other three only surface if you can search by "current company: Nike" plus a location that isn't Beaverton, and pull the list in one pass. That is the exact gap Refolk closes: you describe the person in plain English (something like "current Nike software engineer, US-based, not in Portland metro") and get a ranked shortlist across GitHub, LinkedIn, and the open web without stitching together three tools.
The 730-profile pool, broken down
Refolk's index shows roughly 730 current US-based Nike engineers across core IC and management titles. That is the ceiling for any recruiter working this event.
| Segment | Count | Note |
|---|---|---|
| Total US Nike engineers (IC + mgr) | 730 | SWE, Sr/Staff/Principal, EM, Data, DevOps, SRE, ML |
| Software Engineer (base title) | ~40% of sample | Entry to mid IC, most H-1B exposed |
| Senior + Staff + Principal | ~48% of sample | The expensive, portable layer |
| Engineering Manager | ~8% of sample | Thin mgmt layer, ex-Nike EMs are scarce |
| 2026 announced tech-heavy cuts (YTD) | ~2,175 | 775 (Q1) + 1,400 (Q2) per WWD + Storyboard18 |
| US tech engineer displacement (estimate) | 600 to 900 | Derived, not Nike-confirmed: majority of 1,400 is tech, split across NA/EMEA/APAC |
Two things jump out. First, the seniority mix skews high: nearly half the sample is Senior and above, which is the layer that gets absorbed fastest and commands the highest counter-offers. Second, engineering managers are thin, which tells you Nike runs a relatively flat eng org and that ex-Nike EMs will be rare on the market. If you need one, be first.
The regional signal matters too. Refolk's index shows Nike's US engineering headcount skewing Bay Area and Seattle, not just Portland, which means a meaningful share was hired remote in the last few years and is structurally unlikely to relocate anywhere, let alone Bengaluru.
The H-1B pocket nobody is filtering for
The highest-conversion micro-segment inside the 730 is Nike's H-1B holders, because Beaverton-or-Bangalore is functionally a forced exit for visa engineers who can't easily transfer to India without torching their US immigration progress. Nike filed 94 H-1B Labor Condition Applications in FY2025 - 2026, with top titles including Software Engineer and Senior Production Support WMOS App Engineer.
For those 94 positions, the calculus is not "should I move." It is "how fast can I get an H-1B transfer before my Nike role ends." Recruiters who cross-reference:
- Current company Nike
- US-based location
- Signals of visa status (LCA disclosure, prior OPT, non-US degree)
- Tenure > 1 year (so an H-1B transfer is actually viable)
...are looking at a pre-qualified urgency pool of a few dozen names, not thousands. This is where Nike Global Technology layoffs turn into a targeted list, not a spray.
Beaverton is a thin local market. That is your leverage.
Portland-metro cannot absorb 500+ ex-Nike engineers overnight, which is exactly why Beaverton software engineer sourcing gets easier, not harder, over the next 6 to 12 months. The Philip H. Knight Campus houses about 10,600 employees on a ~400-acre site, and there is no Meta, Google, or Apple campus down the road quietly hoovering up the displaced. The nearest large absorbers are:
- Adidas North America (Portland). Direct competitor, obvious landing spot, and they know it. Expect them to be selective and slow.
- Columbia Sportswear (Portland). Adjacent retail tech, but a smaller eng org.
- Costco Tech (Seattle). A relocation, not a commute.
- Lululemon (Vancouver BC / Seattle remote). Cultural fit, but limited PDX presence.
- Nike alumni networks on Slack and LinkedIn, which historically spin up within weeks of large WARN drops per warntracker.com.
That absorption gap is the real leverage for out-of-market recruiters. A remote-first company offering Bay or Seattle relocation is competing against a small, saturated local market rather than the usual FAANG wall.
Beaverton has no FAANG neighbor. The supply glut is real and it lasts a year.
The waves have a schedule. Use it.
Nike has filed 15 WARN notices between April 2009 and April 2026 covering 4,649 workers across Illinois, Mississippi, New York, Oregon, and Tennessee, and the 2026 restructuring is multi-phase, which means ongoing WARN drops through late 2026 create identifiable outreach windows rather than a single event to time. Michele Adams, VP People Solutions, is the executive who notifies Oregon state authorities, so her signature on a new WARN filing is your leading indicator.
The cadence to watch:
- Wave 1: Q1 2026, ~775 roles, mostly announced.
- Wave 2: Q2 2026, ~1,400 roles across Global Operations, technology-heavy, the current wave.
- Wave 3: Rolling WARN drops through late 2026 as relocation decisions crystallize and Beaverton offers are declined.
Wave 3 is where most sourcing teams miss the boat. Engineers who accept a Beaverton offer in June, discover in August that their partner won't move, and quietly restart their search in September don't appear on any layoff tracker. They show up as "current: Nike, actively interviewing" in profile behavior, which is a signal you can only see if you're indexing continuously. Refolk pulls those signals across GitHub activity spikes, LinkedIn headline edits, and open web mentions rather than making you re-run the same Boolean string every week.
Don't forget the past-company search
The obvious search is "current company Nike," but the highest-value ex-Nike engineers hiring shortlist often lives one step back. Nike cut roughly 1,600 jobs in early 2024, ~775 in early 2026, and now 1,400 more, which means the ex-Nike cohort on the market today spans 24+ months of post-Nike tenure elsewhere. Some are already at Adidas, Columbia, or a Series B in Portland, restless, and one good pitch away from moving.
Search by "Nike" as past company, filter by post-Nike tenure of 12 to 24 months (the classic itch window), and you get a warmer pool than the freshly-laid-off cohort, which is currently being pitched by 40 recruiters a week.
The niche retail tech pool most sourcers ignore
Nike's supply-chain and materials-platform engineers are a specialty retail tech engineer talent pool that maps poorly to FAANG job ladders but perfectly to a specific set of buyers, because Converse footwear engineering is being moved closer to factory partners and materials supply chain work is being absorbed into footwear and apparel supply chain teams. That produces a cohort of WMS, PLM, and materials-informatics engineers with real Nike-scale retail domain depth.
Who wants them:
- Lululemon, Under Armour, Columbia, Adidas NA: direct retail peers with real WMS and PLM investment.
- Chewy, Wayfair: adjacency, especially on warehouse management.
- Levi Strauss: WWD flagged them among recent cutters, but their remaining supply-chain tech org still hires.
These engineers don't self-describe with the right keywords, which is why Boolean strings miss them. They call themselves "Senior Production Support WMOS App Engineer," not "Supply Chain Platform Engineer," and that title only shows up if you're searching semantically. Describe the person to Refolk in plain English ("ex-Nike engineer with warehouse management systems or PLM experience, US-based, 5+ years") and the ranking does the mapping for you.
The bottom line for anyone building this pool
The Nike story is not "1,400 people got laid off." It is "a hub-consolidation is forcing a geographically-bounded talent wave onto the US market in identifiable phases through late 2026, and only a fraction of it will show up on WARN." The 730-profile US engineering pool in Refolk's index is your ceiling. The H-1B sub-segment is your urgency pool. The past-company cohort is your warm pool. The supply-chain specialists are your niche pool. Build all four lists now, in that order, and refresh them every time Michele Adams signs another Oregon WARN notice.
FAQ
How many US-based Nike engineers are actually addressable in this cut?
Refolk's index shows roughly 730 current US-based Nike engineering profiles across core IC and management titles (SWE through Principal, plus EM, Data, DevOps, SRE, and ML). The plausible US-tech-engineer-displacement estimate over the 2026 waves is 600 to 900, derived from the ~1,400 Global Operations cut being majority-tech and split across North America, EMEA, and APAC. Not all 730 will hit the market, but that number defines the realistic ceiling.
Why focus on "won't relocate" instead of the WARN list?
Because the WARN list captures only the formally laid off. The larger and less-contested pool is engineers who are offered relocation to Beaverton or the Nike India Technology Center and quietly decline over the following 60 to 90 days. Those decisions never appear on a layoff tracker, but they show up as location-mismatched "current: Nike" profiles that update their headlines and start interviewing. Filtering by US location outside Portland metro captures both groups in one pass.
Who else in the Pacific Northwest will absorb this pool?
Not many, and that is the point. Adidas North America is the obvious direct competitor in Portland, with Columbia Sportswear as the other local retail-tech landing spot. Beyond that, engineers face a relocation either way: Costco Tech in Seattle, Lululemon in Vancouver BC or remote, or the Bay Area. Out-of-market recruiters offering remote or a Seattle/Bay relo have unusual leverage here because the local market is thin and cannot absorb the volume.
What is the best sourcing angle for the H-1B sub-segment?
Nike filed 94 H-1B Labor Condition Applications in FY2025 - 2026, and those visa holders face the sharpest version of the relocate-or-leave decision because moving to India typically forfeits US immigration progress. Cross-reference current-Nike + US location + visa signals + 12+ months tenure to build a pre-qualified urgency shortlist of a few dozen names. This group converts faster than any other slice of the 730 because their timeline is externally imposed, not preference-driven.
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.