Microgrid Architect Lead, Power Generation 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 run with no utility behind them, and the machine you design is the only thing holding frequency. 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. Role Scope Own the design basis. Fix voltage levels, topology, grounding, redundancy boundaries and the repeatable block and cluster unit for the islanded grid, with v1 and the site and block single-lines issued inside six months. Treat the block as a product. Hold one standard design across sites, drive out the variation that turns a repeatable build back into bespoke engineering, and freeze the design early enough that procurement and construction never absorb late change. Write the grid code and hold vendors to it. Set the internal grid code every generator, BESS, inverter and transformer must meet, own the conformance evidence that proves compliance before equipment ships, and own the technical content of equipment specifications and bid evaluation, with v0.1 in vendors' hands before the first major RFP. Build the model of record. Produce the first-pass generation, BESS and reserve sizing and the first load flow, short circuit and transient stability results yourself, own the study register and its prioritised roadmap, and accept or reject every vendor and EPC study against it. Set stability, protection and phasing. Define the loss-of-largest-unit contingency, reserve policy and a load shedding scheme with compute as a participa