Robotics Software Lead

GRAM•Palo Alto, CA

About The Position

GRAM is building a standalone legged robot for critical infrastructure, initially focused on utilities. The Robotics Software Lead will architect the full onboard software stack and serve as the central node connecting system modules. The role owns message-passing architecture, middleware, and real-time performance so perception, controls, planning, and drivers communicate at the required speed without unexpected latency. The position does not directly own locomotion, perception, or controls. This is a hands-on role reporting to the Head of Engineering. It begins as an individual-contributor position, with a path to build a team as the company scales. GRAM is based in Los Angeles and is moving to the San Francisco Bay Area.

Requirements

  • 8+ years of experience.
  • Production experience with publish/subscribe middleware such as Zenoh or DDS.
  • Experience with real-time operating systems, including profiling, tracing, and latency analysis.
  • Strong understanding of concurrency and inter-process communication, including memory management.
  • Strong C++ skills and working knowledge of Python.
  • Designed the software architecture of a robot or similar real-time system and carried it through to production or field deployment.

Nice To Haves

  • Experience with legged, humanoid, or other mobile robots, ideally standalone and battery powered rather than fixed-arm robots.
  • Experience with EtherCAT or other fieldbus implementations.
  • Experience with GPU platforms such as NVIDIA Jetson and onboard AI inference runtimes.
  • A mechatronics-to-software background with real-time systems deployed in production.
  • Experience from autonomous vehicles, aerospace, or drones where real-time architecture is a core discipline.
  • Rust experience.

Responsibilities

  • Own the onboard software architecture, including how perception, estimation, planning, and control fit together and communicate.
  • Own real-time performance across the stack, set latency and jitter budgets for hardware-facing loops, and identify sources of lost cycle time.
  • Define and own the middleware layer and time synchronization across sensors and compute.
  • Partition workloads across CPU, GPU, and microcontrollers to isolate safety-critical loops from autonomy and AI.
  • Lead the upgrade of the current ROS stack to a supported release and define a modular architecture across software layers.
  • Build logging and replay tooling for debugging field runs.

Benefits

  • Early equity included in the package.
  • Opportunity to own a domain and build a team around it.
  • Freedom to build the architecture from scratch.
© 2026 Teal Labs, Inc
Privacy PolicyTerms of Service