PpWe're looking for a Build System Engineer to join a forward-thinking Software Engineering organisation within a major global automotive OEM. The role sits at the core of a large-scale software build transformation — owning and advancing the build system as a first-class platform product, enabling fast, reproducible, and scalable software delivery across embedded ECUs, infotainment, telematics, and central compute domains. /p ul liContract type: Permanent or freelance /li liBenefits: Competitive package; high-impact, high-visibility role within a major software-defined vehicle programme /li /ul h3Responsibilities /h3 ul liDeliver reproducible, hermetic builds across host and embedded targets on Windows and Linux /li liMake quality first-class — integrating SBOMs, licence checks, standards enforcement, and tests directly into the build /li liProvide clean abstractions so that developers interact through a stable, consistent interface /li liTighten CI/CD integration and drive build and test performance insights /li liSteward ecosystem coherence through shared conventions and inner-source contribution /li liEnable large-scale migration to variant-aware, cross-ECU build setups /li liCommunicate clearly with developers and stakeholders, building trust through pragmatic standards and a strong developer experience focus /li /ul h3Qualifications /h3 ul liStrong C/C++ skills; proficiency in Rust or Python also required /li liProven track record delivering reproducible builds on Windows and Linux at scale /li liExperience with variant-aware and platform-aware build setups /li liComfortable integrating quality gates and tests directly into the build pipeline /li liGraph-first, pipeline-second mindset — platform thinking with a "make the whole system better" attitude /li liPragmatic and collaborative, with strong stakeholder and cross-team partnership skills /li liAutomotive or embedded experience (safety, standards, reproducibility) is a plus /li liMonorepo migration experience is advantageous /li liFamiliarity with AUTOSAR architecture (Classic Adaptive) is beneficial /li liExperience treating rules, toolchains, and configs as product assets is a plus /li /ul /p #J-18808-Ljbffr