• Own the technical vision, architecture, and roadmap for Developer Experience platforms, including: • Developer portals and internal platform products • CI/CD pipelines and code delivery systems • Container-based developer and runtime environments, including orchestration and lifecycle management • API platforms, service templates, and established “golden paths” • Observability, reliability, and operational tooling • Lead ****DevX**** platforms as products, with: • Clear ownership and accountability • Roadmaps informed by real developer needs • Defined reliability, security, and service expectations • Act as a hands-on technical leader: • Review architecture, designs, and system patterns • Apply practical engineering judgment to platform and tooling decisions • Make informed trade-offs across scalability, security, reliability, and usability • Provide deep technical leadership across polyglot engineering environments, spanning modern backend, frontend, mobile, data, and distributed systems technologies • Apply strong understanding of multiple programming paradigms (object-oriented, functional, reactive, event-driven) to ensure DevX initiatives align with how engineers actually write and maintain code. • Be accountable for core repository strategy and health, including: • Code organization and modularization • Dependency, version, and release management • Shared libraries, frameworks, and reuse patterns • Secure, compliant contribution and governance models • Define and own a multi-year Developer Experience strategy aligned with: • Automotive and industrial software delivery constraints • Safety, security, and regulatory requirements • Operating at scale across global regions, time zones, and organizational boundaries • A broad and evolving technology landscape, spanning legacy systems through modern and emerging (“bleeding-edge”) platforms • Ensure DevX initiatives reflect real developer workflows, operational constraints, and production realities • Balance standardization and autonomy through well-designed paved paths that support consistency while enabling innovation • Define, own, and continuously evolve Developer Experience KPIs that measure productivity, reliability, code quality, delivery performance, and developer sentiment • Establish a ****DevX**** measurement framework that combines: • Quantitative engineering metrics (e.g., lead time, deployment frequency, change failure rate, recovery time) • Platform usage, adoption, and reliability signals • Regular developer surveys and qualitative feedback mechanisms to identify friction and unmet needs.