Lead Autonomy Engineer

TAR•San Francisco, CA

2d•Hybrid

About The Position

TAR builds its own construction robots to install a proprietary solar racking system at the scale and pace gigawatt campuses demand. The autonomy software that drives them has to hold up in the dust, heat, and vibration of a live construction site in West Texas. As Lead Autonomy Engineer, you own a core piece of the autonomy stack: perception, planning, or controls; from early development through field deployment, and act as the technical lead for a small group of autonomy engineers. You report into the VP of Autonomy and split time between the San Francisco robotics facility and regular field trips to West Texas.

Requirements

5-7 years of software engineering experience, including some experience leading a small team or serving as a technical lead on a project.
Hands-on experience owning software or autonomy for a robotics system through to production or field deployment
Comfortable writing realtime, safety critical software with limited compute
Solid expertise in one or more of perception, navigation, planning, or controls for autonomous systems.
Comfortable reviewing others' technical work and communicating design trade-offs to a manager or cross-functional partners.

Nice To Haves

Experience with autonomy for energy, industrial, or infrastructure robotics rather than consumer robotics.
Experience partnering closely with hardware teams on tightly coupled hardware/software/autonomy systems.
Background at a high-growth, venture-backed robotics or hardware startup.

Responsibilities

Own the technical design and delivery plan for a defined area of the autonomy stack (e.g., perception, planning, or controls), turning org-level roadmap priorities into concrete engineering work.
Lead day-to-day technical direction for a small group of autonomy engineers, reviewing designs and code and mentoring less experienced engineers.
Drive your area of the stack from early development through field deployment, validating against real operating conditions.
Make architecture and design decisions within your area that hold up under field conditions, working closely with hardware engineers so autonomy is co-developed with the robots it runs on.
Own the development lifecycle for your area: roadmap input, prioritization, release, monitoring, and iteration.
Spend time at the West Texas site (1-3 weeks per year) closing the loop between field performance and software fixes.
Partner with the VP of Autonomy, contributing to hiring and roadmap decisions.