FluidStack
Controls Commissioning Engineer, R&D
About this role
Fluidstack seeks a Controls Commissioning Engineer to validate and optimize building management, energy, and automation systems for next-generation AI data center infrastructure. You'll execute comprehensive testing protocols, diagnose system behavior against design specifications, and drive improvements across commissioning scripts and factory processes.
What you'll do
- Commission BMS, EPMS, and automation sequences on first-unit deployments, verifying alignment with design intent
- Execute point-to-point, functional, and integrated test scripts; document and disposition results
- Analyze system trends and sequence behavior; reconcile actual performance against specifications and resolve discrepancies
- Support factory controls FAT (Factory Acceptance Testing) processes for modules before shipment
- Debug control logic and PLC/BMS code to identify and escalate root causes
- Document findings to enable engineering improvements to standards, not just individual sites
What they're looking for
- Data center or industrial plant controls commissioning experience
- BMS and PLC logic programming or troubleshooting
- Point-to-point and functional testing verification
- EPMS (Energy Management) system testing
- Tridium, ALC, or PLC platforms
- Technical documentation and root-cause analysis
- Integrated systems testing and analytics-driven commissioning
- Sequence validation and error detection
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.
- Website
- fluidstack.io
Likely interview questions
- Walk us through your experience commissioning control systems—what was your role in verifying BMS or PLC logic against design specifications?
- Describe a time you caught a sequence or logic error that point-to-point checks initially missed. How did you identify and document it?