Software 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!

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

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.

• Build and own production services across the telemetry collectors, ingesters, and automation stack that every downstream Automation and Operations team depends on.

• Design and evolve the messaging and time‑series data layer that ingests real‑time telemetry from device signals across the global compute fleet.

• Own the software infrastructure and data lake underpinning the platform, setting the data contracts and engineering standards other teams build against.

• Build the APIs and dashboards that surface telemetry to commissioning, operations, and leadership teams in real time.

• Drive the integration between device-level data streams and the automation API layer as the platform scales to new sites.

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.

• You’ve built and owned production services that other teams depend on, and you don't ship code you wouldn't want to be paged for at 3am.

• You treat telemetry pipeline health and data integrity as non-negotiable, because the automation decisions that deliver compute to customers are only as good as the signal underneath them.

• You’ve worked with high-throughput messaging systems (NATS, Kafka, or equivalent) at real scale and know where the failure modes show up before they hit production.

• You’ve designed time‑series data models in Click House, Timescale DB, or a comparable system, and can walk through the tradeoffs between write throughput, query performance, and schema evolution.

• You’ve instrumented production services with…