Skip to main content

FluidStack

Manufacturing Engineer — Line Design & Takt

Austin, TX$203k–$232kfulltimemidAdded today

About this role

Fluidstack seeks a Manufacturing Engineer to design and optimize production lines for AI infrastructure modules, focusing on layout optimization, takt time modeling, and capacity planning. You'll own line design from concept through ramp, ensuring bottleneck-free operations and operator-centric workflows.

What you'll do

  • Design production line layouts, station counts, and takt timing for module fabrication and assembly
  • Build capacity models that accurately predict bottlenecks, buffers, and output curves under real-world variation
  • Develop ramp plans that scale lines from first unit to full rate while identifying constraints
  • Adapt and redesign lines as product configurations evolve without major factory rebuilds
  • Use simulation and quantitative methods to identify and eliminate bottlenecks proactively
  • Optimize for operator ergonomics, task presentation, and workflow efficiency

What they're looking for

  • Manufacturing line design and layout optimization
  • Takt time and capacity modeling
  • Discrete event simulation
  • Lean manufacturing and Toyota Production System principles
  • Bottleneck analysis and constraint theory
  • Data-driven decision making
  • Ergonomics and human factors engineering
  • Production ramp planning
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.

Website
fluidstack.io
View all jobs at FluidStack

Likely interview questions

  • Walk us through a manufacturing line you designed—what was the biggest bottleneck you discovered, and how did you solve it?
  • Describe a time your takt model didn't match reality. What went wrong, and how did you validate your next model?
Unlock all 7 questions free — and practice them live →