If you write software at CARIAD, Audi, Porsche, or any VW Group unit, your resume is now competing against tens of thousands of other engineers whose CVs all say "AUTOSAR" and "ISO 26262". On September 3, 2026, Volkswagen's supervisory board unanimously approved Future Plan 2030, a roughly €16 billion restructuring that clears the way for up to 50,000 more job cuts on top of the ~50,000 already in motion.
This is a tactical guide to rewriting your resume so a SaaS, cloud, or medtech hiring manager can actually read it.
What Future Plan 2030 did to the software org
Future Plan 2030 killed CARIAD as an in-house platform builder and turned it into an integrator of Rivian and XPeng code, which means "I worked on VW.OS" is no longer the resume line it was two years ago. The board approved the plan on September 3, 2026, sending shares up 7.9% the same day, and it targets lifting group operating return from ~4% to 9%. About half of the new cuts land in Germany, roughly 25,000 domestic positions and the exact pool CARIAD sits inside.
The mechanism matters for how you write the resume. CARIAD's E3 2.0 platform was cancelled after the Rivian JV closed. Cariad now coordinates externally developed technology, primarily from Rivian for global markets and XPeng for China from 2026. So the phrase "built the next-gen VW software stack" now signals a project that was shelved. What survives on your resume are the specific components you shipped: the OTA backend, the ADAS perception module, the telematics gateway, the CI pipeline. Name the artifact, not the org.
€16B restructuring budget divided across up to 60,000 targeted cuts. That number is your severance leverage.
The numbers you are competing inside
CARIAD is a small slice of the headline layoff number, and the auto-software shortage outside Wolfsburg is real. Here is the open-web dataset that frames the market you are about to enter.
| Metric | Figure | Source |
|---|---|---|
| CARIAD headcount (founding intent, 2020) | ~6,000 | InsideEVs |
| CARIAD cuts already executed (2024/25) | 1,600 (~30%) | EV Magazine |
| Additional VW Group cuts approved Sept 3, 2026 | 50,000 | CNBC |
| Prior VW cuts already in progress | ~50,000 | CNBC |
| Share of new cuts in Germany | ~50% (~25,000) | Archyde |
| Auto-software demand vs supply, 2026 | 3.5× shortage | ManpowerGroup |
| CARIAD share of Future Plan 2030 headline cuts | ~3.2% | Derived |
Two things jump out. First, CARIAD is a small slice of the headline number, so you are not competing against 50,000 other embedded engineers. You are competing against the couple thousand software people actually being cut plus the tens of thousands of adjacent Audi and Porsche R&D staff who will drift into software-adjacent searches. Second, ManpowerGroup puts demand for experienced automotive software engineers at 3.5× supply. The shortage is real. It just is not in Wolfsburg.
Why the CARIAD line reads as "was on the Titanic"
CARIAD accumulated $7.5 billion in operating losses over three years, and outside Germany the name has become shorthand for the industry's software struggles. If your resume opens with "Senior Engineer at CARIAD, 2021 to 2026" and nothing else, a SaaS recruiter reads it as five years on a cancelled platform. You have to preempt the objection in the first bullet under the job.
The fix is to lead with what you personally shipped, with a number attached, before the reader gets to the org-level context:
- Cut OTA rollout latency from 42 hours to 6 hours across 1.2M vehicles
- Owned the CI pipeline for the ADAS perception stack; raised test coverage from 61% to 88%
- Shipped the cloud backend for feature X to production; 99.95% uptime over 14 months
- Led a 6-engineer team through ISO 26262 ASIL-B certification in 9 months
That is the exact translation work Refolk does automatically: paste your CARIAD job description and a target posting, and Refolk rewrites your history against the words the target actually uses. It pulls "OTA pipeline" forward for a SaaS DevOps role and "ISO 26262" forward for a medtech role, from the same underlying facts.
The two-resume rule for the CARIAD pivot
You need two resumes, not one, because the lateral market and the vertical market read completely different signals. This is the single highest-leverage move for an automotive software engineer pivot in 2026.
Resume A: the lateral, auto-adjacent version
This one leans into AUTOSAR, ASPICE, ISO 26262, CAN, LIN, Ethernet, and any specific ECU or domain controller you touched. It is aimed at Tier-1s and services firms that are hiring exactly this profile:
- KPIT and Tata Elxsi (services, actively recruiting ex-OEM software talent)
- Bosch, Continental, Aptiv (Tier-1 suppliers with SDV programs)
- Mobileye (ADAS)
- Chinese OEM subsidiaries setting up European engineering centers
- Rivian itself, which now owns the platform work CARIAD used to do
For this version, the CARIAD name is neutral to positive. The hiring manager knows the codebase and the certification regime. Keep the domain jargon; you will lose keyword matches by translating it away.
Resume B: the vertical, non-auto version
This one strips CAN bus, LIN, and AUTOSAR from the top third of the page and reframes your work as domain-agnostic disciplines. The sectors that pay for exactly this rigor:
- Medtech (IEC 62304, FDA 510(k) software)
- Aerospace and defense (DO-178C, DO-254)
- Industrial IoT and robotics (IEC 61508, safety PLCs)
- Fintech infra (payments and trading systems that care about latency and correctness)
- Cloud platform teams at any SaaS with a hardware or telemetry story
For Resume B, "AUTOSAR" becomes "component-based software architecture with static configuration and layered abstraction." "ISO 26262 ASIL-B" becomes "safety-critical system design with formal hazard analysis and traceable requirements." "CAN bus" becomes "real-time messaging over constrained networks." You are not lying, you are speaking the language of the reader.
The five translations that do the most work
Here are the specific phrase swaps that move an embedded software resume from something recruiters skim past into one they actually read. Each matters because the ATS keyword filter and the human reader are looking for the vertical-native term.
- "AUTOSAR Classic / Adaptive" becomes "C++ real-time framework with layered runtime and static configuration" for cloud and platform roles, or stays as-is for Tier-1s.
- "ISO 26262 ASIL-B" becomes "safety-critical software lifecycle with hazard analysis, traceability, and independent verification" for medtech, aerospace, and industrial IoT.
- "ASPICE Level 2" becomes "formal process maturity with reviewed requirements, bidirectional traceability, and audited change control" for regulated fintech and healthtech.
- "CAN, LIN, FlexRay, Automotive Ethernet" becomes "deterministic messaging protocols over bandwidth-constrained networks" for IoT and edge platforms.
- "HIL / SIL testing" becomes "hardware-in-the-loop and simulation-based integration testing for embedded targets" for robotics and industrial automation.
Name the artifact you shipped, not the org that shelved the platform.
Use the severance window the German market gives you
At an implied €267,000 per position under Future Plan 2030, CARIAD engineers have a reskilling runway that engineers in leaner markets simply do not get. Between IG Metall under Christiane Benner, works council leverage under Daniela Cavallo, and German co-determination, voluntary departure packages in this round are expected to fund a 6 to 12 month gap credibly.
Here is what to do with that window, in order of ROI for the pivot:
- A cloud certification with a real project attached. AWS Solutions Architect Professional or CKA (Certified Kubernetes Administrator) plus a public GitHub repo where you deployed something non-trivial. The cert alone is a checkbox, the repo is the proof.
- A portfolio project that is not automotive. Contribute to an open-source project in the vertical you are targeting. For medtech, that might be an OHIF or Orthanc contribution. For fintech, a real payments or ledger project.
- A blog post explaining ISO 26262 to non-auto engineers. Three posts, published on your own domain, indexed by Google, linked from your LinkedIn. This is how you signal that you can translate.
- Two live target-role interviews per week from month two onward. Do not save your applications until the cert is done. The interviews teach you which parts of your resume are landing.
Over 40 applications, per-posting tailoring is 40 resumes you did not have to rewrite by hand and 40 fit scores that tell you whether a posting is worth the interview prep before you spend the time. Refolk does that tailoring per application; the alternative is a single generic CV against openings that each want different keywords.
The four objections you will get, and the answer to each
Every CARIAD engineer interviewing outside auto in Q4 2026 and Q1 2027 will hear some version of these. Have the answer ready in the first 30 seconds.
- "Wasn't CARIAD kind of a mess?" Yes at the org level; here is the specific thing my team shipped and the metric it moved. The platform decision was above me.
- "Do you know cloud-native tooling?" Show the repo and the cert. If you do not have them yet, name the two you are 60 days from finishing.
- "You have only worked in one industry." Frame safety-critical embedded as a discipline used across medtech, aerospace, and industrial. Name one specific parallel (IEC 62304 vs ISO 26262).
- "Why should we pay SaaS comp for someone from an OEM?" Because auto software demand exceeds supply 3.5× per ManpowerGroup's 2026 read, Tier-1s are actively bidding, and you have a competing offer or a plausible one.
The one thing not to do: apologize for the CARIAD line. It is on your resume because you shipped things there. If you can name three of them with numbers, that job is an asset. If you cannot, that is the actual problem, and it is a resume problem, not a career problem. Fix the resume.
FAQ
Is now a bad time to interview outside automotive from Germany?
No. The auto-software shortage is 3.5× and Tier-1 suppliers like Bosch, Continental, KPIT, and Tata Elxsi are hiring the exact CARIAD profile. Outside auto, medtech and industrial IoT are actively looking for ISO 26262-caliber engineers under IEC 62304 and IEC 61508. The market is soft for generalist SaaS engineers in 2026, but it is not soft for safety-critical embedded specialists who can translate their work.
Should I list CARIAD or just "Volkswagen Group"?
List CARIAD if you are applying to any auto, Tier-1, or supplier role, because the codebase and certification regime are known. For SaaS, medtech, or fintech, list "Volkswagen Group (CARIAD software unit)" so the reader anchors on the parent brand first. Either way, the first bullet under the job must be a shipped artifact with a number, not a job description.
How do I handle the Rivian and XPeng pivot in interviews?
Treat it as evidence you worked on a platform mature enough that a major automaker chose to integrate external code alongside it. Do not defend the cancellation. Instead, name the specific module you owned, whether it survived the transition, and what you learned about integrating third-party stacks - a skill every SaaS platform team values. If your work was on E3 2.0 and got shelved, own that and pivot to the reusable pieces: CI, cloud backend, OTA, testing infrastructure.
Do I really need two versions of my resume?
Yes. The lateral Tier-1 reader wants AUTOSAR, ASPICE, and CAN in the top third. The vertical SaaS, medtech, or fintech reader wants those same skills translated into domain-agnostic language, or they will filter you as too niche. Maintaining two versions by hand is tedious, which is why per-posting tailoring is the actual unlock for a CARIAD layoffs resume in this cycle.