Nike's Pace Memo: The 15-Month Window on 720 Beaverton Techies

On October 1, 2026, Nike CEO Elliott Hill told employees that the "Pace" restructuring would cut jobs starting in calendar 2027, and then declined to say how many, where, or who. For sourcers covering Beaverton, that silence is the opportunity. Every tech, digital, and supply-chain employee on the Oregon campus now knows they are a target, and no recruiter in the market has a list.

What Nike actually announced on October 1

Nike announced a four-year restructuring targeting $2.5B in savings through fiscal 2031, including about $1B in employee-related costs on top of the $300M already recognized in FY26, with layoffs not beginning until calendar 2027. Hill called it "Pace" and framed it as an operating-model overhaul rather than a cost cut, but the mechanics are the same: a smaller workforce, consolidated into fewer regions, with a new campus in Bengaluru absorbing the center of gravity.

The specifics Hill did share:

• Three regions instead of four from FY28. Americas combines North America and Latin America. Asia Pacific plus Greater China run out of Singapore. EMEA stays as is.
• A new Bengaluru campus opens in FY28, covering Nike, Jordan, and Converse.
• Most of the $2.5B in savings lands in FY29 and FY30, meaning the heaviest cuts are two-plus years out.
• No role count. No department breakdown. No notification date beyond "calendar 2027."

This is the third 2026 round. January took 775 jobs at US distribution centers as automation came online. April cut roughly 1,400 roles "with the majority in technology," per COO Venkatesh Alagirisamy, and explicitly named Beaverton and the Nike India Technology Center as the two surviving tech hubs. Pace is the follow-through.

$1B

Why "zero names" is the sourcing window, not the obstacle

The absence of a number is the window. When a company announces specific headcount, every ex-employee's inbox fills inside 72 hours and warm-reply rates collapse for a month. Nike announcing zero means every Beaverton employee is now in low-grade job-search mode, but no recruiter has a target list to work from. Through October to December 2026, sourcers face something close to no competition for warm replies.

The mechanism is well documented. Organizational psychologists have shown that prolonged uncertainty raises emotional exhaustion and intent-to-leave among survivors, not just the people who get cut. Hill gave his workforce a 15-month ambiguity cloud. That is a longer window of elevated job-search intent than any single-day notice has ever produced.

Three practical consequences:

1. No media-driven inbound rush. There is no "Nike list" circulating. Candidates are not being hammered.
2. Equity math reinforces the uncertainty. NKE fell roughly 4% after-hours on the announcement to about $34 and is down 45% year to date. RSU grants from 2022 to 2024 are worth a fraction of promised value. The money math and the uncertainty math point the same direction.
3. Internal transfers are frozen in all but name. When a company tells you the structure is changing but will not say how, mid-career PMs stop treating internal mobility as a safe bet.

The index: 720 US profiles, 1,283 in India

Nike's tech center of gravity has already shifted to India, and the Pace memo is ratifying that, not initiating it. In Refolk's index of professional profiles, there are about 1.78 times more Nike-adjacent tech workers in India than in the US on comparable titles. The FY28 Bengaluru campus is the physical infrastructure to match a workforce distribution that already exists.

Two things jump out of the US query. First, 720 is small enough to actually work end to end in a quarter. Second, Portland metro is not in the top 10 locations for ex-Nike tech talent in the index. The dispersion is already into the Bay Area, with Google, Apple, Figma, Microsoft, and even Oxide Computer appearing as current employers. The migration out of Beaverton started before Pace was named.

Nike told its own employees they are a target, then refused to say who. That is a 15-month warm-reply window.

The real at-risk function is duplication, not engineering

Hill's exact phrasing was that Nike will "add capabilities in some areas and eliminate duplication in others," which is the softest possible description of middle-management elimination. The people between the collapsing four-region structure and the new three-region structure are the softest Pace targets, not individual contributors.

Who sits in that layer:

• Regional operations leads duplicated between North America and Latin America, now folding into "Americas."
• Program managers aligned to Greater China who now report into Singapore.
• EMEA-adjacent product managers in Hilversum whose scope narrows as APAC consolidates.
• Director-level roles in Beaverton whose India counterparts already exist. "Director" is the #2 title among India-based Nike-adjacent talent in Refolk's index.

For sourcers, this changes the title filter. The highest-conversion Pace outreach is not "Senior Software Engineer, Nike" but "Director of Program Management, Nike" and "Senior Manager, Supply Chain Analytics, Nike." These are people whose roles have an obvious India mirror and whose equity is deeply underwater.

This is the exact gap Refolk closes. Instead of building a 14-filter Boolean string for "director, duplicated scope, three-region reorg exposure," you describe the person in plain English ("Nike directors in Beaverton whose scope overlaps a Bengaluru counterpart") and get a ranked shortlist back, with current employer, tenure, and the India-based mirror profile where one exists.

The Bengaluru backfill: who to source into ITC right now

