Porsche Technologies Merger: Sourcing the 747 and the Shadow Pool

On October 7, 2026 at the Weissach Development Centre, Porsche presented "Sportwagenschmiede '35" and folded Porsche Engineering and Porsche Digital into a single unit called Porsche Technologies. Management positions are being cut by 40%, functional headcount by 25%, and a Handelsblatt-reported proposal adds roughly 4,100 further cuts on top of the 9,000 already agreed through 2035. For anyone building an SDV, EV, or mobility org, this is the biggest involuntary release of German automotive software talent since the Cariad reorg, and the window is open now.

What actually changed at Weissach on October 7

Porsche merged Porsche Engineering and Porsche Digital into one entity, "Porsche Technologies," with an explicit mandate to use global R&D at lower cost and cut development cost per vehicle line by up to 20%. This is the second software-org collapse at Porsche in the same calendar year: the Car-IT division was dissolved and absorbed into R&D on July 1, 2026, when Sajjad Khan exited the executive board.

The structural pieces to remember:

• Porsche Technologies replaces both Porsche Engineering (Weissach, Ludwigsburg, Prague, Cluj, Nardò, Shanghai) and Porsche Digital (Berlin, Ludwigsburg, Palo Alto).
• Management cut by 40%, functional headcount by 25%, inside the new unit.
• ~9,000 positions already covered by prior agreements through 2035; the Handelsblatt leak adds ~4,100 more, for a potential total of ~13,100 against a 41,780-person end-2025 base.
• CEO Michael Leiters (ex-Ferrari, ex-McLaren), who replaced Oliver Blume at the start of 2026, denied the 4,100 figure in a September 21, 2026 internal message, which means works-council negotiations, not announcements, will set the pace.

That denial matters more than the number. Porsche is in Germany, which means separations happen through Betriebsrat negotiation, which means employees spend 6 to 18 months in limbo with no severance in hand. That is the exact window where passive candidates finally read InMail. Compare to Cariad in 2024, where announced severance froze the market for 9 months.

13,100

Why "747" undercounts the real pool by roughly 3x

The 747 figure Revelio Labs reported for Porsche Digital as of March 2026 is only the digital-services staff; the actual addressable candidate pool for SDV recruiters is closer to 2,500 to 3,500 engineers. The multiplier comes from four parallel events happening inside the same calendar year.

1. Porsche Digital, 747 people (Revelio Labs, March 2026) now under the 25% functional cut.
2. Porsche Engineering, roughly 1,900 people globally, now subject to the same mandate and sitting next to lower-cost Cluj, Prague, and Shanghai sites that are being expanded.
3. The dissolved Car-IT division, folded into R&D on July 1, 2026, with reporting-line churn ongoing.
4. MHP, Porsche's consulting subsidiary, being sold to Tata Consultancy Services. In precedents like SAP/Sybase and IBM/PwC Consulting, German consultants absorbed into Indian IT services acquirers have seen 20% to 40% voluntary senior attrition within 18 months.

Add the shuttered Cellforce battery cell unit, the closed Porsche eBike Performance, and divested Rimac and Bugatti Rimac stakes, and the Porsche-ecosystem displacement is far wider than the headline number. Most of these engineers are not laid off. They are sitting under a 25% cut mandate with no severance deal, which is a better sourcing signal than a termination letter.

The Stuttgart corridor map, in named employers

The single biggest competitor you will face for ex-Porsche Technologies engineers is Bosch Engineering GmbH in Abstatt, roughly a 10km drive down the B14 from Weissach. In Refolk's index, 97 software engineers, developers, and architects match the Stuttgart-area automotive-SW slice Porsche Technologies will shed, and Bosch Engineering alone accounts for 8 of them, roughly 8x the gravitational pull of any other named employer in that slice.

Top regional concentrations in the same slice:

