Senior Software Engineer, Packaging
This is the employer's own posting, not a copy on a job board.
What we know
Is it still open?
Confirmed still open
Last checked 1h ago — checked against the employer's own applicant tracking system, which is the company answering directly.
We re-read the employer's own applicant tracking system and the posting was still there. That is the company answering directly.
How old is it?
Posted 4h ago
The date the source published, not the day we noticed it (2026-11-17). Last seen at its source just now.
Is it remote?
Remote
That is the location the employer filed this posting under. Quoted as written — we do not re-word the source's own location.
Who may apply?
Not stated
The description states no restriction of its own. This is the source's own tag.
Pay
$180k–250k/yr
Published by the source in its own salary field. Shown in the posting's own currency and period; we never convert.
Skills named in the ad
Recognised terms only, from a fixed vocabulary — this is what CV matching compares against.
Carried by 1 source
-
Ashby employer's own board first seen 1h ago · last seen just now
The listing
Senior Software Engineer, Packaging
Reports to: VP of Engineering
ABOUT FLOXFlox builds developer tools that help teams manage software environments securely and reproducibly. Powered by Nix, our platform brings together command-line tools, cloud services, and build infrastructure for engineers who care about how software gets made. We’re also working on Secure Packages and an AI Release Engineer.
THE ROLESecure Packages keeps a large set of open source packages current, patched, and built reproducibly, and delivers them to customers. Behind it is a distributed build system: a pipeline that watches upstream releases, updates packages, builds and tests them across many execution environments, and publishes the results.
We’re looking for an engineer who knows how software gets packaged. You’ve maintained packages for an operating system or a language ecosystem, and you have good instincts about what a correct package and a sound fix look like. You’ll build and run the system that does this at scale, and when builds break, you’ll be the one who figures out why and fixes it.
Much of the routine update work is automated, including with AI agents. Your packaging judgment is what tells a good change from one that only looks right.
CORE RESPONSIBILITIESKeep packages building, current, and patched: diagnose build failures, dependency conflicts, and regressions, and fix them properly.
Build and improve the pipeline that detects upstream releases, updates packages, tests them, and publishes them.
Operate and scale the distributed build infrastructure behind it, and share on-call for the services you build.
Maintain our downstream package set on top of a fast-moving upstream, including carrying, upstreaming, and retiring changes.
Review automated and AI-generated package changes and improve the tooling that produces them.
Work with product, infrastructure, and security engineers on scope, architecture, and delivery.
Hands-on packaging experience with OS package managers (RPM, deb, apk, Nix, or similar) and language ecosystems (npm, Cargo, PyPI, Go modules, or similar).
Working knowledge of build systems such as CMake, Autotools, Meson, or Bazel, and how to debug them.
Experience building or operating distributed build systems: build farms, remote builders, binary caches, or CI at scale.
Solid software engineering: you can design, build, and ship production services and pipelines. Our backend is Python.
Strong Linux fundamentals.
An understanding of how security vulnerabilities relate to packages and versions, and what it takes to ship a fix.
Clear communication and sound judgment about tradeoffs.
Nix packaging experience: contributing to Nixpkgs and understanding how changes move through staging and channels.
Upstream maintainer or distribution work, for example at Red Hat, Debian, Fedora, Ubuntu, Alpine, or Wolfi.
Experience with distribution build systems such as Koji, Open Build Service, Launchpad, or Hydra, or with self-hosted CI and remote execution (GitHub Actions runners, Buildkite, Bazel).
Experience backporting security fixes.
Familiarity with vulnerability and supply-chain data such as CVEs, OSV, VEX, SBOMs (SPDX, CycloneDX), or signing and provenance (Sigstore, SLSA). We don’t expect all of these.
Experience with workflow orchestration such as Temporal.