FluidStack
QA Engineer, Capacity Delivery
About this role
Fluidstack seeks a QA Engineer to own quality assurance for its data center capacity delivery program, ensuring design and construction standards are met before field deployment. You'll establish QA processes, audit vendor and field work against specifications, and drive continuous improvement by feeding quality lessons back into the design cycle.
What you'll do
- Own QA strategy for capacity delivery engineering, catching defects at design phase rather than in the field
- Develop and implement QA program including checklists, hold points, and acceptance criteria for productized builds
- Audit vendor performance and field construction quality against specifications and standards
- Investigate nonconformances and drive them to root cause closure rather than symptomatic fixes
- Create and enforce inspection and test plans that field teams follow
- Incorporate quality lessons learned into future designs to prevent repetition of mistakes
What they're looking for
- QA/QC program management for large infrastructure or construction projects
- Inspection and test planning with practical field implementation
- Nonconformance report (NCR) management and root cause analysis
- Data center or mission-critical facility experience (bonus)
- ISO 9001 or similar quality system experience (bonus)
- Owner-side quality assurance perspective
- Commissioning and acceptance criteria definition
- Vendor quality auditing and management
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
- Tell us about a time you caught an expensive design error before it reached the field—what was the impact and how did you prevent similar issues?
- How do you balance maintaining quality standards without becoming a schedule bottleneck or blocker?