Technical Lead Aftersales

Development, maintenance, operations of Aftersales applications and infrastructure for Premium German OEM:
• Securing Global Serviceability
• Modernization & Cloudification
• Efficiency through Modularization
• Innovation & Quality
• Global Compliance

Responsibilities

Overall program responsibility for successful delivery, reporting, customer interfacing with strong domain know-how to build-up the delivery team.

Skills

Must have

Technical lead for an Engineering program for Aftersales for OEM about diagnostics/programming platform — someone who experience with building and maintaining the tool side, not just consumed it as a workshop technician

Automotive diagnostics/aftersales IT, ideally with experience at an OEM or a systems integrator working directly on the diagnostics toolchain

Comfortable operating at the intersection of vehicle electronics and IT application development — understands both worlds

Required domain expertise (automotive diagnostics & workshop systems):

Hands-on experience with an OEM workshop diagnostics platform (e.g. BMW ISTA, Mercedes XENTRY/DAS, VW ODIS, Porsche PIWIS, Audi VAS, or equivalent Tier 1 suite)

Client-side vehicle communication protocols: UDS (ISO 14229), DoIP (ISO 13400), OBD-II, KWP2000, CAN (ISO 11898), MOST, Ethernet — how the tool initiates sessions, sends requests, and interprets responses

ECU programming orchestration: therapy plans / flash sequences, precondition management (battery, vehicle state, network), multi-ECU coordination, rollback and recovery, post-flash configuration

Vehicle configuration models: how vehicle orders (FA), installed configurations (FP), software levels (I-Stufe), and master records (VCM or equivalent) drive diagnostic routing, programming eligibility, and fault code interpretation

Diagnostic content pipeline: how engineering data (specifications, measurement parameters, programming files) flows from OEM development into the tool — compilation, packaging, distribution, versioning

Workshop hardware interfaces: ICOM / VCI / PassThru devices, measurement hardware (IMIB or equivalent), physical connections (OBD, Ethernet gateway), and real-world failure modes (intermittent connections, mixed ECU generations, partial updates)

Protocol abstraction layers: middleware between tool and vehicle bus (e.g. EDIABAS, D-PDU API, ODX/OTX runtimes) — what they abstract, how they fail, how to debug them

Release and validation: testing tool releases against physical vehicles, and regression testing across 15+ years of vehicle generations

Nice to have

Desired technical background (less critical than domain, but helpful):

.NET / C# ecosystem (the platform is a large .NET 4.8 WPF windows desktop application)

Azure cloud services (parts of the platform are migrating to cloud-native)

Understanding of CI/CD pipelines for desktop application distribution (MSI packaging, staged rollouts to workshops)

Familiarity with ITSM processes in an automotive workshop context (incident triage, known error databases, L2/L3 support for a globally deployed tool)

Other

Languages

English: C1 Advanced,German: C2 Proficient

Seniority

Senior