Build the first system
Software Engineer, Fleet & Field Tools
Build dispatch, operator workflows, telemetry, fleet controls, and daily reporting around the physical operation.
Apply nowThe mandate
Build the software layer that dispatches machines, shows their state, guides interventions, records field performance, and connects robotics telemetry to the harvest operation. Own the operator experience from first start through daily closeout.
First-year outcomes
Evidence the role is working.
- 01
A field-lead interface for dispatch, status, exceptions, and safe intervention.
- 02
A durable telemetry and event model that explains every productive and unproductive minute.
- 03
Offline-capable workflows with controlled synchronization and no silent data loss.
- 04
Role-based access, fleet configuration, release visibility, and useful operational reports.
What you will own
- Build operator-facing web or mobile workflows for assignment, status, intervention, and closeout.
- Design APIs and typed event contracts across robots, edge services, and cloud systems.
- Implement telemetry ingestion, storage, replay, alerting, and operational analytics.
- Own identity, authorization, configuration history, and audit trails.
- Create deployment and observability tooling that supports staged, recoverable robot releases.
- Spend time with supervisors and technicians to remove steps that do not survive field use.
What we are looking for
- Has shipped software used to operate physical systems, fleets, or time-sensitive field work.
- Can design typed interfaces and reliable data flows across robot, edge, and cloud boundaries.
- Builds operator workflows around exceptions and recovery rather than ideal paths.
- Treats offline behavior, observability, auditability, and access control as product requirements.
- Can work across backend, frontend, infrastructure, and robot integration without losing system clarity.
The field reality
The environment is part of the design.
Connectivity will fail, operators will use phones in glare and dust, and the right action must be obvious during a live harvest. The software exists to keep machines productive and accountable, not to create another dashboard nobody watches.
- Fleet management, IoT, logistics, industrial software, or robot operations.
- Offline-first applications, event-driven systems, geospatial tools, or time-series data.
- Web, mobile, backend, cloud infrastructure, and edge deployment.
- Security and observability for remote physical systems.
Apply for this role
Upload your résumé.
We are actively hiring for Software Engineer, Fleet & Field Tools. A professional link is optional.