> Markdown version of [/jobs/ext/4786780-full-stack-robotics-software-engineer](https://www.wearedevelopers.com/jobs/ext/4786780-full-stack-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). --- # Full Stack Robotics Software Engineer - **Company:** Octavian, Inc. - **Location:** Los Angeles, CA, United States - **Salary:** $170,000 - $190,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Computer Vision, Databases, Computer Engineering, Software Debugging, Linux, JSON, Python (Programming Language), OAuth, Robotic Automation Software, Software Engineering, Software Systems, Web Standards, Robot Operating System, Git, Information Technology, Restful APIs - **Published:** November 19, 2026 - **Apply:** https://www.careerbuilder.com/job-details/full-stack-robotics-software-engineer-los-angeles-ca--586771cf-e665-4110-8ff6-682cf28eeb93 ## About the Role Robotics Software, Software Engineering, Sterilization, Robotics Software, Communication Skills, Software Engineering, Robotics, Software Development, Electrical Engineering, Mechanical Engineering, This company is a spin-out from Sorting Robotics and we are inheriting a decade of robotics infrastructure and know-how. The role is for the first robotics software engineer at the company. You'll be working directly with the founders and learning from the previous team on how to build a robotics company. You'll need to be scrappy, a jack of all trades and a master of one, be able to communicate your ideas quickly and effectively, adapt to changing dynamics, have experience with robotics, and be able to push through the journey of building a new company., * Familiarity with Python * Familiarity with Git * Familiarity with CI/CD pipelines, AWS services * Familiarity with web standards, RESTful APIs, OAuth * Experience training VLA or inference models for motor control You will work on different parts of the stack at various times. We expect you to understand where everything goes and why, and we expect you to add to the stack to make the development process more robust. Requirements * Must be AI-Native in all workflows * Degree in Computer Science, Computer Engineering, or related fields. * Experience with Linux (systemd, journalctl, network manager, permissions). * Hands-on experience in robotics or computer vision * Experience working with Hardware. * Strong analytical and problem-solving skills. * Strong communication and collaboration skills. * Authorized to work in the US without visa sponsorship. ## Description This role is not for the faint of heart. You should expect to work 60+ hours a week, expect for there to be more problems than solutions, expect for you to have very little hand-holding, invent technology that didn't exist 6 months ago, expect to feel the pressure of performance when everyone in the room is depending on you and there are millions of dollars on the line. All this will be true, but you will also be in a room of people that respect you; where everyone is rowing together to achieve the noble goal of saving lives with our robotic systems., * Design, develop, and implement software to control machines developed by Octavian Robotics. * Build and implement the initial infrastructure of the company. * Work closely with mechanical and electrical engineers and guide design decisions based on what software can effectively accomplish. * Work closely with customer success and sales staff to translate customer and company needs into software solutions. * Train entry/mid-level software developers in the development lifecycle of the product lines you're working on. * Work with engineers and customer success staff to remote and debug logs in the machine and understand customer problems. * This is an on-site position. You're expected to work on-site with the other team members five days a week. We are based in Los Angeles. Sometimes, nothing will work, and you'll need to conduct experiments until the problem's root cause (hardware or software-related) is fully understood. Before writing any code, you must deeply understand complex topics and communicate proposed solutions to a highly technical team. Ideally, you write the minimum number of lines that solve the problem ("spin lock? Why not? It solves this problem" - "I'll just use a JSON file for now as a database so anyone can easily modify it").