On September 3, 2026, Volkswagen's supervisory board unanimously approved Future Plan 2030, adding roughly 50,000 job cuts on top of the 50,000 already agreed and shrinking the group's model lineup by half by 2035. If you write software at CARIAD, validate ECUs at Audi Neckarsulm, or own an infotainment variant at Emden, the specialty on your resume is being deleted along with the SKU. The question is not whether to rewrite. It is which vocabulary you rewrite into.
Why the 75% complexity cut deletes variant specialists first
The plan reduces model complexity by roughly 75%, and that math falls hardest on engineers whose resumes read as variant work. Surviving VW, Audi, and Porsche models will share more code, more platforms, and fewer regional configurations, so the group needs fewer people who own the delta between a Passat B8 and B9 diesel and more people who own the platform underneath both.
Read the September 3 approval as three linked decisions:
- Half the lineup dies by 2035. Every derivative engineer attached to a discontinued nameplate loses their reason to exist inside the org.
- Complexity drops ~75%. Fewer variants means fewer variant-integration jobs, fewer market-specific calibrations, fewer country packs.
- Four German plants (Emden, Zwickau, Hannover, Neckarsulm) have until June 2027 to justify their survival with a viable European production strategy.
The mechanism is simple. Fewer SKUs means fewer people needed to integrate options across them. If your last five years read as "responsible for infotainment integration on Passat B9 vs B8 diesel," a recruiter at RV Tech or Scout sees a skill that VW itself decided is worth 75% less by 2030.
~50,000 already agreed plus ~50,000 approved on September 3, 2026, including Audi, Porsche, and CARIAD.
The CARIAD problem: a name that reads as failure
CARIAD's brand is a liability in your headline and an asset in your bullets, so move the noun and keep the work. The public narrative is that VW spent over €14 billion, delayed its L4-capable platform from 2026 to 2030, and cut close to a third of CARIAD's roughly 6,000-person workforce while reassigning the future architecture to the Rivian joint venture. Recruiters have read that story.
They have not read what you personally shipped. The rewrite is to lead with architectural nouns the receiving org uses, then attribute the work to CARIAD in the employer line where it belongs:
- Not "CARIAD software engineer, VW.OS infotainment stack" as your headline.
- Yes "Zonal ECU integration lead, vehicle abstraction layer, OTA delta updates" as your headline, with CARIAD in the employer field.
The 4-year slip on L4 is public. Own what you shipped inside it: bench validation runs, MISRA-compliant modules, ASPICE Level 2 or 3 artifacts, HIL coverage numbers, specific ECUs that made it to a B-sample. Hiding the timeline looks worse than owning it, because Rivian, Bosch, and Vector recruiters all know the dates.
This is the exact rewrite Refolk does for you: paste the RV Tech, Scout, or Elektrobit posting, and Refolk pulls the architectural nouns out of your CARIAD history and puts them where a recruiter reads first, without you having to relive the launch that slipped.
The 1:7 SDV supply gap hiding in Refolk's index
The software-defined vehicle label is scarce enough that adopting it moves you into a much smaller and more visible pool. In Refolk's index of professional profiles, 3,470 people in Germany list AUTOSAR as a skill. Only 489 professionals across Germany and the US combined self-describe as software-defined vehicle focused. That is roughly a 1-to-7 ratio, and it is the single most useful arbitrage on any Volkswagen layoffs resume being written this quarter.
| Segment | Count | Source |
|---|---|---|
| AUTOSAR-skilled professionals, Germany | 3,470 | Refolk's index |
| "Software-defined vehicle" self-identified, Germany + US | 489 | Refolk's index |
| Ratio SDV-labeled to AUTOSAR-labeled | ~1 : 7 | Derived |
| Automotive software engineers, Germany (narrow title set) | 139 | Refolk's index |
| RV Tech headcount, 12 months post-founding | 1,500+ across 5 countries | volkswagen-group.com |
| CARIAD workforce reduction | ~6,000, ~30% cut | adolfocarreno.com |
| Total VW Group cuts by 2030 | ~100,000 | cnbc.com |
The mechanism behind the gap: AUTOSAR is a standard you can list truthfully after one project. SDV is a framing that requires you to describe architecture, update pipelines, and lifecycle ownership. Most engineers who could truthfully claim it never bothered. The ones who do rewrite the label surface immediately in searches at RV Tech, Excelfore, Red Hat, GM, Bosch, and CARIAD Inc, which are the top employers in that 489-profile pool.
Relabeling AUTOSAR work in SDV vocabulary is not marketing. It is arbitrage on a 1-to-7 supply gap.
RV Tech is the reference employer, not the rescue plan
RV Tech, the $5.8 billion Rivian-VW joint venture, is the vocabulary your resume should match, but it cannot absorb even 10% of the CARIAD wind-down on its own. One year after founding, RV Tech reported more than 1,500 employees across the United States, Canada, Germany, Serbia, and Sweden. It is building the zonal electrical architecture that will underpin the Volkswagen ID.EVERY1 in 2027 and the first Audi with the full Rivian-developed stack in 2028, replacing MEB and PPE.
That means two things for your CARIAD engineer job search:
- Read RV Tech job descriptions as a translation dictionary. Zonal computing, OTA, vehicle abstraction layer, centralized compute, delta updates. These are the words a 2026 automotive software resume must contain.
- Do not aim only at RV Tech. With 1,500 seats globally and hiring in Berlin, Palo Alto, and distributed, it will not clear tens of thousands of applicants. Tier-1s and adjacent OEMs are the actual mass absorbers.
The two-version resume: JV/OEM path vs tier-1 supplier path
Keep two versions of your EV engineer pivot resume, because the reader on the other side is optimizing for different things. The JV/OEM version at RV Tech, Scout Motors, and Horizon Robotics reads architecture and integration scope. The tier-1 version at Elektrobit, Vector Informatik, IPG Automotive, intive, Wind River, FORVIA HELLA, and Bosch reads standards compliance, tool ownership, and OEM-shipped modules.
| Reader | Wants to see | De-emphasize |
|---|---|---|
| RV Tech, Scout, Rivian | Zonal architecture, OTA, SDV, centralized compute, delta updates | AUTOSAR Classic-only work, single-variant integration |
| Elektrobit, Vector, Wind River | AUTOSAR Adaptive, MISRA, ASPICE, ISO 26262, specific ECUs shipped | Generic "platform" framing without a standard attached |
| Horizon Robotics, Chinese partners | ADAS perception, sensor fusion, China-market calibrations | EU-only compliance work |
| Bosch, FORVIA HELLA | Tool chain ownership (CANoe, DaVinci, EB tresos), tier-1 program experience | Pure OEM-side product management |
Writing two versions by hand takes an evening per posting. Refolk tailors the resume to each posting automatically, so the RV Tech application leads with zonal and OTA, and the Vector application in the same session leads with AUTOSAR Adaptive and ASPICE, without you maintaining two master files.
Answering "why did you leave VW in 2026" before it's asked
Address the departure narrative on the resume itself, because the voluntary and partial-retirement math is skewing the story about who is left. CEO Oliver Blume said about 37,000 departure agreements have already been signed, largely through voluntary measures and partial retirement. The implication a hiring manager will draw, fairly or not, is that engineers who stayed into the involuntary wave were the ones whose buyout math didn't work, which usually means mid-career specialists.
Get ahead of it in one line under the role, not in the cover letter:
- "Departed as part of Future Plan 2030 platform consolidation; last shipped module: [specific ECU / feature / bench artifact]."
- "Elected to exit ahead of Neckarsulm wind-down decision (June 2027 deadline); available immediately."
- "Role eliminated in CARIAD architecture handover to RV Tech joint venture; owned [specific handover artifact]."
The pattern: name the plan, name what you shipped last, name your availability. Recruiters read that as clean.
The five nouns that belong in your 2026 headline
Rewrite the top third of your resume so a recruiter searching in an ATS or on LinkedIn hits the words RV Tech, Scout, and the top tier-1s actually filter on. From the SDV-labeled pool in Refolk's index and current RV Tech and Rivian job descriptions:
- Zonal architecture or zonal ECU (replaces "domain controller" for the 2026 vocabulary).
- Vehicle abstraction layer (the SDV framing of what CARIAD called VW.OS internally).
- OTA delta updates or OTA pipeline (not just "over-the-air"; specify the update strategy).
- Centralized compute (the architectural claim MEB and PPE could not make).
- Software-defined vehicle (the label 489 people globally use; join them).
Two anti-patterns to strip:
- Do not list "VW.OS" without translation. Outside CARIAD alumni, nobody parses it.
- Do not lead with the €14 billion program name. Lead with the module you personally shipped inside it.
Where to be visible while the applications go out
Add two named communities to your online presence, because recruiters at the 489-profile SDV pool source through them. SDVerse appears repeatedly in the SDV-keyword pool in Refolk's index and is the closest thing the SDV world has to a marketplace-plus-community. GitHub contributions on any AUTOSAR Adaptive, Zephyr, or automotive-grade Linux repo do more for a CARIAD engineer job search than a fifth LinkedIn post about the layoffs.
The distribution of where the 489 SDV-self-identified profiles actually work, from Refolk's index: Excelfore, SDVerse, GM, CARIAD Inc, Bosch, Red Hat. That is your target list on day one, with RV Tech, Scout, and Horizon Robotics stacked on top.
FAQ
Should I still list CARIAD on my resume after the layoffs?
Yes, in the employer field, not the headline. CARIAD is a recognized engineering org with real system-level scope, and hiding it looks evasive. What you change is the framing above it: lead with architectural nouns (zonal, OTA, vehicle abstraction layer, SDV) that RV Tech, Scout, and the top tier-1s search on, and let CARIAD sit in the employer line where recruiters expect it. Own what you shipped, including bench validation and ASPICE artifacts from the L4 program that slipped from 2026 to 2030.
Is RV Tech realistically hiring displaced VW engineers?
RV Tech is hiring in Berlin, Palo Alto, and distributed across five countries, but with roughly 1,500 total employees a year after founding, it cannot absorb even 10% of the CARIAD wind-down. Treat RV Tech job descriptions as your vocabulary reference and apply, but stack tier-1s (Elektrobit, Vector Informatik, IPG Automotive, intive, Wind River, FORVIA HELLA, Bosch) and Chinese-partnered stacks like Horizon Robotics on the same target list. The two-version resume (JV/OEM and tier-1) is not optional.
How do I frame the delayed L4 program without sounding like I failed?
Quantify what you personally shipped inside it, not what the org announced. Specific ECUs at B-sample, MISRA-compliant modules, ASPICE Level 2 or 3 artifacts, HIL coverage percentages, and bench validation runs are all real work that survives a program slip. Recruiters at Rivian and Bosch already know the 2026-to-2030 timeline; pretending otherwise is what damages you. One clean line under the role naming Future Plan 2030 as the reason for departure closes the loop.
What is the single highest-leverage change to make this week?
Relabel your AUTOSAR and platform work in software-defined vehicle vocabulary if you can do so truthfully. In Refolk's index, 3,470 professionals in Germany list AUTOSAR but only 489 across Germany and the US self-describe as SDV-focused, a roughly 1-to-7 supply gap. Adding "software-defined vehicle," "zonal architecture," and "OTA delta updates" to your headline and skills, backed by specific bullets, moves you into the smaller and more visible pool that RV Tech, Excelfore, GM, and Red Hat actually search.