Robot Autonomy Engineer
San Francisco Bay Area, California USA·Posted 1mo ago
aillmroboticspython
<h1><strong>Role Description</strong></h1> <p>We are looking to recruit an exceptional Robot Autonomy Engineer<strong> </strong>to build the decision-making stack that turns a goal into coordinated, reliable robot behavior in real industrial applications — what the robot should do next, in what order, and how a fleet of them shares a workspace without getting in each other's way.</p> <p>In this role you will:</p> <ul> <li>Own the autonomy stack above the controller — task planning, behavior planning, path planning and trajectory planning — from the moment work arrives to the trajectories handed off to motion control.</li> <li>Design the behavior architectures that structure long-horizon manipulation and navigation tasks, and that degrade into retry, recovery and operator handoff rather than into a stall.</li> <li>Bring principled task planning to industrial workflows: goal and precedence reasoning, task allocation, and planning under uncertainty.</li> <li>Plan and coordinate motion for multiple robots sharing an industrial facility — separation, reservation, deconfliction and deadlock-free repositioning — so that adding a robot adds throughput.</li> <li>Integrate LLM and VLM reasoning into planning for task decomposition, subtask grounding and language-conditioned goals, together with the verification and fallbacks that make a model's output safe to execute on real hardware.</li> <li>Define the contract between learned policies and classical planning: what the model may decide, what the planner must guarantee, and how the two hand off mid-task.</li> <li>Interface with perception, intelligence, controls, simulation and platform software in designing functional architectures that hold up under real-world operation.</li> <li>Hold the whole stack to measurable field performance — cycle time, success rate, intervention rate — through simulation, replay of recorded robot logs, and testing on real robots.</li> </ul> <h1><strong>Qualifications</strong></h1> <p><em>Must-have:</em></p> <ul> <li>MS or PhD in robotics, engineering, mathematics, computer science or a related discipline.</li> <li>Real-world experience in classical motion planning for one or more robots — search-based, sampling-based or optimization-based (A*, RRT/PRM, trajectory optimization, model predictive control) — carried onto hardware rather than left in simulation.</li> <li>Real-world experience in behavior planning: finite state machines, behavior trees or comparable behavior architectures for long-horizon tasks, including failure detection and recovery.</li> <li>Familiarity with task planning in the classical AI planning sense (STRIPS, PDDL, HTN) or decision-theoretic planning (MDP, POMDP), and the judgment to know when that machinery earns its complexity against a simpler reactive design.</li> <li>Proficiency in Python and C++ programming, using up-to-date software development practices and tooling.</li> <li>Self-starter attitude with strong ability to identify problems, prioritize them, then plan and execute working solutions.</li> <li>Enthusiasm for working in a fast paced startup environment and eagerness to support the team on a variety of topics.</li> </ul> <p><em>Nice-to-have:</em></p> <ul> <li>Practical experience fine-tuning and integrating LLMs or VLMs for task planning, including grounding model output in executable, verifiable plans.</li> <li>Multi-robot coordination at fleet scale: task allocation and assignment, traffic management, deconfliction, multi-agent path finding.</li> <li>Experience with mobile manipulation — coordinating a mobile base and one or more arms toward a single task.</li> <li>Familiarity with ROS 2, and with fleet interface standards such as VDA5050.</li> <li>Familiarity with planning and kinematics libraries such as Drake, OMPL or MoveIt.</li> <li>Experience evaluating planners in simulation and against replayed field logs, and the regression testing that keeps a planner honest as it changes.</li> <li>A track record of carrying autonomy from working demo to sustained field operation.</li> <li>Familiarity with functional safety (FuSa) concepts.</li> </ul> <p> </p> <p> </p>