Remote job
Member of Technical Staff, Secure Packages
Job details
About this role
Role overview Keep a large open-source package set current, secure, and reproducibly built, while developing and operating the distributed systems that update, test, and publish packages. You’ll bring practical packaging judgment to both routine maintenance and automated changes, diagnose failures when builds or dependencies break, and share responsibility for the services behind the pipeline.
Responsibilities - Diagnose package build failures, dependency conflicts, and regressions, then implement and verify appropriate fixes. - Improve the pipeline that detects upstream releases, updates package definitions, runs tests, and publishes results. - Operate and scale distributed build infrastructure, such as build farms, remote builders, binary caches, or large CI systems; participate in on-call. - Maintain downstream packages against upstream changes, including carrying, upstreaming, and retiring patches. - Review automated and AI-generated package updates and improve the tools that produce them. - Collaborate with product, infrastructure, and security colleagues on technical scope and delivery.
Requirements - Hands-on packaging experience with an OS package manager such as RPM, deb, apk, or Nix, and with a language ecosystem such as npm, Cargo, PyPI, or Go modules. - Working knowledge of build systems such as CMake, Autotools, Meson, or Bazel, including debugging build issues. - Experience building or operating distributed build systems or CI at scale. - Ability to design, build, and ship production services and pipelines; the backend is written in Python. - Strong Linux fundamentals and an understanding of how package versions relate to security vulnerabilities and fixes. - Clear communication and sound judgment when weighing technical tradeoffs.
Nice to have Nix packaging or contributions to Nixpkgs; distribution or upstream maintenance experience; familiarity with build systems such as Koji, Open Build Service, Launchpad, or Hydra; security fix backports; supply-chain data and tooling such as CVEs, OSV, VEX, SBOMs, Sigstore, or SLSA; or workflow orchestration such as Temporal.