You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Flox

Senior Software Engineer, Packaging

  • Remote
  • 6+ years

Salary

$180,000 - 250,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

Reports to the VP of Engineering.

The company builds developer tools that help teams manage software environments securely and reproducibly. The platform is built on Nix and combines command-line tools, cloud services, and build infrastructure for engineers who care about how software is made.

The company is working on a secure packages product and an AI release engineer project.

The secure packages product keeps a large set of open source packages current and patched, builds them reproducibly, and delivers them to customers. A distributed build system sits behind it. It watches upstream releases, updates packages, builds and tests them across many execution environments, and publishes the results.

Much of the routine update work is automated, including by AI agents, so your packaging judgment is what separates a sound change from one that only looks correct.

Responsibilities

  • Keep packages building, current, and patched by diagnosing build failures, dependency conflicts, and regressions, and making real fixes rather than workarounds.
  • Build and improve the pipeline that detects upstream releases, updates packages, tests them, and publishes them.
  • Run and scale the distributed build infrastructure, and take part in on-call duty for the services you build.
  • Maintain the downstream package set on a fast-moving upstream, carrying changes, upstreaming them, and retiring them when they are no longer needed.
  • Review changes produced by automation and AI, and improve the tooling that generates them.
  • Work with product, infrastructure, and security engineers on scope, architecture, and delivery.

Requirements

  • Hands-on work 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 the ability to debug them.
  • Experience building or operating distributed build systems, such as build farms, remote builders, binary caches, or large-scale CI.
  • Strong software engineering skills: you can design, build, and ship production services and pipelines. The backend is written in Python.
  • Solid Linux fundamentals.
  • Understanding of how vulnerabilities relate to packages and versions, and what it takes to ship a fix.
  • Clear communication and sound judgment when weighing tradeoffs.

Where you’d work

Fully remote

You can work from

  • United States

About the company

Flox

  • Industry: SaaS

3 of their 3 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 22 checks run
  • 0 red flags

Still hiring?

15 checks

No red flags

How crowded?

7 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details11 facts · Role, Location, Compensation, Company
Tech stack
  • Python
  • Go
  • Linux
Seniority
Senior
Industry
SaaS
Specialty
Backend
Region
United States
Pay period
Annual
Show 5 more factsShow less

Role

Category
Development
Specialty
Backend
Seniority
Senior
Experience
6+ years
Tech stack
  • Python
  • Go
  • Linux

Location

Work model
Remote
Region
United States
Remote from
  • United States

Compensation

Salary
$180,000 - 250,000 / year
Pay period
Annual

Company

Industry
SaaS

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason