MISSION

We're not trying to manufacture every component of a robot from scratch, and we're not just integrating someone else's finished platform either. Like an automotive OEM, we define the system architecture and source the best components for each part of it — while keeping full system-design and integration ownership in-house. That includes deliberate trade-offs: not every component needs to be top-spec everywhere, and where those trade-offs land has to be understood by the system as a whole, including the software controlling it. You'd own that end-to-end.

WHAT YOU'LL DO

Define the system architecture for full (humanoid) robot builds — actuation, end effectors, sensing, compute, power — sourced from external suppliers rather than built from scratch in-house.
Own supplier and component selection: evaluating, qualifying, and integrating parts from multiple vendors into a single coherent system.
Make deliberate cost/capability trade-offs across subsystems based on target use cases — for example, a lower-cost, less sensitive component on one side of the robot where the task doesn't demand more, and a higher-spec one where it does.
Make sure those hardware trade-offs are legible to the rest of the system: specifications, capabilities, and limitations of each configuration need to be knowable and usable by the software controlling the robot.
Work directly with our research team so hardware decisions and the "brain" controlling the robot develop together, not in sequence.

WHAT WE LOOK FOR

Senior‑level experience (10+ years) in robotics hardware, mechatronics, or complex electromechanical systems integration — you've owned a full system, not just a subsystem.
Track record of building complete robots or comparably complex systems from externally sourced components, including supplier evaluation and qualification.
Strong systems‑level thinking: comfortable making and defending trade‑offs across an entire build, not optimizing one part in isolation.
Able to work closely with software/controls teams — you don't need to write the control code, but you need to think about how hardware decisions affect it.

NICE TO HAVE

Direct experience with humanoid or other complex multi‑DOF robot platforms specifically.
Background in automotive or another OEM‑style industry where system integration with externally sourced components is the norm.
Experience specifying or working with asymmetric or non‑uniform hardware configurations (different specs for functionally different parts of the same system).
Existing supplier network in robotics components (actuators, end effectors, sensing, compute).

#J-18808-Ljbffr

OMN4I