Refolk
May 15, 2026·8 min read

Nike Cut the CTO Seat and 1,400 Roles. Source the SNKRS Bench Now.

Nike's April 2026 tech cuts gutted SNKRS, closed Atlanta, China, and Gdańsk, and eliminated the CTO seat. Here's how to source the displaced engineers.

sourcing Nike engineersSNKRS app engineers hiringNike tech layoffs 1400recruit retail technology engineersNike Atlanta tech center layoffs
Nike Cut the CTO Seat and 1,400 Roles. Source the SNKRS Bench Now.

On April 23, 2026, Nike announced roughly 1,400 role cuts, "with the majority in Technology." Two and a half weeks later, Hypebeast and House of Heat filled in the part Nike's press release wouldn't: the SNKRS app team, the people who keep launch-day traffic from collapsing under its own weight, was effectively gutted. If you hire mobile commerce, anti-bot, or flash-sale infrastructure engineers, this is the cleanest displaced-senior-engineer event of the year.

The window is short and the cohort is unusually well-defined. Three tech sites are going dark, Beaverton and the Nike India Technology Center are the only survivors, and the CTO seat itself was eliminated. That last detail is the one most recruiters are underweighting.

What Nike actually did on April 23

The official memo from COO Venkatesh Alagirisamy talks about sharpening "alignment with the business," building "leaner teams," and consolidating the "technology footprint." Translated into hiring-manager English: Nike is collapsing its global tech presence into two hubs (the Philip H. Knight Campus in Beaverton and the Nike India Technology Center in Bengaluru) and shutting down everything else.

Per Retail Dive, WWD, and Oregon outlets, the sites being wound down are:

  • Atlanta Technology Center in West Midtown, opened in 2023, ~16,400 sq ft, built for ~80 to 100 employees across logistics/supply chain, cybersecurity, and AI/ML centers of excellence.
  • Nike Gdańsk Technology Center in Poland, opened with public fanfare a few years back.
  • China technology operations.

The cuts represent less than 2% of Nike's global headcount, but they are dramatically over-indexed on US and EMEA technology ICs and managers. The financial backdrop tells you why retention budgets aren't coming: Q3 FY2026 net income fell 35% year over year to $520M on roughly flat $11.3B in sales.

1,400
Roles cut on April 23, with the majority in Technology
Nike's tech footprint is consolidating into just two hubs: Beaverton HQ and the Nike India Technology Center.

The CTO elimination is the real story

Headcount numbers are easy to publish, easy to read, and easy to overweight. The structural change buried in the Retail Dive coverage is more important for anyone trying to convert a Nike engineer this quarter: there is no CTO anymore. Technology reports up through Alagirisamy as COO.

That means two things for your pitch. First, retention counters will be unusually weak, because there is no executive in the room whose job is to fight for tech headcount and equity refreshes. Second, every displaced engineer now has a clean, honest narrative for why they're leaving, which makes outbound reply rates spike for the next 60 days. They don't have to spin it. The org chart did it for them.

Lead with "you'll have a CTO again." Comp is the second sentence, not the first. </pull> If you're an engineering leader making outbound calls personally, that one line outperforms every variation of "we'd love to chat about an exciting opportunity." It names a thing the candidate is actually angry about. ## The SNKRS engineers are a tiny, specific labor market House of Heat reported that roughly 90% of the teams tied to SNKRS launches (product, engineering, program management, launch ops) were affected. Nike hasn't confirmed a number. Former Nike engineer Stacy Devino went on LinkedIn and described the SNKRS org as "obliterated," and added a technical detail worth highlighting: launch-day traffic on SNKRS is effectively a self-inflicted DDoS. Read that the way a hiring manager should read it. These engineers have shipped, at consumer scale: - High-concurrency queueing under traffic spikes that look like attacks. - Bot and sneaker-bot mitigation (the sophisticated kind, not Cloudflare-out-of-the-box). - Raffle integrity and fraud prevention on inventory worth millions per drop. - Inventory reservation and oversell protection at flash-sale concurrency. - Mobile clients that have to degrade gracefully when the backend is on fire. That's a labor market measured in the low thousands globally, not tens of thousands. If you're sourcing for Ticketmaster, Supreme, StockX, GOAT, Shopify Plus drops, Fanatics, Live Nation, Klarna, or anyone running app-based scarcity drops, the people who survived SNKRS Saturday mornings are your shortlist. The trick is finding them without spending three weeks on Boolean strings, which is exactly the friction [Refolk](/) was built to remove: describe "former Nike engineers who worked on SNKRS launch infrastructure, queueing, or bot mitigation, US-based" in plain English and get a ranked list.