• Stuttgart (Porsche HQ, Mercedes-Benz, broader Baden-Württemberg automotive cluster)
• Abstatt (Bosch HQ for powertrain electronics)
• Munich (BMW, Cariad)
• Kaiserslautern (Porsche Engineering's largest non-Weissach site)

If you are a US SDV employer, your real competition is not a transatlantic move. It is a short commute down the B14 and a modest base-salary bump at Bosch. Price accordingly, and lead with product scope and SDV ownership rather than relocation packages.

Who to target: the German cohort that does not move to Cluj

Target German-based product managers, UX engineers, cloud and backend engineers, and MLOps leads, because those are the roles that do not migrate cleanly to Cluj, Prague, or Shanghai. The merger is explicitly a cost-arbitrage play toward Porsche Engineering's lower-cost sites, with a stated goal of cutting development cost per vehicle line by up to 20% through modular development and expanded in-house capacity at those locations.

What that implies in practice:

• Embedded C/C++ engineers at Cluj and Prague are safer than Berlin product designers. Do not waste cycles there.
• Weissach, Ludwigsburg, and Berlin digital-product staff carry the highest involuntary-attrition probability.
• Cloud and backend engineers who built Porsche Digital's connected-car and charging backends have transferable stacks that Rivian, Lucid, Scout Motors, and Cariad hire into directly.
• MLOps and data engineers on predictive maintenance, telematics, and ADAS data pipelines map to any SDV employer.
• UX and design engineers on HMI and companion app are the most portable globally. They also do not speak Romanian.

This is a sourcing problem of describing the person precisely rather than running yet another LinkedIn boolean. "Cloud backend engineer, currently at Porsche Digital or Porsche Engineering in Berlin or Ludwigsburg, built connected-vehicle or charging backends, open to Munich or remote EU" is the kind of query that falls apart in a traditional search builder, which is the exact gap Refolk closes: describe the person in plain English and get a ranked shortlist across GitHub, LinkedIn, and the open web.

The MHP to TCS pool nobody is sourcing yet

MHP, Porsche's management and IT consulting subsidiary, is being sold to Tata Consultancy Services, and the resulting German automotive consultant pool is the parallel displacement event most SDV recruiters have missed. Historical precedent (SAP/Sybase, IBM/PwC Consulting) suggests 20% to 40% voluntary attrition at the senior-consultant level within 18 months of a German-to-Indian-IT-services acquisition.

Why MHP consultants matter for automotive software sourcing:

• They have sat inside OEM programs at Porsche, Audi, Mercedes, and BMW, often as the de facto architects for vehicle data platforms and dealer management systems.
• They carry the OEM Rolodex that in-house engineers do not.
• Many are ex-OEM engineers who went to MHP for the day rate; they are reachable with the right pitch about going back in-house, at scale.
• The acquisition starts the clock on senior earn-out windows, which is when the controlled exits begin.

If you are hiring product managers or solution architects for an EV charging network, a fleet platform, or an SDV program, this is the pool. Nobody is sourcing it against you yet.

Management denied the 4,100 figure. That paradoxically opened the sourcing window, because disputed leaks drag works councils and freeze severance.

The US angle: PCNA and the Atlanta competitive set

Porsche's own likely US sink for retained engineering roles is Porsche Cars North America in Atlanta, which Refolk's index shows as the single largest Porsche-keyword employer with 10 of 80 engineering profiles. The direct US competitive set for those same engineers is Lucid Motors, Rivian, Scout Motors, and the US arm of Cariad.

What this means in practice: if a US employer wants to recruit a German Porsche Digital or Porsche Engineering lead into an Atlanta, Palo Alto, Newark, or Novi role, the counter-offer is almost always PCNA holding them in Atlanta, not Bosch holding them in Abstatt. The economics flip for different candidate cohorts, and your sourcing short list should be partitioned accordingly.

A 60-day sourcing plan while the works council negotiates

Run a 60-day plan that pipelines the Porsche Digital 747, the broader Porsche Engineering 1,900, and the MHP pool in parallel, and resist the temptation to wait for a WARN-equivalent announcement that will not come in Germany. The works-council process means you have time, but the engineers you want have already started conversations with Bosch Engineering, Mercedes-Benz, and Cariad.

Week by week:

1. Weeks 1-2. Build three named lists: Porsche Digital Berlin and Ludwigsburg, Porsche Engineering Weissach, MHP senior consultants. Prioritize cloud, backend, MLOps, UX, and product management titles. Skip the Cluj and Prague embedded engineers.
2. Weeks 3-4. First-touch outreach that references the merger by name and offers a scoped conversation, not a job. Reply rates are highest when the engineer has not yet picked their next employer.
3. Weeks 5-6. Loop in hiring managers for a 20-minute scoping call rather than a formal interview. German candidates in Betriebsrat limbo need low-commitment next steps.
4. Weeks 7-8. Lock in offers before the next reporting-line reshuffle inside the new Porsche Technologies unit, which is when internal retention counter-offers will start landing.

97

FAQ

How many engineers are actually at risk from the Porsche Technologies merger?

The headline number is 747 Porsche Digital employees per Revelio Labs (March 2026), but the real addressable pool is closer to 2,500 to 3,500 once you add Porsche Engineering's roughly 1,900 global staff, the dissolved Car-IT division, and MHP consultants exposed to the Tata Consultancy Services acquisition. Not all of those will separate, but all of them are now sitting under a 25% functional cut mandate with reporting-line uncertainty, which is the condition under which passive candidates reply.

Why is Bosch Engineering the main competitor rather than Mercedes or BMW?

Because of commute distance and brand familiarity. Refolk's index shows Bosch Engineering GmbH holding roughly 8x the Stuttgart-area automotive software gravitational pull of any other named employer in the matched slice, driven by the Abstatt powertrain-electronics HQ sitting about 10km from Weissach down the B14. For a US SDV employer, the realistic competition is not Rivian versus Mercedes, it is your Atlanta or Palo Alto offer versus a short-commute Bosch role at a modest premium.

When does the sourcing window actually close?

Likely not before mid-2027 for the Porsche Digital and Porsche Engineering cohort, because Michael Leiters publicly denied the 4,100 figure in a September 21, 2026 internal message, which means works-council negotiations will drag. The window closes faster for the MHP consultants, where the Tata Consultancy Services acquisition will trigger controlled senior exits over the first 18 months. Compare against Cariad in 2024, where announced severance froze the market for 9 months before releasing a wave.

What roles should US employers specifically target?

Target German-based cloud and backend engineers, MLOps leads, UX and HMI engineers, and digital product managers from Weissach, Ludwigsburg, and Berlin. Skip embedded C/C++ roles at Cluj and Prague, which the merger is explicitly expanding rather than cutting. For Atlanta-based roles, your main counter-offer problem is Porsche Cars North America retaining its own; for Palo Alto and Newark roles, it is Lucid, Rivian, Scout Motors, and Cariad hunting the same list.