Software Engineer, 1X

• You work across the full stack, from infrastructure and systems out to the embedded edge, and you switch languages and technologies quickly as the work demands. You do not have to be an expert at every layer, but you carry sound reliability thinking into any of them
• You understand how a mechatronics stack comes together, so you can find the edges of a problem and tell whether it sits in software or hardware. You treat sensing, telemetry, and logging as first class parts of reliability
• You treat reliability as a product with real users, and you own your work e2e and ship without waiting to be told
• You communicate clearly with internal and external stakeholders, turn data into findings people can act on, present them to stakeholder groups, and raise the bar for the people around you
• Strong software engineering background with real depth in at least one layer of the stack (cloud and backend, systems, or embedded) and the range to reason across the rest
• Experience building test and reliability infrastructure, or distributed systems at scale, such as APIs, real time data pipelines, monitoring, and incident management
• Strong DevOps and Linux skills, including CI/CD and infrastructure as code, and fluency in Python plus at least one systems language
• Strong statistical and probabilistic skills and an allergy to the sunk cost fallacy
• Experience building from zero to one and then from one to production

Desirable

• Our team owns the reliability and testing plan for every software system that runs on the robot or talks to it
• That covers the front end, back end, cloud, mobile, on-robot services, and the embedded stack
• Our work runs from hardware-in-the-loop testing and e2e regression through incident management, on-call, observability, release gating, and the SLOs that tell us what reliable actually means
• From the first test a developer writes to the moment the robot moves in someone's home, we make robot software something the company can trust at fleet scale
• Own software reliability as a product
• Start from the whole system and drive reliability practices as far down the stack as they need to go, from web and cloud through mobile, on-robot services, and embedded
• You will build and own parts of an integrated testing package that checks the system e2e, starting with a developer test and ending with real robot movement
• This is critical path work
• As we scale from hundreds to tens of thousands of robots, whether customers can trust their robots, and whether our engineers can move fast, comes down to this layer
• Deliver an integrated testing package that covers every layer of the stack, from web and cloud to mobile, on-robot services, and embedded, and push those reliability standards steadily deeper over time
• Own e2e testing that starts with a developer test and ends with robot movement, and put real numbers on that movement, those actions, and the robot's health
• Triage reliability issues, find where the edges of a problem are, and route them to the right software or hardware team
• Set the pace for software reliability best practices across the org, for internal teams and external customers