We're looking for a Hardware Integration Engineer to own the execution of hardware integration - taking released subsystem designs and turning them into validated, flying prototypes, while our specialist engineers stay focused on their disciplines. This is a deeply hands-on engineering role, not a project management or people management position: you'll work across Mechanical Engineering, Electronics, Embedded Software and Flight Test to ensure complete UAV systems are integrated, debugged, validated and ready for flight, combining practical engineering with technical leadership of prototype execution. Own the transition from subsystem designs to complete, flight-ready prototypes. Lead prototype integration, hardware bring-up and multidisciplinary debugging — catching integration issues before they become flight test problems. Stay hands-on across disciplines: PCB modifications, interface boards and wiring harnesses; mechanical prototype components and fixtures; hardware debugging, assembly, rework and rapid prototyping; and embedded bring-up and validation where required. Act as the primary Hardware Engineering interface to Flight Test — preparing aircraft for testing, making sure tests answer the right engineering questions, supporting investigation of hardware issues, and driving engineering improvements from the results. Build tools and methods that improve hardware development, including board validation firmware, test automation, manufacturing and EOL test solutions, and engineering utilities and instrumentation. Own the technical execution of integrating mechanical, electronics, embedded and systems work into validated, flight-ready hardware, so specialist engineers can stay focused on their own disciplines. Have hands-on experience integrating mechanical, electronics and embedded subsystems into working hardware — in aerospace, robotics, automotive or another hardware-intensive field. Are comfortable debugging across disciplines, from PCB and wiring issues to mechanical fit and embedded bring-up, rather than staying within a single specialism. Have experience preparing hardware for test (bench, flight or field) and turning test results into concrete engineering fixes. Can build your own tools and test infrastructure — firmware, automation, fixtures — rather than relying on others to provide them. Want a deeply hands-on engineering role, not a project or people management position. Communicate well across engineering disciplines and can work effectively with specialist teams without owning their subsystem designs.