The buyer question
Which decisions define the Wolfsburg automotive-software mandate — vehicle-software platforms under the Volkswagen transition, in-vehicle and connectivity software, or factory digitalisation — and which software outcomes will the candidate personally own?
What the public record shows
The transition frame is the verified VW record: Golf relocation to Puebla from 2027, two lines instead of four at Wolfsburg, 734,000-unit capacity reduction, 35,000-plus workforce reduction by 2030 with more than €15 billion annual savings — and the BMW record's digital-controls standard: new lines integrating digital controls, automated logistics and robotics. Wolfsburg's software work serves the same transition.
Programme facts say nothing about any Wolfsburg employer's candidate pool, wages or vacancy duration.
What changes in this market
Wolfsburg software mandates split by layer. Vehicle-platform software proves itself in releases delivered at automotive scale. Connectivity software proves itself in shipped features. Factory-digitalisation software proves itself in systems live on operating lines. Transition-era evidence means software delivered through restructuring, not before it.
KiTalent's mandate analysis
- Name the layer — vehicle-platform software, connectivity, or factory digitalisation.
- For platform mandates, ask for releases delivered at automotive scale.
- For connectivity mandates, ask for shipped features.
- For factory mandates, ask for systems live on operating lines.
- Treat the transition programme as context; test compensation and availability against the live mandate.
Where the public record stops
Test those points against the live mandate.
Sources
Related KiTalent research
- The Market Map Is Not the Shortlist: why market coverage and candidate assessment are separate decisions in an executive-search mandate
- How to Assess a Leader Beyond Competencies: a practical framework for testing judgment, evidence and operating context after the brief is defined
