Skip to main content

Medra

Robotics Software Engineer

San FranciscofulltimemidAdded today

About this role

Join a Physical AI startup building autonomous robotic systems for scientific research. You'll develop motion planning, computer vision, and control algorithms to enable robot arms to manipulate laboratory equipment with human-level precision, working both in simulation and on physical hardware.

What you'll do

  • Design and implement motion planning and trajectory optimization algorithms for robotic arm manipulation
  • Develop computer vision solutions to detect and interact with lab consumables and equipment
  • Integrate, test, and debug robotics software across simulation environments and physical systems
  • Collaborate with customer scientists to understand requirements and guide solution deployment
  • Own kinematics, dynamics, and control implementations for robotic systems
  • Identify optimization opportunities and architect solutions for scalability and robustness

What they're looking for

  • Motion planning and trajectory optimization
  • Robot arm kinematics and dynamics
  • Python development
  • Computer vision
  • Control systems
  • Robotics simulation (PyBullet, MuJoCo)
  • Software engineering best practices
  • System integration and debugging

Benefits

  • 401k retirement plan
  • Medical, dental, and vision insurance
  • Relocation assistance
  • Unlimited PTO
  • Weekday team dinners
  • 100% in-person collaborative environment in San Francisco
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Medra

Medra develops a Physical AI Scientist platform that uses robotic automation to innovate life science research and laboratory workflows. The company is hiring Mechanical Engineers to design and test hardware for robotic systems that enhance laboratory protocols.

View all jobs at Medra

Likely interview questions

  • Describe your experience developing motion planning algorithms—what challenges did you face and how did you solve them?
  • Tell us about a time you integrated complex robotics software with physical hardware; what debugging strategies did you use?