You build the brains that let a machine sense, decide, and move on its own — the perception, planning, and control behind a self-driving car, a drone, or a robot. Teaching machines to act without a human at the wheel.
The day often blends coding, simulation, and test — writing perception or planning algorithms, running them against mountains of logged data, then watching them fail in fresh ways on real hardware. You work on a tight interdisciplinary team, and a clean demo and a robust system are worlds apart. Much of the real work is chasing the rare edge case that breaks everything.
Context changes the work sharply. In a research group you may push novel methods with loose timelines; in a product team, you're hardening something for the road under real deadlines and real liability. The field moves fast, tools churn, and safety cases can dwarf the actual algorithm work. For some, the wearing part can be how much of autonomy is still unsolved, no matter the hype.
Strong autonomy engineers tend to be rigorous, comfortable with ambiguity, and oddly motivated by failure — because that's where the learning is. If you need tidy, solved problems and quick wins, the open-endedness can grind. But if making a machine reliably handle the real world pulls at you, few fields are as engaging right now.
Where this role sits in the broader career landscape — and where it can take you.
Roles like this one sit within a broader occupational category. The numbers below reflect that full landscape — helpful for context, but your specific experience will depend on level, specialty, and where you work.
Roles with similar work and overlapping career paths
View all Engineering roles →Truest gives you tools to understand your strengths, explore roles that fit, and plan your next move.
Explore Truest career tools