refolk prompt: Engineers and EMs who worked on SNKRS, drops, queueing, or bot mitigation at Nike, currently in the US or Poland, open to remote. note: You'll get a ranked shortlist across LinkedIn, GitHub, and conference talks, with the SNKRS-adjacent signal weighted above generic "Nike mobile" matches. </refolk>

Don't sleep on the Poland cohort

Gdańsk is the underrated piece of this. The Nike Gdańsk Technology Center had a public opening, a recognizable cohort, and a LinkedIn-filterable office location. Engineers there skew toward backend, platform, and integration work, and many are open to remote EU contracts that US-based startups can offer through an EOR. The competitive set hunting them is narrower than the US set, so your reply rates will be higher if you move first.

Atlanta is the sleeper geo for cyber and ML

Most coverage treats the Atlanta closure as a footnote. It isn't. The Atlanta Technology Center, opened in 2023, was explicitly built around three centers of excellence: logistics/supply chain, cybersecurity, and AI/ML. It was led by Dr. Mona-Lisa Pinkney, Nike's senior cybersecurity leader and co-founder of Nike's Black Employees in Technology Network. That site produced senior security architects and applied ML engineers, not generic commerce devs.

The natural absorbers in Atlanta are obvious if you've sourced the city before: NCR Voyix, Mailchimp/Intuit, Greenlight, Calendly, Salesloft, and the federal contractor belt. If you're hiring detection engineering, fraud ML, or supply-chain ML in the Southeast, this is the cleanest 60-to-80-person cohort you'll see all year, and Pinkney's network is the high-leverage sourcing node, because the cybersecurity employee resource group she co-founded will be the place a lot of this talent regroups.

This is also where the "recruit retail technology engineers" framing gets too narrow. Half of what came out of Atlanta isn't retail tech at all. It's enterprise security and ML that happened to have a Nike badge.

The Shopify and EQL tell

Multiple outlets (HotNewHipHop, Rolling Out, Hypebeast follow-ups) reported that Nike is redirecting parts of its drops and retail tech stack toward third-party platforms. EQL and Shopify show up most often. Shopify Plus has run drops at this scale before. EQL is purpose-built for raffles and queues.

The sourcing implication: the displaced SNKRS engineers were, in many cases, the people whose internal projects got killed in favor of these vendors. They have detailed, fresh opinions about both. That makes them unusually high-conversion targets for:

  • Shopify itself, especially Hydrogen, checkout, and bot-defense teams.
  • EQL and direct competitors.
  • Headless commerce vendors (commercetools, Hydrogen partners, fast.co successors).
  • Any DTC brand running scarcity drops on Shopify Plus that needs a senior IC who has actually been in the war room at 10:00am Eastern on a Jordan launch day.

If you're at one of those companies, the conversion window is roughly 60 days from the rolling notifications. After that, the strong ones are gone.

How to actually run the search this week

A few practical notes from running this kind of displaced-cohort search before.

Don't filter only on "Nike"

A US search for engineering ICs and managers with Nike in their profile keywords returns roughly 450 matching profiles in our index, concentrated in the SF Bay Area, NYC, Chicago, Seattle, and Boston. Historical destinations include Google, Apple, JPMorgan Chase, and Dropbox. That's a useful sourcing pool and a competitive-poach map for who's been quietly hiring out of Nike for years. But Nike-only is too narrow. Add Converse, Jordan Brand, and the contractor names that show up under Nike umbrella projects. slug: dw55qmg51v

