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

Member of Technical Staff, Infrastructure & Operations

  • 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

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 how software is made.

The company is also developing a secure packages offering and an AI agent for release engineering, aimed at keeping enterprises secure.

This role reports to the VP of Engineering.

Responsibilities

  • You will run and improve the infrastructure behind the company's SaaS platform, build systems, and development workflows, across cloud, CI/CD, monitoring, and production operations, so they stay reliable, secure, and simpler to maintain.
  • You will own the reliability of the customer-facing SaaS product and critical internal systems, and work with engineering to set and meet service-level objectives and customer commitments.
  • You will define and track service-level objectives for critical services, with measurement windows agreed with engineering.
  • You will take part in on-call rotation, investigate incidents, restore service, and run blameless reviews that lead to fixes preventing repeat failures.
  • You will provision and maintain production infrastructure with Terraform, AWS, and Nix-based tooling.
  • You will operate and improve the builders and build farm, covering reliability, capacity, build speed, caching, and storage.
  • You will maintain and improve CI/CD and release pipelines, adding deployment checks, staged rollouts, and dependable rollback so engineers can ship changes safely.
  • You will set up monitoring and alerts that show service health and customer impact across hosts, build infrastructure, and cloud services.
  • You will back up and regularly test restores and disaster recovery plans for critical services and data.
  • You will automate routine operations and build reusable tooling that lets the engineering team manage infrastructure safely.
  • You will manage secure access, networking, secrets, and infrastructure configuration together with the team.
  • You will plan capacity and improve efficiency, weighing reliability, performance, and cost.
  • You will write clear runbooks and documentation, and help engineers make services easier to operate and troubleshoot.

Requirements

  • You have substantial hands-on experience running customer-facing production services and a record of raising reliability and resolving hard incidents.
  • You have strong AWS and Terraform experience, including provisioning, maintaining, and troubleshooting cloud infrastructure.
  • You have strong Linux systems skills and practical troubleshooting across networking, DNS, storage, processes, and performance.
  • You have built and run CI/CD pipelines and supported software delivery.
  • You have experience with monitoring, alerting, and production incident response.
  • You have strong Nix experience, particularly running build infrastructure, remote builders, binary caches, or reproducible build systems.
  • You can write maintainable automation and tooling in languages such as Python, Rust, or shell.
  • You use sound judgment on operational risk and safe changes, knowing when to dig deeper or bring in another engineer.
  • You communicate clearly, write useful documentation, and work collaboratively on shared ownership.
  • You have experience managing a production NixOS fleet.
  • You have Kubernetes experience.
  • You have experience with PostgreSQL.
  • You have experience with Tailscale, Cloudflare, or similar networking and edge infrastructure.
  • You have experience operating Linux and macOS builders, bare-metal infrastructure, or distributed build systems such as Hydra.
  • You are familiar with GitHub Actions, self-hosted runners, Prometheus, Grafana, or Sentry.
  • You have experience improving software supply-chain security and protecting build and release infrastructure.
  • You have technical leadership experience, including planning infrastructure work, guiding decisions, and helping a team deliver operational improvements.

Conditions

This role includes on-call duty.

The company welcomes senior individual contributors and technical leads who share ownership with the team and stay close to the technical work.

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

Worth a look before you spend an evening tailoring a CV for it.

  • 22 checks run
  • 1 red flag

Still hiring?

15 checks

No red flags

How crowded?

7 checks

1 red flag

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
Details10 facts · Role, Location, Compensation, Company
Tech stack
  • Python
  • PostgreSQL
  • AWS
  • Kubernetes
  • Terraform
  • Linux
  • CI/CD
  • GitHub Actions
  • Prometheus
  • Grafana
  • Rust
Seniority
Staff
Industry
SaaS
Region
United States
Pay period
Annual
Show 5 more factsShow less

Role

Category
DevOps & Infrastructure
Seniority
Staff
Experience
6+ years
Tech stack
  • Python
  • PostgreSQL
  • AWS
  • Kubernetes
  • Terraform
  • Linux
  • CI/CD
  • GitHub Actions
  • Prometheus
  • Grafana
  • Rust

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