Development Engineer, Facility Software Automation

ABOUT FLUIDSTACK We exist to make humanity more free. For most of human history, you farmed or you starved. Technology gave people more time for the things they wanted to do, instead of things they had to do. Powerful AI will be the biggest lever for human choice we've ever built - but only if models are aligned with what humanity actually wants. There are groups building AI who don't share these goals. Whoever deploys frontier compute infrastructure fastest will decide whether AI expands human freedom or shrinks it. We're singularly focused on delivering 10 to 100s of GWs of compute faster than anyone else, rethinking every layer of the stack. We acquire power, design and build data centers, and operate them - with teams spanning hardware and software. Speed and scale are our key differentiators. Come be a part of building civilization-scale infrastructure for AI. We hire people who care deeply about this problem space. If that is you, please apply! HOW WE OPERATE - Extreme ownership. Full autonomy. Own things end to end often taking on scope outside your core role without being asked to get things done. - Velocity. We drive everything forward as fast as possible. - First principles. Challenge every assumption. Zero analogy thinking, no egos, the best idea wins. - Love of the game. The frontier of AI is the most interesting problem of our time. We put in long hours at high intensity to push the frontier forward. THE FACILITY SOFTWARE AUTOMATION TEAM Examples of key problems the team is working on - We do not just watch infrastructure run. We use the signals we collect to build automations that act on it -- compressing the time between a facility coming online and compute being in customers' hands. Detect, decide, act. If we fail to do any one of those three, we lose the trust of the customers who depend on us to keep the frontier moving. - Bad telemetry is a trust failure at gigawatt scale. Every facility Fluidstack operates runs on the data we collect. A missed signal is a missed alert. A missed alert is a customer running frontier AI workloads on infrastructure that cannot see itself. At the scale we are building, that is not a monitoring gap -- it is an outage. - The platform has to scale as fast as the build does. Fluidstack delivers gigawatts of compute in six months -- a fraction of the industry's 18 to 24 month timeline -- and every new site adds more devices, more signals, and more automation decisions that depend on clean data. The telemetry platform either grows ahead of the business or it becomes the constraint that slows it down. ROLE SCOPE - Own the infrastructure underpinning the Facility Software Automation platform: cluster architecture, deployment configuration, and the operational reliability of every service in the stack. - Own and manage containerization workflows and CI/CD pipelines for telemetry services, making deployments from commit to live in production fast, safe, and repeatable without manual intervention. - Own the observability layer, Prometheus, alerting, and dashboards, that gives the platform team and Fluidstack operations the signal to catch problems in telemetry pipelines before they hit downstream teams. - Drive infrastructure-as-code standards across the platform so every environment change is version-controlled, reviewed, and auditable at the pace of a team shipping continuously. - Work directly with engineers to take new telemetry services from first commit to production-ready deployment, setting the bar for what production-ready means on this platform. WHAT WE'RE LOOKING FOR The below is a starting point. We always make space for exceptional people, so if you don’t fit this role exactly, tell us where you would https://jobs.ashbyhq.com/fluidstack/05c2e69c-42f9-4fcb-9cf0-a467aaf98f1c. - You have owned container-based infrastructure in production: designed the architecture, debugged the failure modes that only appear under load, and carried the pager for it. - You treat telemetry pipeline health and data integrity as non-negotiable, since the automation that delivers compute to customers depends entirely on the reliability of the data flowing underneath it, and you build and operate accordingly. - You have hands-on experience with containerization technologies (Docker, Kubernetes, or equivalent) and have used them to build deployment workflows that engineering teams depend on without thinking about it. - You have built CI/CD pipelines that engineers actually trust, where a merged PR reaches production safely without anyone watching over it, and you understand modern development workflows well enough to build them from scratch. - You drive infrastructure-as-code as a functioning discipline: every environment change is version-controlled, reviewed, and auditable, and you hold the platform to that standard. - You have built observability stacks from scratch (Prometheus, Grafana, OpenTelemetry) and you know the