Controls Engineer, Design Development

About this role

Fluidstack is seeking a Controls Engineer to design standardized control systems for modular data center builds at scale. You'll create reusable templates, sequences of operations, and specifications that eliminate repetitive engineering and ensure consistency across 50GW+ of infrastructure deployments.

What you'll do

• Develop template controls designs and standardized points lists for modular data center builds to enable rapid, repeatable deployment
• Write sequences of operations for mechanical and electrical systems that serve as the source of truth for programming teams
• Author and maintain Division 25 integrated automation specifications across multiple sites as equipment and designs evolve
• Coordinate controls design across mechanical, electrical, and commissioning teams to ensure alignment and prevent field conflicts
• Build standard bills of materials and instrumentation specifications that lock IO and controls hardware for each modular build
• Catch coordination gaps between disciplines before they reach the field and become costly change orders

What they're looking for

• Controls design packages and drawings (BACnet, Modbus, SCADA/BMS platforms)
• Sequences of operations for mechanical and electrical systems
• Division 25 specification writing and CSI MasterFormat
• Points lists and bills of materials development
• Data center systems (chillers, CRAH/CRAC, fan walls, switchgear)
• Cross-functional coordination and commissioning knowledge
• Modular or productized build delivery experience
• IO scheduling and controls tooling

Benefits

• Competitive salary: $200,000–$250,000 per year
• Equity compensation in the form of stock options
• Work on civilization-scale AI infrastructure
• Extreme ownership and full autonomy over projects
• Fast-paced, high-impact environment at the frontier of AI compute
• Collaborative culture with first-principles problem-solving

Likely interview questions

• Walk us through a controls design package you created that a contractor or programmer built from without major revisions—what made it clear and complete?
• Describe your experience writing sequences of operations and how you've ensured they translate correctly when handed to programming or control system teams.