Product Engineer, Infrastructure Development & Delivery

Fluidstack•San Francsisco, CA

11d•$224,000 - $300,000

About The Position

Fluidstack is building civilization-scale infrastructure for AI, aiming to deliver 10 to 100s of GWs of compute faster than anyone else by rethinking every layer of the stack. This involves acquiring power, designing and building data centers, and operating them, with teams spanning hardware and software. The company emphasizes speed and scale as key differentiators. They are looking for individuals who care deeply about this problem space and are driven by a mission to make humanity more free through AI. Fluidstack operates with a philosophy of full autonomy, insane urgency, reasoning from first principles, and a passion for tackling the frontier of AI. They encourage employees to take on scope without being asked and to challenge assumptions. The company values building something that truly matters to the world and fosters an environment of high intensity and long hours to push the frontier forward.

Requirements

Shipped production code in Go, Python, or TypeScript, and can pick up whatever language the problem demands.
Built real features on LLM APIs (OpenAI, Anthropic, or open-weight models), MCP servers, and agentic frameworks.
Work daily with AI coding tools like Claude Code and Cursor, and get agents doing useful work autonomously alongside you.
Identify problems, design the solution, and ship it without waiting for direction or approval.
Moved fast under deadline while leaving foundations that other engineers extended after you moved on.
Earned credibility with people who build physical things: construction leads, field engineers, schedulers, or commissioning agents, and driven adoption of your software inside their real deadlines.
Product taste shows in what you've shipped: interfaces field crews call obvious, and workflows that match how the work actually happens.

Nice To Haves

Construction tech or project controls (P6, schedule engines, critical path).
BIM, IFC, or Revit data models.
Commissioning, BMS/EPMS, or controls protocols.
Document control and submittal workflows.
Graph data models.
Computer vision on site imagery.

Responsibilities

Build the schedule that runs the portfolio: one template schedule per building type, instantiated per project, with every activity tied to the materials it consumes, so need-by dates for switchgear, transformers, and cooling fall out of the critical path instead of a spreadsheet, and a slip in permitting reprices the procurement calendar the same hour.
Turn the site into structured data: work packages, contractor field entries, rack placements, cable runs, and QA inspections land as records tied to the design revision they were built against, percent complete is computed from evidence rather than reported on a call, and the customer sees delivered against committed without anyone assembling a deck.
Ship change orders as a workflow, not an email chain: scope, cost, and schedule impact drafted from the design delta, routed through legal, finance, and the general contractor with the approval trail attached, and the bill of materials and schedule updated the moment the order is signed.
Make the design the source of truth: ingest building information models straight into the bill of materials with a reviewable diff on every revision, generate submittal requirements per spec section, and keep sites, buildings, and data halls as one canonical record that every downstream system reads instead of copies.
Ship commissioning as software: test procedures generated per asset from the design revision across all five levels, results landing as evidence against the asset they tested, energization gates that check themselves, and handover that opens on proof instead of a signature.