Nike's India Technology Center is hiring the exact backfill, and the pool to work is ex-Flipkart, ex-Myntra, and ex-Walmart Global Tech supply-chain and data profiles. Open requisitions at ITC Embassy GolfLinks include Lead Software Engineer and Software Engineer 1 through 3 slots on the Data, Analytics, and Intelligence team, which Nike describes as building "scalable AI/ML solutions and intelligent platforms." That is the organizational layer the Pace memo is building up.

If you recruit for Nike or any of its India-based competitors, the sourcing lanes are:

• Flipkart supply-chain data engineers. The closest cultural analog for ITC's DAI team.
• Myntra product and category managers. Direct retail-tech overlap with Nike Direct.
• Walmart Global Tech Bengaluru. The largest India-based cohort of US-retailer tech talent, and the single biggest source of warm Nike referrals.

The Bengaluru campus story is a classic case of a cost-cut announcement that is also a hiring announcement. If you only read the $2.5B headline, you miss that Nike is hiring harder in India than it is cutting in Oregon on a role-weighted basis.

Converse in Boston is the quiet pool

Converse engineers in Boston are twice-dislocated and almost never covered in Nike-focused sourcing. The April memo moved Converse manufacturing and engineering closer to factory partners. The October campus announcement explicitly folds Converse into the Bengaluru scope alongside Nike and Jordan. These engineers have been reorganized twice in six months and are not on any sourcer's standard Nike list.

Three reasons the Converse pool converts:

1. No Beaverton loyalty. Converse Boston employees were acquired, not hired by Nike directly. Their emotional attachment to the parent brand is weaker.
2. No Bengaluru path. Unlike Beaverton PMs who can plausibly fight for a role in the new three-region structure, Converse functional engineers have no internal escape hatch.
3. Boston market absorbs them fast. The local tech cohort will take Converse product engineers without a title downgrade.

If your search string is "current company: Nike" you are missing Converse entirely. Searching by parent company or asking for "Converse engineers and product managers in Boston with 3+ years tenure" surfaces the pool in one query.

A 90-day sourcing plan for Pace survivors

Work the 15-month window in three phases, front-loading the warm-reply advantage before the first notification lands in January 2027. The highest-leverage work happens before any list exists.

Phase 1, October to December 2026: build the shadow list

• Pull all 720 US Nike-adjacent tech profiles into a single pipeline.
• Enrich with tenure, title, and manager where visible. Flag directors and senior managers in Beaverton with India counterparts.
• First-touch message explicitly acknowledges the Pace memo without claiming inside knowledge. "Saw the Oct 1 announcement, imagine the ambiguity is exhausting, 15 minutes next week?"

Phase 2, January to March 2027: convert the first-notification cohort

• Nike begins actual notifications. Media coverage returns and inbound saturation spikes.
• Shift from cold outreach to warm reconvert. Candidates who replied in Phase 1 and said "not now" are now ready.
• Use referrals from Phase 1 placements to open the Converse Boston door.

Phase 3, April 2027 onward: Bengaluru backfill races

• ITC hiring accelerates visibly.
• US sourcing shifts to displaced directors who will not relocate and are now permanently in the market.
• India sourcing shifts to ex-Flipkart, ex-Myntra, ex-Walmart Global Tech, with Nike as the brand hook.

Pace survivors are not findable by title alone. You need the intersection of company, geography, title layer, and reorg exposure, which is why the 720-profile US cohort is tractable in a single quarter rather than a single year.

FAQ

How many Nike employees will Pace actually cut?

Nike has not said. The disclosed numbers are $2.5B in total savings through FY2031 and $1B in employee-related costs on top of $300M already in FY26. For precedent, April 2026 cut roughly 1,400 roles "with the majority in technology." Pace is almost certainly larger, given the dollar pool, but the deliberate ambiguity means no sourcer should pretend to know the number.

When should I start outreach to Beaverton tech employees?

Now, October to December 2026, before the first notifications land in calendar 2027. The 15-month ambiguity window is the entire point. Once Nike begins specific role eliminations, the market floods with inbound and warm-reply rates drop. Research on prolonged restructuring uncertainty shows survivors raise their intent-to-leave even without being on the list.

Does the Bengaluru campus mean US cuts will be deeper than announced?

The signal points that way, but Nike has not confirmed it. The April memo named Beaverton and ITC as the two surviving tech hubs. The October campus announcement is the physical infrastructure for ITC. Refolk's index already shows about 1.78 times more Nike-adjacent tech talent in India than the US on comparable titles, so the center of gravity has already shifted. The FY28 campus is ratifying the shift, not creating it.

Who else is hiring from the ex-Nike tech pool right now?

Google, Apple, Figma, Microsoft, and Oxide Computer all appear as current employers of ex-Nike engineers in Refolk's index. The dispersion is heavily toward the Bay Area rather than staying in Portland, which is why Portland metro does not crack the top 10 locations for ex-Nike tech talent. If you are competing for this pool, assume FAANG-orbit compensation is the benchmark your Pace survivor is already comparing against.