Controls Engineer, Robotics

We believe robots will be the next chapter in making physical labor safer and more affordable. But, nearly nine out of ten American factories and warehouses don’t have a single robot. Tutor Intelligence is changing that.

We build robots that go straight into real factories and warehouses, to do real work, with real impact. Our robot Cassie does back-breaking work, moving boxes, pallets, and bulk goods for family-owned manufacturers to some of the largest brands in the world. Our robot Sonny does handwork, using two arms to achieve human‑like dexterity in picking and packing. Every robot learns on the job, and each one we deploy makes the next one more capable, more affordable, and faster to put to work.

Founded at MIT and headquartered in Watertown, MA, we do it all in‑house: the robotics hardware, the machine learning, and the field deployment and service. We’re a team of researchers, engineers, technicians, operators, and sellers who love building things and solving hard problems.

Our mission is grand: robots everywhere, for the common good, raising the standard of living across North America, and then the world.

Our robots work in customer facilities with people nearby. The code that decides how an arm moves, how fast, and how it stops is what keeps those people safe. We're looking for a controls engineer to own it.

The work is controls: joint limits, speed limits, stopping distances and stopping times, contact and collision behavior, the loop that turns a motion command into torque, and the monitoring that detects when that loop misbehaves. It is also software work. The code lives in a large codebase that changes every week, and the safety‑critical parts of it have to be written, organized, tested, and reviewed so they stay correct through those changes.

The person we want has worked in a codebase where a mistake had physical consequences, has written and organized a lot of code there, and is comfortable with the physics underneath it.

You will build the hardware‑in‑the‑loop test bench that runs the control code against real arms and real stop circuits, in continuous integration. You will also keep the evidence current: the measurements and tests that show the arm stops when it should, updated as the code, the arms, and the applications change.

The formal side of safety, risk assessments and the standards customers ask about, is part of the role. We will teach it.

• Own the safety‑critical control code for our arms: Limits, stop behavior, collision response, and the monitoring around the control loop
• Work on the control loop itself: Timing, stability, and failure modes, from the motion command down to the drives
• Organize the code so it can be trusted: Keep the safety‑critical parts small, separated, tested, and reviewable, and set the rules for how other code touches them
• Build hardware‑in‑the‑loop testing: A bench and a continuous‑integration path that run the control code against real arms and real safety hardware
• Keep the evidence current: Stopping‑time measurements and the tests behind the safety argument, updated whenever the code or the hardware changes
• Document the design: Decisions, limits, and the reasons for them, in a form other engineers follow

• Real‑time control experience on physical systems: Robot arms, vehicles, aircraft, or similar. You have written control code that moved hardware and handled its failures
• Experience in a mission‑critical codebase: You have written and organized a large amount of code where mistakes had physical consequences, and you know what that requires of structure, testing, and review
• Comfortable with the physics: Dynamics, torque, inertia, stopping distances, contact. You can reason about what the…