Robotics Software Engineer — Autonomy & Fleet (Field Deployments)

TAR; San Francisco (CA); On-site; USD 140,000 - 210,000; Full time

Benefits offered by this job

Up to $15K relocation bonus

Unlimited PTO

Health, Dental, Vision insurance

$1K monthly meals stipend

Job summary

TAR in San Francisco is seeking a mid to senior Software Engineer for robotics. You will own software across the autonomy stack, from perception to controls, and coordinate a fleet of machines on active construction sites.

Work runs on real hardware outdoors, with travel to deployment sites as needed. This role demands ownership, rapid iteration, and the ability to ship reliable software in challenging environments.

Qualifications

• Professional experience building software for robotic or autonomous systems.
• Track record shipping production robotics software on real deployed hardware.
• Expertise across the autonomy stack from prototypes to production in a systems language (C, C++, or Rust).
• Experience building for real-time and resource-constrained environments.
• Ability to take a system from architecture through field deployment independently.
• High ownership, bias for speed, comfort with ambiguity.

Responsibilities

• Write software across the autonomy stack for prototype and production robots (perception, state estimation, localization, motion planning, controls).
• Implement task and motion planning achieving centimeter precision at construction pace.
• Build the fleet layer for task allocation and deconfliction across multiple machines on an active site.
• Stand up simulation and CI; build logging, telemetry, and data pipelines for debugging.

Skills

Robotics software

Production robotics software

Autonomy stack

Real-time systems

Architecture to deployment

Ownership & speed

Job description

TAR in San Francisco is seeking a mid to senior Software Engineer for robotics. You will own software across the autonomy stack, from perception to controls, and coordinate a fleet of machines on active construction sites.

Work runs on real hardware outdoors, with travel to deployment sites as needed. This role demands ownership, rapid iteration, and the ability to ship reliable software in challenging environments.