Staff Systems Engineer - Robot-as-a-Service Platform

Apptronik is a human-centered robotics company developing AI-powered robots to support humanity in every facet of life. Our flagship humanoid robot, Apollo, is built to collaborate thoughtfully with people, starting with critical industries such as manufacturing and logistics, with future applications in healthcare, the home, and beyond. We operate at the cutting edge of embodied AI, applying our expertise across the full robotics stack to solve some of society's most important problems. You will join a team dedicated to bringing Apollo to market at scale, tackling the complex challenges like safety, commercialization, and mass production to change the world for the better.

JOB SUMMARY

We’re hiring a Senior Systems Engineer to help drive architectural clarity across our Robot-as-a-Service (RaaS) platform — the edge and cloud software that connects our humanoid robots to operators, customer systems, and the broader fleet.

This role lives at the interfaces: between the robot and the platform, between the platform and customer integrations, and between product intent and engineering execution. You will focus on systems thinking and broad technical judgment — defining the right architectural constraints, drawing clean interfaces, and surfacing the decisions that most shape the solution so the right architecture can emerge underneath.

You’ll work as part of the engineering team, collaborating across disciplines to provide architectural clarity, shape the direction of the RaaS solution, and ensure the most important decisions are made well and made on time. Strong cross-functional communication is central to the role — much of your impact will come from helping others align around a shared understanding of the system.

ESSENTIAL DUTIES AND RESPONSIBILITIES or KEY ACCOUNTABILITIES

• Define functional and non-functional requirements for the RaaS platform — including its interfaces to the robot, to customer software, and to operator-facing tools.
• Specify architectural constraints (latency, availability, security posture, data ownership, failure semantics) without overconstraining the design.
• Own the contracts at key system boundaries: robot APIs, integration APIs for external software providers, and the core platform behaviors that customers depend on.
• Drive cross-functional decisions to closure — surface the few high-leverage choices, frame the trade-offs clearly, and keep the team moving.
• Translate product intent into engineering scope, and engineering reality back into language product and customers can act on.
• Go deep where it matters — across data pipelines (data collection, inference, fleet management), the robot-facing API surface, or cross-cutting concerns like security — as the platform evolves and the work demands.

SKILLS AND REQUIREMENTS

• A genuine systems-thinking mindset: you reason about emergent behavior, failure modes, and feedback loops,