BCG · Tech Consulting · Hard · 35-45 min

German Automaker's Software-Defined Vehicle Bet

German Automaker's Software-Defined Vehicle Bet is a hard BCG tech consulting case interview that runs 35-45 min. A German premium OEM has spent €2.1B on an in-house vehicle operating system. A strong answer works through 5 phases: Split the stack; Score build vs buy vs partner on each layer: differentiation, safety case, patch rights, and time to SOP; Quantify the slip; Design the software organization: what the OEM must own (vehicle API, update pipeline, cybersecurity case) even if a supplier writes code; Recommend a cut line, a revised SOP, and the board narrative for the €900M that is not spent.

Last updated 2026-09-05

The brief

A German premium OEM has spent €2.1B on an in-house vehicle operating system. Start of production has slipped 20 months. Warranty software defects are up, and two domain controllers still ship with supplier code the OEM cannot patch over the air. The board is split: the CTO wants another €900M to finish the stack; the CFO wants to adopt Android Automotive for infotainment and keep a thin in-house layer for driving and safety. UNECE R155/R156 cybersecurity and software-update rules apply to every new type. You have six weeks to recommend where to keep building and where to stop.

How to approach it

  1. Split the stack — infotainment, body and comfort, ADAS and safety — and stop treating 'the OS' as one bet
  2. Score build vs buy vs partner on each layer: differentiation, safety case, patch rights, and time to SOP
  3. Quantify the slip — delayed revenue, warranty, and the €2.1B already spent as sunk for the go-forward decision
  4. Design the software organization: what the OEM must own (vehicle API, update pipeline, cybersecurity case) even if a supplier writes code
  5. Recommend a cut line, a revised SOP, and the board narrative for the €900M that is not spent

What a strong answer does

  • Separates brand-differentiating software from commodity infotainment
  • Treats over-the-air patch rights and the UNECE update case as the strategic asset, not the lines of code
  • Ignores sunk €2.1B when choosing the go-forward path and still explains it to the board
  • Gives suppliers a lane without giving away the ability to ship a fix
  • Puts a dated SOP back on the table with a smaller scope

Red flags interviewers score down

  • Recommends finishing the full in-house stack because €2.1B is already spent
  • Hands ADAS safety code to a consumer OS with no safety case
  • Talks architecture and never mentions start of production or warranty
  • No view on who signs the cybersecurity type approval

Cases are written in each firm's style, written and reviewed by working consultants; they are not the firms' own published cases.

More BCG cases