Nike's "Pace" Plan Is Restructure #3. Beaverton Has 15 Months.

On October 2, 2026, Elliott Hill told Nike employees that "fewer roles across Nike" are coming, that notifications begin in calendar 2027, and that the company does not yet know how many roles or where they sit. That is the third restructuring in 24 months and the first one that pre-announces layoffs 15 months out without a target list. For sourcers, that is not a problem. It is the buy window.

The 15-month window Elliott Hill just handed every competitor

Hill's "Pace" memo gives external recruiters a 15-month head start on the entire Beaverton tech org, because Nike itself has told engineers it does not yet know which roles will be cut. Every tenured SWE in Beaverton now sits in Schrödinger's job until a WARN filing lands in 2027, and the information advantage is zero: their recruiter knows exactly as much as they do, which is nothing.

The plan itself is specific where it matters for sourcing and vague where Nike wanted it vague:

• Four reported geographies collapse into three (Americas, Asia Pacific and Greater China, EMEA), effective fiscal 2028 which begins in June 2027.
• $2.5B in cost savings over four years, with $1B earmarked as "employee-related costs."
• ~$1B in pretax restructuring charges through fiscal 2031, on top of ~$300M in severance already recognized in fiscal 2026.
• A new corporate campus in Bengaluru, India, announced in the same memo that pre-announced the cuts.

Q1 FY27 revenue fell 4% to $11.21B, Greater China dropped 26%, the stock is off more than 40% in 2026 alone, and Nike was removed from the S&P 100. The point for a sourcer is not whether "Pace" works. The point is that an engineer who has already watched the stock halve, lived through two restructures, and been told round three is coming has a very different reply rate than an engineer at a company that is quietly fine.

Restructure #3 in 24 months breaks the "it won't be me" bias

The reason "Pace" is a sourcing event and not just a news event is that it is the third wave in two years, and survivors of three waves leave voluntarily at a materially higher rate than survivors of one. The "it won't be me" bias is a round-one phenomenon. By round three it inverts.

Here is the sequence:

1. December 2023 / 2024 execution: $2B cost plan announced under then-CEO John Donahoe. 1,600 cuts globally, 740 at the Beaverton HQ (46% of the total), disclosed through Oregon WARN filings in the June wave. Earlier in 2026, 775 positions were also eliminated at domestic distribution centers for automation.
2. April 2026 "Win Now": ~1,400 global ops roles cut, "with the majority in technology," consolidating tech work at Beaverton and the Nike India Technology Center. COO Venkatesh Alagirisamy's memo named the two surviving tech hubs. Nike published no role count per team or per location, so Oregon WARN did not help this time.
3. October 2026 "Pace": TBD scope, notifications starting 2027, running through fiscal 2031.

Two of those three rounds were tech-heavy. The pattern an engineer sees from inside is: survived 2024, survived Win Now, now watching a four-year clock. The CEO changed in between (Hill replaced Donahoe). Reorg boundaries changed. Reporting lines changed. The thing that did not change is that tech is where the money is.

2,813

Where the 2,813 Nike tech profiles actually sit

In Refolk's index, 2,813 current and recent Nike tech profiles cluster disproportionately in Bengaluru, Beaverton, San Jose, and Pune, which maps almost exactly onto the two hubs Alagirisamy named in April. That is the pool to work before the first WARN notice lands in 2027.

The number to internalize is the gap between the India legal entity and the actual India tech footprint:

Two derived numbers do most of the work. First, 40% of "Pace" savings are coming from people. Second, in the last comparable round, 46% of the cuts landed at the Beaverton HQ. If both ratios hold, Beaverton is still the center of gravity even as Bengaluru expands. That is the arbitrage: Nike is telling the market "India growth, US pain," and the names in both locations are the same list.

"India is growing" does not mean "India is safe"

The non-obvious read on the Bengaluru campus announcement is that NITC engineers are the second-best cohort to source, not an off-limits one. Nike is asking India to grow 33% to 4,000 heads by 2027 while absorbing reorg'd work from laid-off Beaverton peers, with reporting lines, products, and managers all churning. That is a morale sink, not a stability signal.

An active req confirms the direction of travel: Nike is still hiring a Software Engineer I, ITC in Bengaluru right now, inside the Global Technology org building internal Consumer Product and Innovation tools, reporting to a Software Engineering Manager based in Bengaluru. India keeps hiring while Beaverton bleeds.

The pitch to Bengaluru is different from the pitch to Beaverton:

• Beaverton: uncertainty, three rounds in 24 months, 15 months until notification, stock down 40% in 2026.
• Bengaluru: scope creep, unrealistic throughput expectations, inherited US work, a new campus that is a construction site, not a culture.

Sourcers who send the Beaverton message to NITC get ignored. Sourcers who send a "your scope is doubling, your manager is new, your product just changed owners" message to NITC get reply rates that look like the ones Beaverton is about to produce.

By round three the "it won't be me" bias inverts. The people who survived twice are the ones who leave first.

Why Oregon WARN is a trailing indicator this time

Do not wait for Oregon WARN. In 2024 the Beaverton names came out through Oregon WARN filings, but by the time the notices posted, every FAANG recruiter had the same list and reply rates collapsed. In April 2026 Nike published no role count per team or per location, so WARN did not produce a usable list at all. "Pace" is on track to repeat the April pattern, not the 2024 one.

