Apple's 147-Person WARN: Work the Cupertino Cohort Before Oct 20

Apple almost never files a WARN. The California notice covering 147 Bay Area roles, weighted to software engineering and machine learning, is the rarest sourcing event of the year, and it lands inside a CEO transition window that closes the moment John Ternus finishes moving into Tim Cook's office. If you are sourcing ML, computer vision, or AR/VR engineers, this is the cohort to work first and fast.

What Apple's 2026 WARN actually says

Apple's California WARN filing lists 147 layoffs across three Bay Area sites, with separations dated October 19 and October 20, 2026. The cuts skew heavily toward software development engineers, machine learning and AI/ML researchers, computer vision engineers, engineering program managers, and AR/VR software developers.

Here is the site-by-site breakdown, plus the pool math from Refolk's index of professional profiles.

Two facts to internalize before you write a single message. First, the WARN understates the real move. 9to5Mac's reporting puts the combined Vision Pro and Siri number above 200 once cuts below California's WARN-reportable threshold are counted, roughly 100 on each side. Second, this is a rare-skill cluster, not a generalist purge. More than 30 of the Sunnyvale seats alone are AR/VR software developers, a specialty a handful of US employers hire for at scale.

627

Why the Ternus transition compresses your window

The winning outreach window is between the WARN filing and October 20, 2026, not after. John Ternus, Apple's SVP of Hardware Engineering for the last 25 years, became CEO on September 1, 2026, with Cook moving to executive chairman. That timing changes the internal-transfer dynamics, which changes yours.

Here is the mechanism. A CEO transition at Apple's scale triggers a headcount reshuffle: new org charts, new priority projects, new "who owes whom a favor" politics. Internal transfer is almost always the first offramp offered to a WARN-listed engineer with long tenure, and Ternus, who ran hardware for iPad, AirPods, iPhone, Apple Watch, and Vision Pro, has personal relationships across the exact teams these engineers came from. Expect an aggressive internal-save effort in September.

That means:

• Early September: engineers know they are cut but internal transfer conversations are live. Response rates to outbound are moderate. Positioning matters more than urgency.
• Late September to early October: internal-save answers come back. This is your peak reply window. Engineers who did not get placed internally start reading InMail.
• Mid October to Oct 20: every recruiter watching WARN piles in. Inbox volume spikes. You lose on message quality, win only on speed and specificity.
• Post Oct 20: the strongest profiles are gone quickly. What is left is the pool everyone else is fighting over.

If you are still building your Apple-linked ML/AI list on October 5, you are late. This is the exact gap Refolk closes: you describe the person in plain English (say, "senior ML engineers at Apple in Cupertino or Sunnyvale who've worked on Siri or Vision Pro") and get a ranked shortlist back, without stitching together six Boolean strings against LinkedIn's degraded search.

The four sub-cohorts inside the 147, and who actually wants them

Treat the WARN as four distinct talent segments, not one pile. The buyers, message, and competing counter-offers differ for each.

1. Siri ML and on-device assistant engineers

Apple is rebuilding Siri on a new technical architecture that needs different engineering expertise than the current team was built around. The people being cut hold deep on-device inference, wake-word, ASR fine-tuning, and legacy assistant orchestration experience. They are not LLM-first researchers.

Natural landing spots:

• Amazon Alexa
• Google Assistant and Gemini on-device teams
• Rabbit, Humane successors, and voice startups building hardware-first agents
• Automotive voice stacks
• Wearables voice (Meta Ray-Ban, Samsung Galaxy Buds)

Do not pitch these engineers to a generalist LLM lab. Their edge is on-device constraints, not transformer research.

2. Vision Pro immersive video and gaming

Reports from AppleInsider and Bloomberg name the Apple Vision Immersive Video and Apple Vision gaming teams specifically. Apple previously paused further Vision Pro headset development to chase smartglasses that rival Meta's Ray-Ban products, so this cohort saw the writing on the wall.

The obvious buyer is Meta Reality Labs, which is racing Ray-Ban Meta and the next Quest against Apple's smartglasses pivot. Snap Spectacles, Niantic, Google XR, and stealth smartglasses startups round out the market. This is the segment where Refolk's index shows the most concentration outside Apple itself, with Meta as the clear number two current employer among Apple-linked ML/AI engineers.

3. Computer vision engineers

