Infrastructure Engineer

Flint runs background agents that make changes to real codebases and serves AI-generated pages at scale. That creates an infra problem most companies don't have: many agents editing code in parallel, and you have to coordinate, merge, and ship their work without it turning into chaos. You'll own the systems that power all of it: cloud architecture, CI/CD, deployments, observability, and security. It's a 0-to-1 role: you'll inherit a scrappy setup and make it production-grade.

Responsibilities

The concurrency and coordination problems of running many background agents in parallel, the core hard problem of this role; Cloud infrastructure end-to-end: architecture, provisioning, CI/CD, deployments; Cutting latency and cost as we scale, without trading off reliability; Observability and incident response, so we know when things break before users do; Security across the stack and deployment pipelines; Making it easy for product engineers to deploy confidently and debug fast

Requirements

You've scaled a product through real user growth and know what breaks, and when.; You're strong with cloud (AWS or GCP), containers (Docker/Kubernetes), and IaC (Terraform or Pulumi).; You think in systems, performance, reliability, and cost trade-offs come naturally.; You can drop into infra you didn't build and make it better without a runbook.

Nice to have

You've been through a startup growth phase; Security depth: SOC 2, threat modeling, or pen testing; You've built self-service tooling that product engineers actually used

Benefits

Historic office in Jackson Square (with 2 rooftops and a shower); A crazy upside-down battlestation; 20 PTO days a year; Full health benefits; Lunch and a fully stocked snack bar at the office, incl. Cometeer coffee pods; Dog friendly; Competitive salary + equity; More benefits coming very soon