Nike Cut 90% of SNKRS. Beaverton's Drop Engineers Are in Play.

Nike announced ~1,400 cuts this week and buried the lede in a single sentence: "the majority in Technology." If you source engineers and your tracker still flags Nike as "Apparel & Footwear," you are about to miss one of the cleanest, most geographically concentrated releases of senior consumer-app talent of the year.

The competitor crowd chasing Meta, Amazon, and Oracle alumni cannot see this pool with their default filters. That is the entire opportunity.

What Nike actually said

The memo came from EVP and COO Venkatesh Alagirisamy: "Collectively, these changes will result in a reduction of approximately 1,400 roles in Global Operations, with the majority in Technology." The cuts span North America, Asia, and Europe and represent just under 2% of Nike's global workforce.

The structural piece matters more than the headcount. Nike is consolidating its technology footprint into exactly two hubs: the Philip H. Knight Campus in Beaverton, Oregon, and the Nike India Technology Center. Everywhere else is being wound down or absorbed. The rationale Alagirisamy cited was "more advanced automation" and simplification, not performance. These engineers were not managed out. They were rewritten out.

This is Nike's third round in 2026 alone: 775 in January, then 1,400 in April, with this latest wave aimed squarely at tech. It lands during the final phase of CEO Elliott Hill's Win Now turnaround, launched in December 2025, and follows a Q3 FY26 print where net income fell 35% to $520 million on $11.3 billion in sales. This is structural, not a one-off correction.

The SNKRS detail nobody indexed

Here is the part the apparel press undersold. According to a report from House of Heat, Nike has cut up to 90% of the staff behind the SNKRS app, redirecting the drop strategy toward third-party platforms including Shopify and EQL. One source estimated that 90% of teams connected to SNKRS launches, including product, engineering, program management, and launch operations, were impacted.

Stacy Devino, a former Principal Engineer on the SNKRS team, posted publicly on LinkedIn that the team had been "obliterated." A named, senior, public ex-Nike principal IC is the single best starting node a sourcer could ask for. If you build a second-degree graph off Devino's connections, filter for Greater Portland, and intersect with Nike tenure of 5+ years, you have a shortlist before lunch.

Nike's own statement says SNKRS will be "powered by a unified Nike App and SNKRS engineering team." Read that again. The team is being merged, not preserved. The "unification" is the layoff.

90%

Why this archetype is worth chasing

SNKRS engineers ran extreme-burst-traffic drop infrastructure. Bot defense. Queueing. Raffles. Real-time inventory reconciliation under load patterns closer to Ticketmaster than to a normal e-commerce site. That is not a skill set you find on a generic "senior backend, e-commerce" search.

The buyers for this talent are obvious once you say it out loud: Shopify and EQL (literally named as Nike's pivot partners), Fanatics, StockX, GOAT, Whatnot, TikTok Shop, and the ticketing-adjacent crowd including SeatGeek and DICE. Lululemon, On Running, Hoka/Deckers, Crocs, and Dick's GameChanger will fish in the same pond for digital roles. Fintechs running flash-sale style infrastructure (think NFT drops, IPO allocation tooling) should be in this pool too and mostly are not.

The Nike tech stack, per active Nike Platform job specs, is Java, Python, Golang, or Node.js on RESTful microservices in AWS (S3, Route 53, ELB/ALB, SQS/SNS), with Docker and Kubernetes. Streaming is Kafka, Pulsar, Spark Streaming, or Flink. The SNKRS and Nike App iOS surface is Swift. Nike Engineering open-sourced Willow, a Swift logging library, and Elevate, a Swift JSON parser. Contributors to those repos are a high-precision filter you can run today.

The arbitrage: Nike is "Apparel" on LinkedIn

This is the part most sourcing tools get wrong. Nike's LinkedIn industry code is Retail Apparel and Fashion. Default "tech layoff" filters and most automated tracker feeds (Layoffs.fyi, TrueUp, the various Crunchbase pulls) either skip Nike entirely or list it without the engineering signal.

If your sourcing workflow is "alert me when a tech company does a RIF," you will not see this until Q3, by which point Shopify and Fanatics will have already cleared the senior bench. The arbitrage window is the next four to six weeks while the apparel framing still holds.

This is exactly the kind of cross-industry pattern that breaks Boolean. You need to ask for the person, not the filter. Refolk is built for this: describe in plain English the engineer you want, and it searches GitHub, LinkedIn, and the open web together. "Former Nike SNKRS or Nike App engineer in Greater Portland with 5+ years tenure, Swift or Kotlin or Kafka, recently active" returns a ranked shortlist regardless of what industry code LinkedIn glued onto the employer.

A concrete sourcing plan for the next two weeks

You do not need a clever framework. You need to run three queries before your competition figures out Nike is a tech company.

1. The GitHub spine

Pull contributors to the Nike Engineering org repos over the last five years. Willow, Elevate, Wingtips, Riposte, and Harbormaster are the highest-signal entry points. Cross-reference contributor profiles for Portland, Beaverton, or "Greater Portland Area" locations. This catches platform and mobile engineers who shipped code, not managers who shipped slide decks.

The GitHub-to-LinkedIn join is where most workflows leak. Engineers use different names, no employer in their GitHub bio, sometimes no public email. This is the second place Refolk earns its keep: it does the GitHub-to-LinkedIn-to-current-location reconciliation in one pass instead of forcing you to maintain a spreadsheet.

2. The LinkedIn pull, done right

The naive query is "Past company: Nike + Greater Portland." That returns 20,000 results, most of them in retail, supply chain, or marketing. Layer in skills (Swift, Kotlin, Java, Kafka, AWS, Kubernetes), tenure (5+ years at Nike), and the "Open to Work" signal. Then prioritize titles that include "Principal," "Staff," "Senior Software Engineer," "Engineering Manager" (the player-coach tier), or "SRE."

Tenure under two years at Nike is mostly noise. Five-plus years is institutional knowledge: people who ran a Cyber Monday, shipped a Jordan drop, and debugged the queue at 3 a.m. when the Travis Scott AJ1 dropped. That is the differentiated artifact.

3. The named-node graph

Start from Stacy Devino on LinkedIn. Pull her recent activity, comments, and the people reacting to her posts. Ex-coworkers cluster in the comments section after a layoff. This is the highest-signal sourcing surface that exists for the next 30 days and it requires zero tooling.

The "unification" is the layoff. Read the press release like a sourcer, not a fan.