Overlaps with the Vision Pro segment, but broader. CV engineers who worked on Vision Pro hand tracking, eye tracking, or SLAM are directly relevant to autonomy talent networks (Cruise alumni are already in Refolk's Apple-adjacent index), robotics, and AR startups.

4. Engineering program managers

The most overlooked slice. Apple EPMs who shipped Vision Pro or Siri features hold rare hardware-plus-software coordination experience, and the WARN filing explicitly lists engineering program managers among the cut roles. Meta Reality Labs and hardware-heavy startups pay premiums for this profile.

Why this cohort is different from the 2023 Meta and Google waves

Apple layoffs are historically rare. 2026 has already blown past last year's total tech layoff count, but Apple's prior 2026 move was 57 people in Escondido in June. That means the tenure profile is unusually long and the outbound counter-offer bar is unusually high. Do not run the playbook you ran on ex-Meta 2023 talent.

Three concrete differences:

1. Tenure. In Refolk's index sample of 25 Apple-linked ML/AI engineers, 19 currently list Apple as their employer. Read that as a strong 5-plus year median tenure. These are not job-hoppers. Messages that lead with "moving fast" underperform messages that lead with "the next 8 years."
2. Competing internal offers. Apple is cutting Vision Pro and Siri while hiring aggressively for foundation-model and Apple Intelligence work. A meaningful share of your targets will get a real internal offer before Oct 20. Your outbound needs to beat "stay at Apple, different team."
3. Apple compensation baselines. Long-tenure Apple ICs on Siri or Vision Pro sit well above generalist senior engineer bands. If your comp band is thin, the WARN cohort is not your pool.

Sourcers who wait until October 20 are competing with every recruiter watching WARN. The winning move is contact before the effective date, while internal transfer signals are still live.

The tactical playbook, in order

Here is the sequence I would run this week if I had an ML or CV req to fill.

1. Build the base list. Pull every US ML, AI, or CV profile currently employed at Apple in Cupertino, Sunnyvale, Santa Clara, or Mountain View with five-plus years of tenure. In Refolk's index that is a subset of the 627 Apple-linked ML/AI engineers.
2. Layer the WARN signal. Cross-reference against public signals of Siri, Vision Pro, VisionOS, immersive video, or ARKit work: GitHub commits to Apple-adjacent open source, WWDC session credits, patent filings, published papers.
3. Split into the four sub-cohorts (Siri, Vision Pro, CV, EPM) and assign a message template per cohort. Do not send one generic "saw the news" note.
4. Send in the peak reply window, roughly late September through the first week of October. Not earlier (they are still in internal-save mode), not later (inbox saturation).
5. Lead with a peer name from Refolk's index. Meta and Cruise alumni, ex-Magnit-at-Apple contractors. "I placed X at Y last year, similar background" outperforms "I saw the WARN."
6. Skip InMail for the top of the list. Send GitHub, personal site, or referred email. Cold InMail reply rates on senior engineering outbound are not the tool for this cohort.
7. Track the June 2026 Escondido precedent. Apple laid off 57 people in Escondido; check where they landed by now. That gives you a live list of buyers who already know how to close Apple engineers.

The "AI layoff" framing trap

Do not sell these engineers as "AI layoff" refugees. Apple's cuts illustrate why it is difficult to classify every technology layoff as an AI layoff. Companies eliminate positions as part of product changes, management restructuring, or cost reductions while simultaneously increasing hiring in other technical areas.

Apple is doing exactly that: cutting Vision Pro and Siri while ramping foundation-model and Apple Intelligence hiring. If your outreach frames the engineer as a victim of "AI displacement," you sound uninformed and you lose the response. Frame them as specialists whose product got deprioritized, not as generalists whose skills got automated. The difference in reply rate is not subtle.

6.7%

What to watch after Oct 20

Two feeds to monitor for the true scope beyond WARN: 9to5Mac, which broke the 200-plus combined Vision Pro and Siri estimate, and Mark Gurman at Bloomberg, who has the internal reorg thread. Any additional cut that stays under California's WARN threshold, or lands outside California entirely, will not show up in a public filing. It will show up in Gurman's reporting first.

Also track internal moves. Ternus taking the CEO chair on September 1 means the next 90 days will produce a wave of Apple engineers voluntarily leaving after being reassigned to a project they did not sign up for. That secondary cohort, invisible to WARN, is often larger than the WARN itself, and you find it by re-running your Apple-linked shortlist every couple of weeks and flagging new "Open to work" and profile-update signals.

FAQ

When exactly do the Apple layoffs take effect?

Separations are dated October 19 and October 20, 2026, per Apple's California WARN filing. That gives affected engineers roughly six weeks of notice, which is also your outbound window. Contact in the back half of September through early October lands best; after October 20, you are competing with every recruiter who reads WARN feeds.

How many Apple engineers are really being cut?

The WARN says 147 across Cupertino (79), one Sunnyvale office (40), and a second Sunnyvale office (28). 9to5Mac puts the real combined Vision Pro and Siri total above 200 once cuts below California's WARN-reportable threshold are counted, roughly 100 on each side. Assume 200 as your working number for the total addressable cohort.

Should I source these engineers for an LLM startup?

Usually no. The Siri cuts are happening because Apple is moving to a new technical architecture that needs different expertise; the engineers being cut hold on-device ML, wake-word, and legacy assistant skills. Those transfer to Alexa, Google Assistant, automotive voice, and voice hardware startups, not to a generalist LLM research shop. The Vision Pro cohort is a stronger fit for Meta Reality Labs, Snap, Niantic, and stealth smartglasses than for a foundation-model lab.

Does John Ternus becoming CEO change hiring at Apple?

Yes, in ways that matter for sourcing. Ternus is a 25-year Apple hardware engineer who managed engineering for iPad, AirPods, and recent iPhone models, with deep ties across the Apple Watch and Vision Pro teams. Expect an aggressive internal-transfer save effort for WARN-listed engineers in September, which means a meaningful share of your targets will get a real internal offer before October 20. Your outbound has to beat "stay at Apple on a different team," not just "leave Apple."