If you were one of the roughly 200 Apple engineers cut on August 21, 2026, you already know the awkward part: there is no WARN filing, no 8-K, no press release. Bloomberg's Mark Gurman has the only real account, and everything downstream (Engadget, 9to5Mac, TechCrunch, MacRumors, AppleInsider) traces back to that one story. The story of your layoff is whatever you write on your resume.
And the two halves of this cut need almost opposite resumes.
Why Apple's Aug 21 layoff is actually two disjoint job searches
Apple cut roughly 100 people from Vision Pro (largely the gaming team plus immersive video) and roughly 100 from Siri and the Intelligent Systems Experience (ISE) group, and the reasons behind each half force different resume strategies. One cohort was cut for unit economics; the other was cut because a rewrite made their stack obsolete.
- Vision Pro side: an economics cut. Per Bloomberg, an immersive-video episode can cost several million dollars to film against a small active user base at the $3,699 headset's price point. The engineers did their jobs. The math did not work.
- Siri / ISE side: a skills cut. Apple is rebuilding Siri on a new AI-powered architecture that requires different expertise, and the cuts landed on teams still working the old stack while the new Siri AI was being demoed to developers on June 8.
That distinction matters because recruiters cannot Google the reason you were let go. There is no article that says "the graphics pipeline team was preserved" or "the NLU rules team was dissolved." The Intelligent Systems Experience group barely exists as a public name. You get to decide what story the resume tells, and you should tell a different one depending on which side of the split you sat on.
Split roughly 100 Vision Pro (gaming, immersive video) and 100 Siri/ISE, per Bloomberg. No WARN filing exists.
What the Refolk index says about your actual competition
Your target pool is lopsided in ways that should change how you write. Refolk's US index of professional profiles gives four counts that matter here, and two ratios that do most of the work in this article.
| Cohort or query | Count in Refolk index | Top employer signal | Note |
|---|---|---|---|
| AR / Vision Pro / Spatial Computing / visionOS titles (US) | 19 | Snap Inc. (13) | Tiny titled pool; Snap dominates |
| visionOS / RealityKit / ARKit skills (US) | 946 | Bay Area, NYC, Seattle | Realistic competitive pool for Vision Pro cohort |
| Conversational AI / Speech / NLU / Voice Assistant titles (US) | 18 | Onix (5) | The "legacy Siri-style" title pool |
| ML/AI/Research Engineer + LLM/PyTorch (US) | 3,441 | Meta (5 of top 25) | Target pool Siri engineers must credibly enter |
| LLM-ML pool ÷ legacy voice-assistant pool | ~191x | - | Target market is nearly 200x larger than the legacy one |
| Spatial-skills pool ÷ titled Vision Pro pool | ~50x | - | Skills-based reframe unlocks ~50x more matches |
The two ratios say the same thing in different words:
- 50x more matches if a Vision Pro engineer writes for the skills pool (visionOS, RealityKit, ARKit) instead of the titled pool.
- 191x more roles if a Siri engineer credibly reframes into LLM-era ML instead of staying inside the legacy voice-assistant title.
Whatever you called yourself at Apple is not what your next job title is going to be called.
The Vision Pro engineer resume: reframe as spatial, not as Vision Pro
If you were cut from the Vision Pro gaming or immersive-video team, your resume should stop leading with "Vision Pro" and start leading with "spatial computing / AR" with the visionOS 27 toolchain listed as skills. The arithmetic: 19 titled AR/visionOS engineers versus 946 with the same skills under a different title. You want to be found by all 946 searches, not just the 19.
Name the toolchain, not the product
The reader hiring you at Snap Spectacles, Meta Reality Labs, or ByteDance's Pico team is searching for toolchain keywords, not marketing names. In June 2026 Apple shipped updates to RealityKit, Unity, Unreal, and Godot support, plus Spatial Preview, Foveated Streaming, controller APIs, and an Apple Immersive Video toolchain. Those are the strings that land you in a recruiter's saved search.
Rewrite bullets around:
- RealityKit / ARKit / visionOS 27
- Unity and Unreal cross-platform spatial builds
- Foveated Streaming and Spatial Preview
- Controller APIs and hand-tracking input
- Apple Immersive Video pipeline (if you actually touched it)
Lead with unit economics, not with "the future of computing"
Your team was cut because episodes cost several million dollars to produce against a limited user base. If your resume opens with "shipped the future of computing," a hiring manager reads it as "expensive." Flip it. Lead with the cost side of what you built:
- Frames per dollar, not just frames per second.
- Render-farm hours saved.
- Content pipeline throughput per headcount.
- Contractor spend reduced.
A resume that reads like a line manager wrote it (cost, throughput, headcount leverage) beats one that reads like a keynote. This is the exact tailoring Refolk handles from a job posting: paste the Snap Spectacles or Meta Reality Labs listing, and Refolk rewrites your own bullets against that specific job's economics language, then scores how well you actually fit before you hit send.
The Snap concentration is real. Aim there first.
Refolk's index shows Snap Inc. holding 13 of the 19 explicitly titled AR/spatial engineers in the US. That is the most concentrated landing spot in the country for laid-off Vision Pro staff, and Apple will never name it. Meta Reality Labs and ByteDance/Pico are the other two credible destinations. LA metro leads with 5 of 19, so if you were on the immersive-video side and already lived in Culver City, geography is with you.
Do not wait for 2028
Bloomberg reports Apple is still considering a new Vision Pro as early as end of 2028. That is a 24+ month bet on a product Apple just partially defunded, and Apple's near-term focus is smart glasses that will not support immersive video or advanced gaming titles. Do not structure a job search around a possible rehire. Your visionOS skills have a shelf life; use them while 2026 postings still name-check RealityKit.
The Siri engineer resume: translate legacy pipelines into LLM-era vocabulary
If you were cut from Siri or ISE, your resume needs to translate rule-based, hybrid-pipeline, and NLU work into the vocabulary of evals, retrieval, orchestration, and agents, because the target market is nearly 200x larger than the legacy voice-assistant pool. Staying inside "Conversational AI Engineer" puts you in a pool of 18 people nationally. Credibly reframing into LLM/PyTorch ML puts you in the pool of 3,441 where Meta alone accounts for 5 of the top 25 employers.
A resume that reads "Siri NLU, 8 years" doesn't sound senior. It sounds stranded.
The same problems, renamed
Siri engineers worked on hard problems that the LLM world is now rediscovering under new names. Rename them on the resume:
- Intent classification and slot filling → retrieval and tool-calling evals
- Dialogue state management → agent orchestration / state machines
- Rule-based fallback logic → guardrails and constrained decoding
- Utterance annotation and disambiguation → preference data pipelines
- On-device wake-word and ASR tuning → edge inference and quantization
- A/B testing dialog flows → offline eval harnesses and golden sets
None of this is dishonest. It is the same work under the vocabulary a 2026 recruiter searches for. The move you cannot make is claiming to have shipped a foundation model. The move you should make is claiming years of production experience with the exact evaluation, latency, and safety problems every LLM team is now hitting for the first time.
Address the "why cut" question head-on in the summary
Because there is no WARN filing and no press release, a recruiter has no way to distinguish "cut for performance" from "cut because the architecture changed." Say it plainly in the summary line:
"Senior engineer, Apple Siri / Intelligent Systems Experience (2018 to 2026). Team dissolved as Siri moved to a new AI-based architecture, publicly demoed to developers June 8, 2026."
That single sentence does three things: it names the ISE group so keyword searches find you, it dates the cut, and it puts the reason on the record. This is one of the few situations where being explicit about which side of a rewrite you were on actually helps. Refolk will build this summary out of your own history and then rewrite it for each posting, so a Meta AI Infrastructure listing gets a different framing than an Anthropic evals role.
Two landing patterns, not one
For a Siri engineer job search, there are two credible tracks and you should apply to both in parallel:
- LLM-adjacent infrastructure roles at Meta, Anthropic, Google DeepMind, OpenAI, and the ML platform teams at large enterprises. You are competing inside the 3,441 pool but you have production-scale voice-assistant experience most of them lack.
- Legacy conversational AI roles at Onix, LivePerson, Avaya, and the enterprise IVR / contact-center vendors. Refolk shows Onix as the top employer of titled Conversational AI Engineers (5). These roles still value NLU and dialog work directly, no reframe required. They pay less than the LLM track but they close faster.
Sending the same resume to both is how you lose both.
A 30-day plan for both cohorts
Here is the same 30-day skeleton, filled in differently depending on which half of Apple you came from.
| Week | Vision Pro cohort | Siri / ISE cohort |
|---|---|---|
| 1 | Rewrite headline from "Vision Pro" to "Spatial / AR engineer, visionOS 27." List RealityKit, ARKit, Unity, Unreal, Godot. | Rewrite headline from "Siri NLU" to "ML engineer, conversational systems." List PyTorch, evals, retrieval, orchestration. |
| 2 | Apply to Snap Spectacles, Meta Reality Labs, ByteDance/Pico first. Target LA and Bay Area. | Apply to Meta, Anthropic, and enterprise ML platform teams. Parallel apps to Onix, LivePerson, Avaya. |
| 3 | Rewrite 3 bullets around cost, throughput, and content-pipeline economics. | Rewrite 3 bullets around eval harnesses, latency SLOs, and safety guardrails. |
| 4 | Score fit against each posting. Cut anything that reads as generalist AR. | Score fit against each posting. Cut anything that reads as pure rules engine. |
Weeks 3 and 4 are where most people stall, because rewriting the same three bullets 40 different ways is the work nobody wants to do.
FAQ
Should I mention I was laid off at all on my resume?
Yes, briefly, because there is no WARN filing or press release for a recruiter to find. One line in the summary that dates your Apple tenure and names the reason ("Vision Pro gaming team consolidation, August 2026" or "Siri architecture rewrite, August 2026") controls the narrative before someone else invents a worse one. Save the longer story for the phone screen.
Is it dishonest to reframe Siri NLU work as LLM-era ML?
No, as long as you rename the problems, not the tools. Saying you built intent classification and dialog state at Apple Siri scale is honest. Saying you fine-tuned Llama when you did not is not. The 3,441-person LLM/PyTorch pool in Refolk's index is full of people who have never shipped a voice assistant to a million-plus daily users; that is your actual edge, and it does not require lying about which frameworks you touched.
Why is Snap the answer for Vision Pro engineers and not Meta?
Both are credible, but Refolk's index shows Snap holding 13 of 19 explicitly-titled US AR/spatial engineers, the highest concentration of any single employer for that title. Meta Reality Labs is larger overall but its AR engineers are diffused across many teams, so a Vision Pro immersive-video specialist maps more directly onto a Snap Spectacles or Snap AR team than onto a generic Reality Labs listing. Apply to both. Snap is the higher-density first swing.
Should I wait for the 2028 Vision Pro to see if Apple rehires?
No. Bloomberg's reporting says Apple is "still considering" a 2028 model, which is a 24+ month bet on a product line Apple just partially defunded and whose $3,699 headset has struggled to move volume. Apple's near-term focus is smart glasses that will not support immersive video or advanced gaming, so the internal-transfer window for that cohort is narrow. Job-search now, and if Apple calls back in 2028, take the meeting from a position of strength.