Production Engineer, Network

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 Production Engineering Team Examples of key problems the team is working on

• Turn every network fault from a mystery into a closed ticket. Link diagnostics across router to router and NIC to router paths, remote command execution across the fleet, and repair visualization that shows what’s broken and why, because at 10 GW scale debugging has to be systematic, not artisanal.
• Build the network repair pipeline that runs itself. Automated fault detection through RMA initiation, ticket integration, transceiver lifecycle tracking, and return to service, across DC fabric, edge, and host to network layers, because a new site comes online every six months and manual repair doesn’t keep up.
• Build the network monitoring platform for a fleet that never stops growing. Alerting lifecycle and health dashboards for infrastructure spanning multiple hyperscale sites today and 10 GW by next year. It doesn’t exist yet. We’re building it.

Role Scope

• Carry the on-call pager for the network fleet and run repair end to end: diagnose the fault, execute the fix or drive the RMA, and return the link to service across DC fabric, edge, and host to network layers.
• Write Python and Go tooling that replaces manual diagnosis, including link tests, remote command execution across the fleet, and repair visualization that shows what’s broken and why, so faults resolve in minutes, not hours.
• Automate the repair pipeline from fault detection through RMA initiation, ticket integration, transceiver and optics tracking, and return to service, so a failure at any site follows the same path without manual handoffs.
• Maintain the realtime monitoring and alerting that gives every on-call engineer a true picture of network health across all sites, and keep it accurate as new sites and hardware roll in.
• Validate new sites and hardware into production by running the qualification tests that confirm a network is healthy before it carries traffic.

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 .

• You’ve carried a pager for a production network and can walk into an outage, find the fault, fix it or drive the RMA, and write the postmortem without someone walking you through it.
• You’ve written Python or Go scripts that replaced a manual, repetitive network task, from link diagnostics to config pushes to fleet-wide command execution.
• You understand how a transceiver fault, a misconfigured route, and a power event each show up differently in the data, and you can tell them apart from the signals alone.
• You’ve worked hands-on with link diagnostics, optics, and network monitoring protocols such as gNMI, gRPC, NETCONF, and SONiC, and you’re comfortable at the CLI on switches and routers across a fleet.
• You treat toil as a bug. If a repair step means SSHing into ten boxes by hand, you script it once and never do it by hand again.
• You reach real competence in an un…