Skip to content

Open nowPosted 3 days ago

Senior Software Engineer, Packaging

Flox5 open roles

Pay
$180,000 – $250,000 a year
Where
Remote
Work mode
Remote
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowSenior Software Engineer, PackagingFlox · Remote
  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Flox's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

14.3% of postings close within 7 days. Measured by our own scanner across the market. Flox postings stay open a median of 48 days.

Share of postings closed within
  1. 2.2%1 day
  2. 4.7%3 days
  3. 14.3%7 days
  4. 23.1%14 days
  5. 39.5%30 days
  6. 59.2%60 days
This job: posted 3 days ago

Flox median: 48 days open

The posting

Senior Software Engineer, Packaging

Reports to: VP of Engineering

ABOUT FLOX

Flox 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 ROLE

Secure 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 RESPONSIBILITIES

- Keep 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.

WHAT WE’RE LOOKING FOR

- 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.

STRONG SIGNALS

- 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.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Flox's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.
  3. We apply on Flox's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.
  4. Every reply, sorted

    Flox's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.
  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.