Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
Octavian Robotics, Inc. is hiring the first robotics software engineer to join founders in building a surgical robotics company in Los Angeles.
You will design software to control robotic tools, shape initial infrastructure, and collaborate with hardware engineers to translate customer needs into robust software solutions. You will work closely with customers and the sales team, and mentor junior developers while navigating a high-pressure, high-impact environment focused on saving lives through
Octavian Robotics is solving the #1 complication in the $3T surgical industry. We are building robots for the sterilization of surgical tools. Only now with generalized robotics models have we been able to tackle this problem and save lives.
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.
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.
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").
Your work will be focused more on clear communication and business impact than on lines of code you can write or cool tech you can use.
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.