Nike's 1,400 Cut Isn't Consolidation. It's an Offshore With a Relocation Fig Leaf.
Nike's two-hub tech reorg pushes 1,400 supply-chain and retail-platform engineers out. Where to find the ones who won't move to Beaverton or Bengaluru.
On April 23, 2026, Nike COO Venkatesh "Venky" Alagirisamy confirmed roughly 1,400 Global Operations layoffs, the majority in technology, and disclosed that Nike will consolidate its global tech footprint into two sites: the Philip H. Knight Campus in Beaverton and the Nike India Technology Center in Bengaluru. Every other Nike tech location now faces a relocate-or-exit choice. For recruiters and engineering managers, that creates a short, geographically scattered window to reach a deep bench of supply-chain, manufacturing, and direct-to-consumer platform engineers before they re-anchor at a competitor or vanish into a Big Four contracting bench.
This is not a generic retail layoff to ignore. The composition of the pool is unusual, and the framing in the memo hides where the real sourcing leverage is.
The two-hub framing hides a one-way flow
Nike's official story is consolidation into Beaverton and Bengaluru. The reality, if you read the memo against the hiring data, is offshoring with a relocation option that almost nobody will take.
The India Technology Center only launched in 2021. It is still hiring aggressively in April and May 2026 for exactly the functions being cut elsewhere: a Supply Chain and Planning Technology (SCPT) team covering long-range demand sensing, sourcing, manufacturing, inventory flow, customer order management, fulfilment, and distribution, including a brand new Blue Yonder TMS team working with Transportation Engineering and Business Operations. ITC roles run on AWS, Docker, CI/CD, OTEL/Splunk, OAuth/OIDC/Okta SSO, Java, Spring Boot, microservices, DDD, Cassandra/MongoDB/DynamoDB, and Terraform.
That is the stack of the people being displaced in North America and Europe. The skills are not redundant. The geography is.
A US senior engineer in Beaverton or Memphis is not taking an India CTC. H-1B reverse-transfer to ITC is impractical at scale. European engineers in EMEA Nike tech sites face the same wall. So treat every non-Beaverton, non-Bengaluru Nike tech employee as a likely exit, not a likely relocator. The "choice" in the memo is paperwork.
The financial why behind the cuts
The Win Now turnaround is not abstract. Q4 FY25 revenues were $11.1 billion, down 12 percent, with NIKE Direct revenues of $4.4 billion, down 14 percent. The damaging line: NIKE Brand Digital fell 26 percent. Q3 FY25 was similarly soft, down 9 percent.
That 26 percent digital collapse is the direct cause of the retail-platform engineer cuts. It also tells you how to frame outreach: these engineers just shipped a failure they did not get to fix. The pitch is not "great engineers shed for cost reasons." The pitch is "come build the platform you weren't allowed to build," at Lululemon, On, Hoka/Deckers, Adidas, Allbirds, New Balance, or Dick's DSG Ventures.
The COO consolidation is the leading indicator
The EVP CTO role at Nike was eliminated effective December 8, 2025. Dr. Muge Dogan exited. Tech was folded under Alagirisamy, a nearly 20-year Nike veteran who now leads Technology in addition to Supply Chain, Planning, Operations, Manufacturing and Sustainability.
When a company puts technology under its operations chief, "automation" stops meaning "build" and starts meaning "vendor and reduce." Alagirisamy's own memo language confirms it: "using more advanced automation where it helps us work better, and building an even stronger end-to-end foundation for future growth." That is procurement language, not platform language.
When a company puts technology under its operations chief, automation stops meaning build and starts meaning vendor and reduce. </pull>
pull When a company puts technology under its operations chief, automation stops meaning build and starts meaning vendor and reduce.
Three practical implications for sourcing.
First, this is the third wave, not the last. Two earlier rounds hit Nike technology in May and June 2025, with some of that work explicitly shifted to third-party vendors per WWD. The spring 2024 round cut 740 in Beaverton against a $2 billion cost-savings target. The August 2025 round took roughly 1 percent of corporate. April 2026 makes four. Expect a fifth.
Second, the named functions being cut are not all "software." Nike is streamlining Air Manufacturing Innovation facilities, moving Converse footwear engineering closer to factory partners (read: Vietnam and Indonesia), and integrating Materials Supply Chain into Footwear and Apparel Supply Chain. Those are mechatronics, PLC, and process-automation engineers, not Java backend devs. They will not surface in your default "software engineer at Nike" LinkedIn filter.
Third, the third-party vendor shift means a large fraction of the displaced ICs will land at Infosys, TCS, Accenture, Deloitte, and EPIQ, often staffed back into Nike accounts as contractors. If you only search current Nike employees, you miss them entirely. If you search by current employer, you miss the Nike domain expertise that makes them valuable.
## The four pools inside the 1,400
Treat the cut as four distinct sourcing pools, not one. Each needs a different query and a different pitch.
### 1. SCPT and Blue Yonder TMS engineers
The Supply Chain and Planning Technology org is the biggest single pool. These are demand-sensing, sourcing, manufacturing, inventory flow, customer order management, fulfilment, and distribution engineers, many with Blue Yonder TMS experience. Adjacent employers that will absorb them fast: Blue Yonder itself, Manhattan Associates, o9 Solutions, Kinaxis, plus retailers running Blue Yonder stacks (Walmart, Target, Lowe's, Albertsons).
The pitch writes itself: same TMS expertise, less travel mandate, no India relocation.
### 2. Direct-to-consumer / Nike Brand Digital platform engineers
These are the engineers behind Nike.com, SNKRS, the Nike app, and Jordan/Converse digital. They run Java, Spring Boot, microservices, AWS, the works. They are the people who watched a 26 percent digital decline land on their reviews. The trade target list is short and obvious: Lululemon, On Running in Zurich, Hoka under Deckers, Adidas in both Herzogenaurach and Portland, Allbirds, New Balance.
This is where most generic sourcing tools fall apart. "Senior software engineer" returns 100,000 profiles. "Senior software engineer with retail D2C platform experience at Nike" returns nothing on LinkedIn because nobody writes their headline that way. This is why we built [Refolk](/): you describe the person in plain English ("ex-Nike Brand Digital engineers in Portland, Java/Spring, ideally SNKRS or Nike app, willing to stay in the Pacific Northwest") and get a ranked shortlist across GitHub, LinkedIn, and the open web.
3. Air MI and Converse manufacturing engineering
The undervalued pool. Air Manufacturing Innovation runs the proprietary cushioning automation. Converse footwear engineering covers process and tooling. These engineers have PLC, mechatronics, and industrial automation backgrounds, often with deep tribal knowledge of specific factory lines. They do not appear in standard "software engineer" searches at all.
Where they go: contract manufacturers in Vietnam and Indonesia (Pou Chen, Feng Tay), Adidas Futurecraft, On's LightSpray automation, plus US industrial-automation employers like Rockwell, Siemens, and Fanuc. A few will land at non-footwear automation shops (Bright Machines, Symbotic, Berkshire Grey) where the PLC and vision-system skills transfer cleanly.
4. Data and AI platform engineers
The ITC job postings cite "DAI/AI platforms" explicitly. Nike has been building an internal AI/ML platform stack on AWS with Splunk/Grafana observability and Terraform-driven infrastructure. The Beaverton-based members of that team who decline relocation are unusually attractive to retail-AI startups and to mid-market retailers just now standing up their first ML platform teams.
The sourcing window is shorter than the WARN window
WARN filings will roll out across multiple states over the coming weeks, but that is the wrong signal to wait on. Three reasons.
The cuts span North America, Asia, and Europe, representing just under 2 percent of the company's global workforce. Most of the European headcount sits outside US WARN jurisdiction entirely. The ICs in EMEA Nike tech sites will be on the market within 30 to 60 days, well before any US filing tells you their names.
US engineers who decline relocation will not all flip their LinkedIn to "Open to Work." Senior engineers with 10+ years at Nike tend to network privately first. By the time their profile updates, they are already in process at Lululemon or Adidas Portland.
And the Big Four landing pad is invisible. An engineer who lands at Infosys as a contractor back into Nike's account in May will show "Infosys" on LinkedIn in June and look like a generic body-shop hire to any sourcer filtering on current employer. The Nike domain expertise is still there. The badge is not.
This is where plain-English search matters more than Boolean. You don't want "current company: Nike." You want "worked on Nike SCPT or Brand Digital between 2021 and 2026, currently anywhere, willing to leave their current role for a senior IC seat at a competitor." Refolk handles that as one query across GitHub, LinkedIn, and the open web, including the contractor-bench profiles that hide the real expertise.
What to do this week
Three concrete moves before the pool re-anchors.
Pull a ranked list of Nike SCPT and TMS engineers in the US and EMEA, filter for those with 5+ years tenure (the relocation refusers), and pitch them into Blue Yonder, Manhattan Associates, and the Walmart/Target supply-chain orgs. The TMS bench is the most concentrated and the fastest-moving.
Build a separate list for Air MI and Converse manufacturing engineers. Do not search by job title. Search by skills (PLC, SCADA, vision systems, mechatronics) and by employer history (Nike + a factory partner name). With Refolk you can describe the profile in one sentence and skip the title-keyword guessing game entirely.
For the Brand Digital pool, anchor outreach on the 26 percent number, not on Nike's name. The pitch is platform ownership at a brand that is still growing direct-to-consumer revenue. On, Hoka, and Lululemon all qualify. Adidas Portland is the geographic no-brainer for engineers who refuse to leave the Pacific Northwest.
The Win Now turnaround at Nike is going to keep producing waves like this for the next 18 months. The April 2026 cut is the cleanest sourcing opportunity of the four so far because it has a hard geographic forcing function. The next one will not be this clean.
FAQ
How many of the 1,400 will actually relocate to Beaverton or Bengaluru?
A small minority. India CTCs are not competitive for senior US engineers, and EMEA-based engineers face both relocation and visa friction for either hub. Treat the relocate-or-exit choice as effectively an exit for anyone outside the two hubs already. Mid-career ICs with mortgages and dual-income households are the safest bet to be on the market within 60 days.
Where are ex-Nike supply chain engineers most likely to land?
Blue Yonder itself, Manhattan Associates, o9 Solutions, and Kinaxis will absorb the Blue Yonder TMS specialists fastest. The broader SCPT pool will scatter across Walmart, Target, Lowe's, Albertsons, and Coupang. Watch Infosys, TCS, Accenture, and Deloitte for ex-Nike ICs landing on benches that staff back into Nike accounts as contractors, which is the most common hidden destination.
Why are Converse and Air MI engineers a separate pool?
They are manufacturing engineers, not software engineers. Air Manufacturing Innovation runs proprietary cushioning automation built on PLCs, vision systems, and process control. Converse engineering is moving closer to Vietnam and Indonesia factory partners. Standard LinkedIn searches on "software engineer at Nike" miss them entirely. Source on skills (PLC, mechatronics, SCADA) and employer history, not titles.
Is there going to be a fifth wave of Nike technology team layoffs?
Almost certainly. The EVP CTO role was eliminated in December 2025 and Dr. Muge Dogan exited. Tech now reports to the COO alongside Supply Chain and Manufacturing. That structural choice favors vendor consolidation over internal platform investment. With four waves already (spring 2024, May 2025, June 2025, August 2025, April 2026), the cadence suggests another round within 6 to 9 months. Build your Nike sourcing list as an ongoing pipeline, not a one-time pull.