Senior Robotics Software Engineer

We build full-size commercial autonomous robots that mow large properties without an operator in the seat. They run in real terrain — wet grass, dust, heat, GPS dropouts, unstructured environments — for municipalities, DOTs, and commercial contractors across North America.

Our machines ship today, and they work. What this category becomes over the next decade is still being written — we plan to write most of it.

• Develop and ship ROS2 features that enhance machine behavior and unlock new capabilities
• Build out our fleet management layer — telemetry, OTA, remote ops, fleet-wide observability
• Work on perception, sensor fusion, and decision-making in unstructured outdoor environments
• Collaborate directly with mechanical, electrical, and controls engineers — and with the technicians who validate and field-test what you build
• Make architectural calls that affect what the platform can do two and three years out
• Help shape how we hire, review, and scale the software team as we grow

• Strong production ROS2 experience — not a class, not a side project; you ve shipped and maintained ROS2 software that users depend on
• Solid C++ and/or Python; comfort moving between them
• Experience with at least one of: fleet management/distributed systems at scale, or computer vision and sensor fusion in real-world conditions
• A sense of when to build, when to integrate, and when to throw something out
• The judgment to operate as a senior IC: you scope your own work, push back when the spec is wrong, and ship without needing to be managed
• Clear technical writing — design docs, postmortems, code review comments that move the team forward

The core of this job is developing in ROS2: building, extending, and shipping the software that makes our machines do what they do. New behaviors, new capabilities, better decisions in the field.

Within that, two areas have outsized leverage on where the platform goes — and you'd help us decide where to push hardest:

• The fleet problem…
• The perception problem…

The engineering team is ten people. No one is coasting. We don t have process layers between you and the machine. Code review matters here. Design discussions are technical and direct. Decisions get made by the people closest to the work — and the company is led by an engineer who knows the difference between cheap and right.

A research position. A role where you ll spend a year on a prototype that doesn t ship. A place where someone else writes the spec and you implement it. A team where senior means "has been here longest."

A resume helps, but tell us about something you ve built or shipped. The harder, messier, and closer to production, the better.

We want to know:
What was the problem? What did you build? What broke, and how did you find it? What would you do differently? What did you learn that changed how you work?