Skip to main content

FluidStack

Controls Commissioning Engineer, Capacity Delivery

Austin, TX$150k–$204kfulltimemidAdded today

About this role

Fluidstack is seeking a Controls Commissioning Engineer to commission building management and energy management systems for large-scale AI data centers, validating control sequences, automating testing workflows, and ensuring operational readiness across 50+ GW of capacity deployment.

What you'll do

  • Commission BMS and EPMS controls through point-to-point validation and integrated systems testing
  • Verify operational sequences against design specifications and validate failure mode behavior
  • Perform alarm rationalization and graphics validation for operator trust and system reliability
  • Automate test execution, reporting, and commissioning workflows to improve efficiency across sites
  • Lead QA-QC efforts for first-of-a-kind modular data center designs
  • Develop and scale Level 4 and Level 5 commissioning processes

What they're looking for

  • Building controls commissioning (BMS/EPMS)
  • Point-to-point testing and sequence validation
  • Control sequence analysis and critical reading
  • Test automation and scripting
  • Niagara, Ignition, or equivalent BMS platforms
  • PLC programming
  • Integrated systems testing
  • Data center liquid cooling controls (bonus)
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

FluidStack

FluidStack builds AI infrastructure at scale, developing data centers and warehouse operations designed to handle gigawatt-capacity compute deployment. The company is hiring for warehouse engineers, data center operations specialists, product engineers, and people leaders to support rapid infrastructure expansion across multiple sites.

View all jobs at FluidStack

Likely interview questions

  • Walk us through your largest point-to-point commissioning project—how many points did you validate and what tracking methodology did you use?
  • Describe a time you found a gap or error in a control sequence that the programmer missed. How did you identify and resolve it?