The implication for Nike WARN sourcing is counterintuitive: the WARN notice is where the pool goes to die, not where it starts. By the first filing, the names are in every ATS. Build the target list from LinkedIn and GitHub signals in the next 15 months, then use the WARN notice as a trigger to send the second message, not the first.

That is the exact gap Refolk closes. Instead of maintaining a Boolean that drifts every time Nike reorgs its title taxonomy, you describe the person in plain English ("staff and principal engineers at Nike in Beaverton who shipped something on GitHub in the last 18 months, exclude anyone who joined in the last year") and get a ranked shortlist back across LinkedIn, GitHub, and the open web. The point is to have the list before the WARN notice, not after.

The Boolean trap: NITC's legal entity hides 75% of the org

A "current company: Nike India Technology Center" filter on LinkedIn returns roughly a quarter of the actual Bengaluru tech org, because most GCC engineers are employed through contractors, EOR arrangements, or sister entities. The legal entity had 695 employees as of March 2024. The broader footprint is 3,000+.

The filter that works for Nike India Technology Center recruiting:

• Current employer: Nike (not "Nike India Technology Center").
• Location: Bengaluru, Hyderabad, or Pune.
• Title set: SWE, Sr SWE, Staff, EM, Director of Eng, PM, Data Eng, Data Scientist, ML Eng, Principal.
• Exclude: anyone whose employer history shows only the NITC legal entity for less than 18 months (likely a recent transfer, not a tenured target).

The same trap exists in Beaverton in a smaller way: Nike's title taxonomy has shifted enough across the three restructures that a title-locked Boolean from 2024 misses the current org. Describing the role in plain English avoids the problem entirely, which is why Refolk's output on "Nike principal engineers in Portland who have been there 4+ years" beats a hand-built Boolean that has to be rewritten every reorg.

The competitors already working this list

The competitors who will out-source you on the Nike diaspora are the ones with product-market fit for performance footwear engineers and the ones in geographic range of Beaverton. Name them, because that is who your messages are competing against in the inbox.

• On (Swiss, running-focused, Nike's most direct performance competitor). The pitch writes itself.
• Hoka / Deckers. Same pitch, different silhouette.
• Lululemon. Apparel-adjacent, hiring tech aggressively, has a Portland footprint.
• Adidas Portland. Three miles from Nike HQ. The lowest-friction physical move an engineer can make, which is also why Adidas offers tend to be lowball.
• Amazon / AWS Portland. The destination for Beaverton engineers who do not want to do apparel again.

If you are not On or Adidas Portland, your opening message has to acknowledge that the engineer has already heard from both. The way to win is specificity on the product and the team, not generic "we are hiring" copy. The 2,813-profile pool is small enough that the same twenty people are getting the same five messages a week by December.

A 15-month sourcing calendar

Treat the window between October 2026 and the first 2027 WARN notice as four phases, not one. Reply rates and messaging change at each phase.

1. October to December 2026 (now): Build the full 2,813-profile list. Enrich with GitHub, conference talks, and patent filings. First-touch Beaverton staff+ with uncertainty-framed messaging. Do not mention layoffs by name.
2. January to March 2027: Nike's fiscal Q3 and Q4 earnings land. Any new "clarifying" memos from Hill or Alagirisamy are the trigger for second-touch. Pivot NITC messaging to scope creep.
3. April to June 2027 (fiscal 2028 begins): The regional reorg takes effect. Reporting lines change for real. Reply rates peak here. Prioritize anyone whose manager changed in the last 90 days.
4. July 2027 onward (first WARN filings expected): You should already have the second meeting booked. The WARN notice is a scheduling event, not a sourcing event.

The sourcers who treat "Pace" as a 15-month campaign poach the names worth poaching. The sourcers who wait for the WARN notice get the same list everyone else gets, on the same day, with the same subject line.

FAQ

When will Nike's "Pace" layoffs actually be announced?

Elliott Hill said notifications will begin in calendar 2027 and continue through fiscal 2031. He explicitly declined to specify the number of roles or their locations, saying the company does not yet know. The regional consolidation from four geographies to three takes effect in fiscal 2028, which begins in June 2027, so expect the first wave of named notifications to cluster around that date rather than January.

How is "Pace" different from Nike's April 2026 "Win Now" layoffs?

"Win Now" cut ~1,400 roles in April 2026, with the majority in technology, and named Beaverton and the Nike India Technology Center as the two surviving tech hubs. "Pace" is a four-year, $2.5B cost program with $1B earmarked for employee-related costs and no stated role count. "Win Now" was execution. "Pace" is pre-announcement, which is why it opens a 15-month sourcing window rather than a two-week scramble.

Should I source Nike India Technology Center engineers or avoid them because India is "growing"?

Source them, with a different message. Nike is targeting 4,000 heads in India by 2027, up from 3,000 today, while asking NITC to absorb work from laid-off Beaverton peers. That is a scope-creep story, not a layoff story, and it produces real reply rates to the right pitch. Note also that filtering on "Nike India Technology Center" as current employer misses roughly 75% of the actual Bengaluru tech org, which sits under the broader Nike entity.

What is the fastest way to build the 2,813-profile Nike tech list?

Describe the cohort in plain English rather than maintaining a Boolean that breaks every reorg. In Refolk you can ask for "Nike staff and principal engineers in Beaverton or Bengaluru with 4+ years tenure" and get a ranked shortlist across LinkedIn, GitHub, and the open web, with the NITC legal-entity trap already handled. The 15-month window closes the moment the first WARN notice lands, so the time to have the list is now.