Neuralink
Mechanical Engineer, Surgery & Robotics
About this role
Neuralink is seeking a Mechanical Engineer to join their Surgery & Robotics team in Austin or South San Francisco. The role involves designing advanced mechanical assemblies for surgical robots that automate implantation processes, aimed at transforming healthcare solutions.
What you'll do
- Design and develop mechanical assemblies and actuators for surgical robots
- Build rapid prototypes to meet project goals
- Apply analytical methods for actuator and structure optimization
- Conduct FMEAs and user testing to ensure product safety
- Collaborate with QA and Test teams for validation processes
What they're looking for
- 3+ years of mechanical engineering experience
- Strong understanding of engineering principles
- Bachelor’s degree in engineering or science
- Experience with multi-DoF actuated devices
- Familiarity with sensing devices
- Proficiency in rapid prototyping technologies
- Experience in product lifecycle management
Benefits
- Opportunity to make a significant impact in healthcare
- Strong growth potential for high-impact team members
- Comprehensive medical, dental, and vision insurance
- Paid holidays
- Commuter benefits
- Provided meals
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Neuralink
Neuralink develops brain-computer interface technology and neurosurgical robots to enable direct interaction between the brain and computing systems. The company is hiring engineers across clinical implementation, user interface design, manufacturing, and software development to support its pioneering medical devices and surgical systems.
- Website
- neuralink.com
Likely interview questions
- Walk us through a complex mechanical assembly you designed from concept to production. What were the key challenges around precision, manufacturability, or scaling?
- Tell us about your experience designing space-constrained, multi-degree-of-freedom actuated systems. How did you handle competing design constraints?