> Markdown version of [/jobs/ext/482002-sr-robotics-software-engineer](https://www.wearedevelopers.com/jobs/ext/482002-sr-robotics-software-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Sr. Robotics Software Engineer - **Company:** Aurelius Systems - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Salary:** $185,000.0 - $235,000.0 - **Contract:** Permanent contract - **Skills:** Automation of Tests, Code Coverage, Code Review, Continuous Integration, Software Debugging, Hardware-In-The-Loop Simulation, Systems Development Life Cycle, Sensor Fusion, Software Engineering, Software Testing Automation Framework, Robot Operating System, Real Time Systems, Production Code - **Published:** June 8, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=3aedfed04cf60864 ## About the Role Do you have experience in System development?, Do you have a Bachelor's degree?, * 5+ years of robotics software engineering with real shipped systems behind you * Strong hands-on development chops. You're a builder first, and you write production code that runs on real hardware * ROS2 experience and the judgment to know when not to use it * Experience building or operating CI/CD for robotics or hardware-in-the-loop systems * A genuine ownership mentality toward quality. You've seen what bad test discipline costs in the field and you fix it without being asked Where you probably come from: Senior IC at robotics companies that shipped to customers or operators, defense robotics groups, autonomy at automotive, or aerospace robotics programs that put software in front of real users. We want to talk if: You're the engineer who writes the feature and the test for it, and quietly fixes the CI pipeline everyone else complains about. You've taken software from "works on my machine" to "works in the field." Not a fit if: You're a QA specialist who doesn't write production code, you're a researcher who hasn't shipped, or you think test discipline is someone else's job. Nice to Haves: * Real-time systems experience * Sensor fusion or perception background * Defense or safety-critical software release experience * Built test automation frameworks for robotics or hardware-in-the-loop systems before Education: BS, MS, or PhD in CS, Robotics, EE, or equivalent. Track record matters more than degree. How You Operate: * Extreme bias for action. You ship working code on real hardware, not slideware * You debug from first principles, not intuition alone * Comfortable with ambiguity and fast iteration in a startup environment * Clear communicator across software, hardware, and operator-facing surfaces Self directed. * You identify what needs to happen next and do it without being told ## Description * Hands-on development across the robotics software stack from perception, control, and autonomy * Championing QA practices and test coverage alongside Erick and the Principal, embedding quality into how the team works rather than bolting it on * CI/CD infrastructure and deployment hygiene for robotics and hardware-in-the-loop * Writing and maintaining the automated tests and tooling that catch failures before the range does * Code review and raising the quality bar across the robotics SWE team * Cross-functional work across perception, controls, embedded, and EE, * Build more in 1 month than most people build in 1 year. We field test weekly. Your work makes the whole team faster. * Career velocity is real. At ~10 engineers, there are no layers between you and impact. * Work on a problem that actually matters. Small cheap drones are changing warfare. Our laser systems are the asymmetric answer - infinite magazine, near zero cost per shot, scalable to every base, border, facility, and truck. * Join the densest defense startup ecosystem in the country. California is where the next generation of defense companies are being built. How We Work: Core hours are Monday through Friday, 9 to 6. When we're sprinting toward a demo or field test, the team ramps up - nights, weekends, whatever it takes to ship. When the sprint lands, we ramp down. We don't manufacture intensity for show. ## Related Videos - [Robots 2.0: When artificial intelligence meets steel](https://www.wearedevelopers.com/videos/1452-robots-2-0-when-artificial-intelligence-meets-steel) - [Mutation Testing and Fuzzing in C#](https://www.wearedevelopers.com/videos/703-mutation-testing-and-fuzzing-in-c) - [Are Code Reviews Worth It? Insights from 16 Years of Review Data](https://www.wearedevelopers.com/videos/1135-are-code-reviews-worth-it-insights-from-16-years-of-review-data) - [Robots are coming into the wild! Full-Stack Robotics Engineers, be ready!](https://www.wearedevelopers.com/videos/479-robots-are-coming-into-the-wild-full-stack-robotics-engineers-be-ready) - [Code to Road in < 12 hours](https://www.wearedevelopers.com/videos/1082-code-to-road-in-12-hours) - [Data: The Deciding Factor in AI Success](https://www.wearedevelopers.com/videos/100310-data-the-deciding-factor-in-ai-success) ## Related Articles - [How software is steering vehicle technology](https://www.wearedevelopers.com/magazine/515-how-software-is-steering-vehicle-technology) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Never delegate the understanding](https://www.wearedevelopers.com/magazine/749-never-delegate-the-understanding) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)