450
US engineering ICs and managers with Nike in their profile
Concentrated in SF Bay Area, NYC, Chicago, Seattle, and Boston. The April cuts make most of them sourceable on a 60-day window.

Weight on launch and platform signals, not titles

Titles at Nike are noisy. "Senior Software Engineer II" tells you almost nothing about whether someone shipped SNKRS queueing or maintained an internal Java service that nobody outside Beaverton has heard of. Weight your search on talk titles, GitHub activity, patents, and public posts that mention drops, raffles, queueing, traffic shaping, bot defense, or specific event days. Refolk's plain-English search is built for exactly this kind of "skill, not title" sourcing: you describe the behavior you want and the system ranks profiles on actual signal across GitHub, LinkedIn, and the open web, not job titles.

Map the alumni network before the cohort scatters

Within four weeks of a layoff round this size, half the cohort will have updated their LinkedIn to a new company. That's good for them, painful for sourcing, because they stop showing up in any "former Nike" search that doesn't aggressively reweight on tenure. Build the list now, while the "Open to Work" frames are still on the profile photos. If you're using Refolk for the Nike Atlanta tech center layoffs cohort specifically, run the query this week, save the shortlist, and re-run it on day 30 and day 60 to catch the laggards.

India is the wrong place to look

The Nike India Technology Center is a winner in this restructure, not a casualty. India-based recruiters chasing senior Nike IC and management talent are facing a harder market post-layoff, not easier, because Beaverton is moving more work to Bengaluru, not less. The actually-displaced pool is the US, Poland, and China engineers. If your pitch is India-based, you're better off going after Flipkart, Myntra, and Meesho commerce alumni than expecting an exodus from Nike India.

The 60-day shape of this

Nike notifications are rolling now. The COO memo is the public artifact, the CTO seat is gone, and the financial picture says no one is getting a competing offer that beats $200K base plus refresh. By mid-July, the strongest SNKRS and Atlanta cyber engineers will be off the market. By Labor Day, the cohort will be substantially placed.

If you're hiring for SNKRS app engineers, flash-sale infrastructure, anti-bot, or applied ML in the Southeast, the work to do this week is small and concrete: name the three roles you'd open today if you had the right candidate, write the plain-English search, and start the outbound. The 1,400 number isn't the headline. The structural reasons retention won't hold them, that's the headline.

FAQ

How many of the 1,400 Nike layoffs were actually engineers?

Nike said "the majority in Technology" without breaking out a percentage. Based on the site closures (Atlanta, Gdańsk, China tech ops) and the SNKRS-specific reporting from House of Heat suggesting up to 90% of launch-adjacent teams were affected, a reasonable working estimate is that 900 to 1,100 of the 1,400 are tech roles, weighted toward ICs and middle management. Treat that as directional, not official.

Why does the CTO seat being eliminated matter for sourcing Nike engineers?

Because retention counter-offers are typically driven by the CTO's office. With technology now reporting through the COO and the COO's public memo emphasizing automation and leaner teams, displaced engineers have a hard time getting a credible "we'll fix it, stay" pitch. That translates into higher outbound reply rates and shorter time-to-offer-accept than you'd see in a normal RIF.

Where should I look for ex-SNKRS engineers specifically?

LinkedIn office filters for Beaverton, Atlanta, and Gdańsk, plus conference talks (QCon, Strange Loop, AWS re:Invent retail tracks) where Nike engineers presented on queueing, drops, or scale events. The strongest signal isn't the Nike badge, it's a public talk or post about launch-day traffic, raffle integrity, or bot defense. Refolk will rank on those signals if you describe them in the query, instead of you running Boolean strings for a week.

Is the Nike India Technology Center hiring or laying off?

Hiring, on net. It's one of the two surviving tech hubs in Nike's new footprint, alongside Beaverton, and the consolidation is moving work into it rather than out of it. If you're recruiting in Bengaluru, expect Nike India to be a competitor for senior talent over the next 12 months, not a source of it.

Read next