The Role
As Head of Hardware, you own the physical realization of our humanoid platform. You take the robot from a working prototype to a machine that can be built repeatably, reliably, and at rising volume. You come from mechanical engineering and have shipped mechanically demanding products in serious quantities. You are not an electronics designer, but you have led enough electronics work to hold that discipline to the same standard: to read a power budget, question a thermal margin, and know when a schematic review is being rushed.
You work directly with the founders and with the Head of System, who owns the robot's architecture and behavior. You own how that architecture becomes a physical product. The Mechanical Lead, Electronics Lead, and Integration & Operations Lead report to you.
Key Responsibilities
Physical product ownership. Own structures, actuation packaging, electronics integration, harnessing, and thermal behavior of the robot as a built object.
Industrialization. Drive the path from one-off builds to repeatable low-volume production and beyond: DFM, tolerance strategy, supplier and tooling decisions, build documentation, and yield.
Engineering leadership. Build, mentor, and lead the mechanical, electronics, and integration teams. Set the hiring bar and grow leads into the roles the company will need in two years.
Standards and process. Establish design review practice, release and change control, requirements traceability into physical design, and the technical decision frameworks that keep a growing team coherent.
Reliability and validation. Own robustness and lifetime of the hardware. Define what has to be tested, drive the test infrastructure, and make validation results the basis of design decisions rather than an afterthought.
Safety in the physical domain. Champion safety-first engineering for machines that share space with people, building on our functional safety work in ISO TC299 and the emerging humanoid standards.
Supply chain and cost. Own hardware cost structure, supplier selection, and the make-versus-buy decisions that determine how fast we can scale.
Interface with system architecture. Partner with the Head of System so that architectural decisions are made with manufacturability, cost, and serviceability on the table from the start.
