Senior Robotics Software Engineer

• 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, and better decisions in the field are the day-to-day focus
• 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:

• We’re scaling toward thousands of units operating in the field. That means treating robots more like servers through telemetry, observability, OTA updates, fleet-wide health, remote diagnostics, mission orchestration, and the infrastructure that allows a small team to operate a large fleet reliably
• If you’ve done backend or distributed systems work and want to bring that discipline to robotics, this is where it comes into play

The Perception Problem:

• LiDAR is great until it isn’t. It can’t tell you a dark patch is standing water, that a shirt on the ground is soft, or that the object twenty feet ahead is a person, a deer, or a fence post. Those distinctions matter when deciding whether to stop, slow, reroute, or proceed
• Camera-based vision that complements LiDAR in unstructured outdoor environments is one of the highest-impact problems we’re solving. If computer vision is your passion, there’s a place for you here

We’d be thrilled to hire someone who is strong in one area and curious about the other. We don’t expect both at world-class depth, but we do expect deep ROS2 experience. That’s the constant.

WHAT YOU’D ACTUALLY DO:

• Develop and ship ROS2 features that enhance machine behavior and unlock new capabilities
• Build out the fleet management layer, including telemetry, OTA updates, remote operations, and fleet-wide observability
• Work on perception, sensor fusion, and decision-making in unstructured outdoor environments
• Collaborate directly with mechanical, electrical, and controls engineers, as well as technicians who validate and field-test what you build
• Make architectural decisions that impact the platform two to three years into the future
• Help shape how the software team hires, reviews, and scales as the company grows, * Production computer vision in unstructured environments
• OTA update systems, fleet telemetry pipelines, and remote operations tooling
• Embedded Linux, real-time systems, or low-level controls experience
• GPS-denied or GPS-degraded localization
• Experience deploying systems at meaningful scale (hundreds or more units)

ABOUT THE TEAM: The engineering team is ten people. No one is coasting.

There aren’t layers of process between you and the machine. Code reviews matter. Design discussions are technical and direct. Decisions are made by the people closest to the work, and the company is led by an engineer who knows the difference between cheap and right. Trade-offs are made deliberately, not by default.

You’ll have unusual ownership for a company this size and peers who will challenge your ideas when necessary.

The team is based near Green Bay, Wisconsin. The cost of living is significantly lower than coastal tech hubs, the commute is short, and the work is on real robots operating in real-world environments, not a campus parking lot.

WHAT THIS IS NOT:

• A research position
• A role where you’ll spend a year building a prototype that never ships
• A position where someone else writes the specification and you simply implement it
• A team where “senior” means “has been here the longest”

Robotics Software, Software Engineering, GPS (Global Positioning System), Vehicle Fleets, Diagnostics Solutions/Software, Telemetry, Distributed Computing, Robotics, Light Detection and Ranging (LiDAR)\Laser Detection and Ranging (LADAR), Software Patches, * Strong production ROS2 experience. Not a class or side project. You’ve shipped and maintained ROS2 software that users depend on

• Solid C++ and/or Python skills with the ability to work comfortably in both

• Experience with at least one of the following: Fleet management or distributed systems at scale

  Computer vision and sensor fusion in real-world environments

• A strong sense of when to build, when to integrate, and when to start over
• The judgment to operate as a senior individual contributor. You can scope your own work, challenge requirements when necessary, and deliver without constant oversight
• Clear technical writing, including design documents, postmortems, and code review feedback

Tell us:

• 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?

Code, design documents, postmortems, talks, papers, demos, or anything else that shows how you think.