Senior Hardware Test Engineer

Here at Humanoid, we believe in a future where robots amplify human potential. That’s why we’ve set out on a mission to build the world’s most capable, commercially-scalable, and safe humanoid robots. We’re bringing that mission to life with HMND‑01 - our rapidly developed humanoid platform being deployed in real industrial environments - and we’re growing the team to take it even further.

About the Role

We are looking for a Senior Hardware Test Engineer to own the test methodology for HMND‑01’s hardware components, robot subsystems, and complete humanoid robots. You will be the engineer who decides what “good” looks like — from a single actuator on the bench to a full robot walking through an integration sequence. This is a hands-on, technical leadership role. You will design test methods, run them yourself on early prototypes, and partner closely with the test automation team, Manufacturing Engineering, Production Operations, and Supply Chain Quality as we move from EVT toward production. You’ll be the hardware voice that shapes what gets measured on the line, at what tolerance, and why — without owning the QC routine or rig build, which sit with Production Ops Quality and Manufacturing Engineering respectively.

Key Responsibilities

• Test Method Definition
  • Component-Level Methods: Define functional, performance, and stress tests for individual hardware components — actuators, sensors, electronics, structural parts — including pass/fail criteria and required data capture.
  • Subsystem Testing: Design integration tests for major robot subsystems (arms, hands, legs, torso, head) covering kinematic accuracy, repeatability, load behavior, and thermal response.
  • Whole-Robot Testing: Define and execute system-level tests for full robot assemblies, including end-to-end motion sequences, balance, manipulation tasks, and failure-mode behavior.
• Hands-On Test Execution
  • Prototype Bring-up: Be the first engineer to put hands on each new hardware revision, characterising performance against design intent and feeding findings back to the design team.
  • Failure Analysis: Investigate failures during testing, work with hardware engineers to root-cause issues, and verify fixes.
  • Test Documentation: Capture methods, results, and learnings in a way that the rest of the organization can repeat and trust.
• Automation Support
  • Test Automation Inputs: Translate manual test methods into specifications for the automation team. Decide which tests can be automated and which must remain manual, and why.
  • Tooling: Specify and prototype custom test fixtures, jigs, and instrumentation needed to execute your methods reliably during prototype and bring-up work.
  • Data: Define what each test must capture so that automated runs produce results comparable to your manual baseline.
• Production Test — in partnership with Manufacturing Engineering and Production Ops
  • Requirements for Line Rigs & Jigs: Provide the technical requirements for production test jigs, fixtures, and test beds — what they measure, at what tolerance, what data they need to capture, and the pass/fail criteria.
  • In-Process Verification: Define the checks at each stage of assembly that confirm components and sub-assemblies have been built correctly before they move to the next station, including required measurements and rework paths for failures.
  • Test Evidence & Traceability: Define what each production test must capture so that results, measurements, and pass/fail outcomes are written to the production database, linked to the serial number of the unit under test — every shipped robot has a complete and queryable build and test history.
  • System-Level Acceptance: Define final-product acceptance tests — performance envelopes, functional gates, and sign-off criteria for a robot leaving the line.
• Quality & Design Feedback Loop — in partnership with Supply Chain Quality and Production Ops Quality
  • Component Performance Characteristics: Define the system-level performance characteristics that incoming parts must meet.
  • Root-Cause Partnership: Partner with Production Ops Quality on root-cause analysis when line failures trace back to component behavior or system design, and feed findings back into engineering.
  • Closed Loop with Design: Treat test data as a closed loop with design — surface trends from production into design reviews so the product gets better, not just the process.

Qualifications

Must-Have:

• Experience: 5+ years in hardware test engineering, with hands‑on testing of complex electromechanical systems — robotics, automotive, aerospace, or similar.
• Test Methodology: Strong grasp of test theory, test design, and pass/fail criteria definition. You can write a test spec that another engineer can execute without follow‑up questions.
• Mechanical: Solid understanding of mechanical design principles, common core components (gears, bearings, actuators), measurement tools (calipers, micrometers, load cells, encoders), and technical drawings including GD&T basics.
• Electrical: Comfortable reading schematics, using a multimeter and oscilloscope, and reasoning about basic power and signal integrity.
• Production Fluency: Familiarity with hardware production operations — flow, takt, work instructions, traveler documentation — enough to collaborate effectively with Manufacturing Engineering and Production Ops without trying to own their work.
• Tooling: Experience with test and task tracking systems (Jira, X‑Ray, TestRail, or similar).
• Matrix Operating Style: Comfortable influencing test stations, rigs, and equipment design through clear requirements and tight partnership, not through ownership.
• Mindset: Systems thinking — you naturally see how a problem at the component level can manifest as a behavior at the full‑robot level.

Nice-to-Have:

• Robotics experience, especially with serial-link manipulators or legged systems.
• Hands‑on test rig and fixture design experience (mechanical and/or electrical) — useful for speaking the same language as Manufacturing Engineering on rig requirements.
• Python (or similar) for ad-hoc data analysis and lightweight test automation.
• CAD (SolidWorks/Fusion/NX) for sketching test fixtures.
• Familiarity with ROS2.
• Experience with embedded systems and field buses such as CAN or EtherCAT.
• Experience with industrial automation equipment (servos, gateways, sensors, PLCs).
• Knowledge of statistical quality control fundamentals (SPC, MSA) — for working effectively with Quality on test data interpretation.

What You'll Be Testing

• Actuators (motors, gearboxes, encoders, drivers)
• Robot manipulators and end-effectors
• Legged subsystems and balance behaviours
• Power and battery systems
• Full humanoid robot assemblies