Plant Controls Lead (EMS/PPC) at Fluidstack in Austin, TX

Job description

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 Be a barrel. Full autonomy. Own things end to end, take on scope without being asked, no permission required to operate outside your core role. Insane urgency. We drive everything forward as fast as possible. Reason from 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. Build something that actually matters. If you're going to spend your time, spend it on something that matters to the world. The Power Generation Team The Power Generation team designs and builds the power that runs Fluidstack's AI infrastructure, including grids that stand alone with no utility behind them. Examples of key problems the team is working on Build an islanded grid at gigawatt scale, from a blank sheet. Generation, storage and compute running with no utility behind them, where the machine you design is the only thing holding voltage. No playbook exists at this size, so the architecture you set becomes the reference. Get power online in months, not years. Interconnection queues are measured in years and we do not have them. Generating our own power is how a site goes from signed lease to live compute inside six months, and the power system is the long pole in that plan. Make one power block, then build it a thousand times. A repeatable block and cluster unit, validated once and stamped across the fleet, is the only route to the scale we are targeting. Every bespoke site is schedule we do not get back. Design a grid whose largest load answers back. Compute is not passive demand here. Load behaviour, curtailment and shedding are design variables you negotiate and specify, a lever almost no power system engineer has ever been handed. Role Scope Own the control stack. Own the control stack for fully off-grid campuses: the site energy management system, the plant controller for each power block and the dispatch logic across PV, BESS and gas, as one standard architecture that scales from a single block to a gigawatt-scale campus energized in six months. Write sequences our own code runs. Turn the control philosophy into sequences of operation covering every operating mode, source transition, blackstart path, emergency shed and degraded state, and prove each one in simulation and on a hardware-in-the-loop bench before the plant is energized. Build the plant model library and bench so any controller, vendor or our own, is tested against our plant before it ships to site. Hold the generation side of the control contract. Extend the contract between the power plant and the data center from one plant and one facility to many blocks feeding many buildings, with load reduction deadlines measured in seconds that both sides are measured against in production. Decide what we buy and what we build. Choose which components we bring in to energize the first campuses faster and which we build first, replace each b