Embedded Linux Build & Release Engineer

⚠️ Please read before applying:Minimum 5 years of hands-on experience required, with at least one of AOSP, Android BSP, Yocto, firmware, or embedded Linux.This is Full-Time employment only — no B2B/contract engagements.Short-notice/immediate joiners preferred, though strong candidates with the right depth are still encouraged to apply.This is not cloud DevOps. If your background is primarily AWS/Azure/GCP, Kubernetes administration, or Infrastructure-as-Code for enterprise/web apps, this isn't the right fit — even with CI/CD tool experience layered on top. About the RoleBuild infrastructure, CI/CD, release automation, SBOM generation, and supply-chain security for Android and Linux platform development — across L4B's medical, automotive, and space-grade embedded product lines, all built on a shared core platform layer. This is a hands-on builder role. If a pipeline goes red and your instinct is to SSH into the build box and find out why — not file a ticket for someone else — this is your seat. Why This Role ExistsL4B's platforms depend on Android and Linux builds that just work, releases that can be reproduced and trusted, and a clear, provable record of what's actually inside what ships. This role owns that infrastructure — and increasingly, that's a regulatory requirement too: the EU Cyber Resilience Act mandates machine-readable SBOMs and continuous vulnerability monitoring for digital products sold into the EU, with full compliance due by December 2027. Key ResponsibilitiesBuild Infrastructure — Own Ubuntu build systems, build agents, runners, and build farm health; debug builds across Android, AOSP, Yocto, and embedded LinuxCI/CD — Set up and maintain GitLab CI, Jenkins, GitHub Actions, and Azure DevOps; build pipelines from scratch, no inherited pipeline is sacredBuild Failure Analysis — Diagnose toolchain, disk, memory, dependency, permission, and environment issues; independently recover broken pipelinesRelease Engineering — Own release packaging, artifact publishing, versioning, and release notes; guarantee build reproducibility and real release evidenceSBOM & Supply Chain — Implement Syft, SPDX, and CycloneDX; maintain software bill of materials and open-source visibilitySecurity Pipeline — Integrate Trivy, Grype, Snyk, Black Duck, Dependency-Track, and Yocto CVE checks into the build itselfAutomation — Build it yourself: Bash, Python, validation and release automation Must-Have Skills5+ years as a Linux-first engineer — not someone who occasionally touches LinuxReal Jenkins/GitLab CI experienceBuild server administrationStrong Bash and Python scriptingExperience with large native buildsAt least one of: AOSP, Android BSP, Yocto, firmware, or embedded Linux Good to HaveArtifactory, Nexus, or JFrogSBOM generation and CVE pipelinesRelease evidence generation Who This Role Is Not ForKubernetes administrators, Terraform engineers, AWS migration specialists, cloud-only DevOps engineers, or anyone whose CI/CD experience begins and ends with web apps. Also not for candidates seeking B2B/contract arrangements or under 5 years of relevant experience. If you'd rather own build farms and toolchains than cloud consoles, apply and let's talk.