Senior Software Engineer, Internal Systems (Robotics)

Job description

Job responsibilities

• Own the shared data model: The definitions of robots, sites, customers, parts, jobs, and people that every internal system reads.
• Own the internal systems each operations function runs on: Maintenance tickets and service history, manufacturing work orders and serialized builds, tutoring and teleoperation queues, deployment records, and the…
• Turn how a function works into software: Sit with the people doing the work, understand the process, and build the system that carries it out
• Keep operations data trustworthy: Reconcile systems that disagree, replace the spreadsheets, and build the reporting the company uses for its weekly decisions
• Build with AI agents: Direct agents across a large internal codebase, keep the codebase in a shape agents work well in, and review what they produce
• Support the people who use what you build: Same-day answers when a floor or field process is blocked on a tool, and a fix to the process itself when the tool was not the problem

Job requirements

• 6+ years building production software, including ownership of internal or operational systems: You have owned a system a business depends on day to day
• Data modeling as a discipline: You have designed and evolved a relational schema that many teams depended on, and carried out the migrations. PostgreSQL experience preferred
• Full-stack fluency: TypeScript and React on the front end, Python or TypeScript services on the back end, and comfort in whichever layer the problem is in
• Comfort with the people side of operations: You can sit with a technician or a plant manager, understand what they do, and come back with software that fits it
• Comfort with AI coding agents: You have used tools like Claude Code or similar for real engineering work, directing agents through multi-step tasks. You understand their failure modes and know when to trust vs. verify
• Judgment about what to build: You lean toward building a tool over buying one, and you can tell when buying is right. You know when a process needs software and when it does not