Robotics Software Engineer, Simulations

About The Role:

What You’ll Do:

• Build models of the devices that make up our machines (motion axes, sensors, grippers, and the machinery around them) that behave like the real thing behind the same software interfaces.
• Build scenario and regression suites that let machine software be developed and tested in CI, with no hardware in the loop.
• Extend simulation coverage across our machine types so more of the stack can be exercised without a physical machine.
• Build validation tooling that compares simulation behavior against real-machine telemetry, and root-cause divergences to a software bug or a model-fidelity gap.
• Grow toward owning a well-bounded piece of the platform, such as the device-model library or the simulation harness our CI runs on.

What You’ll Need:

• 2+ years building software for systems that interact with hardware or the physical world; industry, internships, robotics competitions, research, and serious open-source work all count.
• Strong programming fundamentals with working Python: you can build and debug real systems in Python, even if it isn't your first language.
• Simulation or modeling exposure: physics simulation, behavioral/discrete-event simulation, digital twins, or game-engine work; you have used a simulator seriously and know where it lied to you.
• A first-principles mindset: you reason about why a design works, not just how you've seen it done.
• Practical understanding of state machines, concurrency, and determinism.
• Systematic debugging habits and the collaboration skills to chase problems across the software/hardware boundary.
• BS in CS, CE, EE, ME, Mechatronics, Robotics, or equivalent experience.

Bonus Points For:

• Working C++: our motion stack and parts of the simulation core are C++ (expected at L4; a strong plus at L3).
• Physics-engine experience: MuJoCo, Drake, Bullet, PyBullet, or similar; rigid-body dynamics and contact modeling.
• Robotics depth: kinematics, dynamics, motion planning, or state estimation.
• Experience with robotics middleware, ROS or otherwise (we build our own).
• gRPC/Protobuf APIs, observability tooling, or CI/test infrastructure at scale.
• Hardware-in-the-loop testing or sim-based validation of real machines.