FluidStack
Mechanical Engineer, Robotics
Austin, TX$203k–$232kfulltimemidAdded today
About this role
Design and develop mechanical systems for data center robotics, focusing on end effectors, docking mechanisms, and robot-to-equipment interfaces. Move rapidly from concept to production-ready hardware while collaborating closely with controls and software teams.
What you'll do
- Engineer mechanical components for robotics systems including end effectors, docking systems, and plant interfaces
- Design physical integration solutions for robots to handle, mate with, and service data center equipment
- Build and test prototypes rapidly, from concept to instrumented trials within weeks
- Conduct reliability testing and failure analysis on mechanical designs
- Execute design for manufacturability (DFM) and production planning for unattended hardware
- Collaborate with controls and software teams in iterative development cycles
What they're looking for
- Mechanical design and CAD for robotics/automation systems
- End effector and gripper design
- Geometric Dimensioning & Tolerancing (GD&T)
- Prototype development and rapid iteration
- Reliability testing and failure analysis
- Design for manufacturability (DFM)
- Integration with software and controls systems
- Server and data center hardware knowledge
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 a robotics or automation project where you took a mechanical design from prototype through reliability testing—what challenges did you encounter?
- Describe your approach to designing interfaces and tolerances that work reliably in real-world conditions. Can you share a specific example of a design that failed and how you addressed it?