Nike Just Cut 1,400 Roles, Majority in Tech. Beaverton Is Open Season.
Nike's April 2026 layoffs released hundreds of ex-Nike technology candidates into Beaverton. Here's how to source them before FAANG closes the window.
On April 23, 2026, Nike COO Venkatesh Alagirisamy told the company it was cutting roughly 1,400 roles across global operations, with "the majority focused in technology." Most tech recruiters saw the headline, filed it under "retail," and kept sourcing. That is the mistake. Beaverton just became the most underpriced senior engineering market in the U.S., and you have about 60 to 90 days before Google, Apple, and Meta absorb the top of the list.
What Nike actually announced
The cut is real, structural, and heavily technical. Nike is trimming about 1,400 roles from its global operations team, roughly 2% of the global workforce, spanning North America, Asia, and Europe. Alagirisamy, who was brought in December 2025 to integrate technology more tightly into operations, framed it as the final phase of CEO Elliott Hill's "Win Now" turnaround. The company is also centralizing its technology footprint into two hubs: Beaverton, Oregon, and the Nike India Technology Center in Bengaluru.
Two implications matter for sourcing.
First, non-hub tech workers are the most exposed. If someone was doing platform, data, or mobile engineering for Nike from Memphis, Boston, or a remote address in Denver, their odds of surviving this reshape are worse than a Beaverton IC's. That is where your outreach yield will be highest.
Second, Beaverton survivors are the reference profile. When you build a Boolean or a prompt, anchor on the stack a current Beaverton Nike SWE ships, not on generic "retail tech."
This also isn't the first cut of the year. Nike eliminated 775 distribution-center positions in January 2026 tied to warehouse automation. Ex-Nike ops-adjacent tech talent has been trickling out since Q1. April just opened the fire hose.
Why most recruiters will miss this pool
Ask a Series B recruiter to list "consumer-scale engineering employers," and you'll hear Netflix, Uber, DoorDash, Instacart, maybe Stripe. Nike almost never comes up. That bias is the entire opportunity.
Nike engineering is not a WordPress shop with a Shopify overlay. Public engineering posts and job specs show a stack that would look familiar at any FAANG platform org:
- Cloud-native, microservice architecture on AWS, rebuilt over five years around observability, security, reliability, availability, and performance
- NoSQL, serverless, containers, AI/ML, GraphQL, CQRS, multi-region
- Specific Beaverton SWE JD anchors: HBase, Spark Streaming and Spark SQL, Elasticsearch on AWS, Terraform for IaC
- Autonomous domain teams running Agile, CI/CD, DevOps
- Public OSS at github.com/Nike-Inc including Willow (Swift logging) and Elevate (Swift JSON parsing)
The SNKRS app alone is a traffic-spike system most B2B SaaS engineers have never touched. Drop days generate load patterns that ticketing, streaming, and fintech companies would kill for on a resume, if only they thought to search for it.
The Nike engineering team has said the quiet part out loud on its own blog: Portland "is not Silicon Valley" and the metro is "not widely associated with the incredible technical talent" the team sees internally. They have been fighting that perception for years. Your job is to exploit it before it corrects.
Build the Boolean, then throw it away
You can start with the obvious string: "Nike" AND (Beaverton OR Portland) AND (Spark OR HBase OR GraphQL OR Terraform). That will get you a few hundred LinkedIn results and roughly the same list every other recruiter who reads Bloomberg will pull this week.
Boolean tops out fast on a job like this because the real signal is not on LinkedIn headlines. It's in:
- Author bylines on medium.com/nikeengineering
- Commit history on github.com/Nike-Inc repos
- Conference talks (AWS re:Invent, KubeCon) with a Nike affiliation
- Nike Tech Talks speakers and attendees, a public Portland series the company runs
- Nike alumni already at Salesforce Portland, Vacasa, Jama, Smarsh, and Navan, who make excellent referrers even if they aren't the hire
This is where plain-English search beats string logic. Instead of stacking eight OR clauses and hoping the profile is honest, you want to ask something like "engineers based in Portland or Beaverton who worked on Nike SNKRS or Nike.com traffic infrastructure in the last three years, with GraphQL and AWS experience," and get a ranked list back. That is exactly the friction Refolk was built for: you describe the ex-Nike technology candidates you want across GitHub, LinkedIn, and the open web, and the shortlist comes back ranked, without the Boolean gymnastics.
The comp arbitrage is real, and it has a number
Here is the part most recruiters outside the Pacific Northwest do not price correctly. In Q2 and Q3 2024, Salesforce's Portland engineering hub pulled three Senior Staff ML Engineers out of Nike's Digital Innovation division. Their new total comp landed in the $285K to $310K range. Nike's Portland bands for the equivalent level sat at $210K to $230K.
That is a 35 to 40% uplift on the same zip code, same commute, no relocation. Multiply it against Oregon's 9.9% top marginal income tax, which creates a 12 to 15% total-comp penalty versus Washington State, and a Seattle-based remote offer looks even better to a laid-off senior IC with a mortgage in Lake Oswego.
If you're a mid-market or Series B recruiter and you think you can't compete with FAANG on cash, look again at the Nike bands. You probably can, and the candidate will treat your outreach as a raise rather than a lateral.
Where ex-Nike engineers actually go
Refolk's index shows about 674 U.S.-based engineers, EMs, and data professionals with Nike in their headline. Among those who have already moved on, the top current employers are Google, Apple, and Meta, three each in the sample, with the geographic center of mass shifting from Portland to the SF Bay Area and Seattle.
Two things follow from that.
One, the quality bar is validated. If Google and Apple are hiring ex-Nike ICs at the staff level, your skepticism about "apparel engineers" is misplaced.
Two, you are on a clock. The strongest 10 to 20% of this April cohort will be off the market inside a quarter. Anyone still open in September is either geographically constrained to Portland, holding out for a specific domain, or has a comp expectation that FAANG passed on. All three are fine profiles for a mid-market hire, but they are not the top of the list.
The best 200 people from this layoff will be gone by Labor Day. The next 400 are your actual pipeline.
</pull>
## The outreach frame that works
Alagirisamy was explicit that the layoffs are part of an ongoing restructuring, not a new strategic direction. In plain English: these engineers were cut for org-shape reasons, not performance. Your first message should respect that.
Three things to do, and one thing to stop doing.
Do lead with the specific work. "Saw your post on the Nike Engineering blog about multi-region failover on GraphQL" beats "noticed you were impacted" every time. It signals you read the byline, not the WARN notice.
Do name the traffic pattern. Engineers who worked SNKRS drops, checkout, or Nike.com peak events have a story most recruiters cannot even ask about. Ask about it.
Do offer a Seattle-remote or Bay Area-remote option if you have one. The Oregon tax math and the Salesforce Portland precedent both push in that direction.
Do not lead with "impacted by layoffs." It reads as ambulance-chasing, and half the pool you want was not actually cut. They just saw the memo and updated their calculus.
## The adjacent pool nobody has connected yet
If you're building a Portland-metro pipeline anyway, layer Intel Hillsboro next to Nike. Intel's Oregon footprint is about 22,000 employees with roughly 8,500 in software and systems engineering, and Hillsboro has been shedding fab and systems talent all year. Nike gives you GraphQL, Spark, and consumer scale. Intel gives you kernel, driver, firmware, and hardware-adjacent systems. Together they cover almost any infra or platform req you'd open in 2026.
Salesforce Portland, Vacasa, Jama Software, Smarsh, and Navan are all hunting the same Principal Platform Engineers you are. They are your competition today and, on a longer view, your future clients when their own reshapes hit. Track them.
This is a case where "Nike digital talent" is the wrong search phrase and "engineers in the Portland metro who ship consumer-scale systems" is the right one. Refolk handles that distinction natively because you describe the person, not the keyword. Ask for "ex-Nike technology candidates who contributed to Nike-Inc open source and now show as Open to Work," and you get exactly that set, not the 40,000 profiles a LinkedIn recruiter search returns when you type Nike into the company field.
## What to do this week
Concretely, in the next five business days:
1. Pull the Nike Engineering blog author list going back 24 months. That is roughly 40 to 80 named senior ICs, all with public technical writing samples.
2. Cross-reference against github.com/Nike-Inc contributors. Anyone with commits in the last 12 months who has updated their LinkedIn tenure to "past" is a priority reach.
3. Build a Portland/Beaverton geo filter with a 90-mile radius so you catch Vancouver, WA and the Salem commuters.
4. Draft two outreach templates: one for the "still at Nike, watching the reshape" profile, one for the "just left" profile. They are different conversations.
5. Ping your Nike alumni at Salesforce, Vacasa, Jama, Smarsh, and Navan. Referrals out of this cohort will close faster than cold outbound.
Nike layoffs 2026 will be a footnote in a Challenger, Gray & Christmas report by December, sitting inside the 52,000+ tech-sector cuts already booked this year, up 40% year-over-year. But for a 60- to 90-day window, sourcing Nike engineers in Beaverton is the cleanest single-employer arbitrage on the board. Move accordingly.
## FAQ
### How many of the 1,400 Nike layoffs are actually engineers?
Nike has not publicly broken down the technology share by count or location. What we know is that COO Venkatesh Alagirisamy said the majority of the 1,400 cuts are in technology, and that non-hub locations are more exposed because the company is centralizing on Beaverton and Bengaluru. A reasonable working assumption is that several hundred U.S.-based technology roles are affected, weighted toward mid-tier sites and remote workers outside the two surviving hubs.
### Is Nike's engineering stack actually competitive with FAANG?
Yes, more than most recruiters assume. Nike engineering publicly runs cloud-native microservices on AWS, uses GraphQL, CQRS, NoSQL, serverless, containers, and multi-region architectures, and shipped an OSS Swift stack. Beaverton SWE job specs cite HBase, Spark Streaming and SQL, Elasticsearch, and Terraform. Google, Apple, and Meta already hire out of this pool at senior levels, which is the strongest possible external validation.
### Why is Portland comp so much lower than Seattle or the Bay Area?
Two reasons. Oregon has a 9.9% top marginal income tax that creates a 12 to 15% total-comp gap versus Washington State, so employers price accordingly. And Portland does not have a critical mass of FAANG offices bidding senior IC comp up, so local bands stay flat. That is exactly why a Salesforce Portland or a Seattle-remote offer can deliver a 35 to 40% uplift on the same role in the same metro.
### What's the fastest way to build a targeted ex-Nike shortlist?
Skip the Boolean gymnastics. Combine three signals: Nike Engineering blog bylines, github.com/Nike-Inc commit history, and LinkedIn tenure changes in the last 12 months, filtered to the Portland metro. Tools like Refolk let you describe that composite in plain English and return a ranked list across GitHub, LinkedIn, and the open web in one query, rather than running three separate searches and reconciling them by hand.