Supporting Tech Lead - Maritime

Who we are

Helsing is a defence AI company. Our mission is to protect our democracies. We aim to achieve technological leadership, so that open societies can continue to make sovereign decisions and control their ethical standards.

As democracies, we believe we have a special responsibility to be thoughtful about the development and deployment of powerful technologies like AI. We take this responsibility seriously.

We are an ambitious and committed team of engineers, AI specialists and customer‑facing programme managers. We are looking for mission‑driven people to join our European teams – and apply their skills to solve the most complex and impactful problems. We embrace an open and transparent culture that welcomes healthy debates on the use of technology in defence, its benefits, and its ethical implications.

Helsing's maritime team is developing next‑generation uncrewed underwater vehicles (UUVs), including the SG‑1 Fathom platform and the Lura AI system, purpose‑built to secure the subsea domain for open societies. As Supporting Tech Lead, you will sit at the centre of that effort, providing the whole‑system engineering perspective needed to move the programme from prototype to a documented, repeatable, production‑ready platform across a 40‑unit build.

You will work alongside a skilled team of mechanical, electrical, and embedded engineers, bringing subsystems together into a coherent, buildable whole. Where competing design approaches create decision deadlocks, you will draw on your knowledge of what works underwater, what has been proven at depth, and what scales to production, to make well‑reasoned calls and keep the programme moving. You will also play an active part in day‑to‑day team coordination, ensuring that deep domain expertise converts into concrete decisions and forward momentum rather than further analysis.

The work is technically demanding, the timelines are short, and the output has direct relevance to the security of open societies.

• Ensure every design decision accounts for manufacturing, assembly, and test from the outset, so that unit 37 can be built identically to unit 1
• Own design documentation, version control, and assembly instructions to a standard complete enough for someone outside the room to build from
• Support supplier selection and qualification, identifying volume‑available components, custom‑development requirements, and single‑source risks that could affect programme delivery
• Drive the transition from engineer‑built prototype to a fully documented, production‑ready build across the 40‑unit programme

• Lead the integration of all subsystems, including the flight‑controller board, edge compute, hydrophone array, satcom, network router, and sensor suite, ensuring each interface is clearly defined and validated
• Coordinate with the Software Tech Lead to ensure the on‑glider software stack and hardware requirements remain mutually consistent throughout the development cycle
• Define and execute the test strategy from bench through tank trials to open‑water sea trials, capturing findings and iterating the design accordingly

• Apply whole‑system UUV knowledge to resolve competing design approaches, drawing on what has been validated at depth and what is known to scale to production
• Assess available options with the information at hand, make well‑reasoned calls, communicate the rationale clearly to the team, and keep the programme moving
• Ensure the team's collective expertise in mechanical, electrical, and embedded domains converts into forward momentum

• Work with the existing technical team to advance Helsing's maritime products from current concept to a fully buildable, producible system
• Own trade‑off decisions that span mechanical, electrical, and embedded software boundaries, articulating reasoning with enough clarity to secure team alignment
• Distinguish between designs that are ready to build and those that need further iteration, preventing the programme from stalling in unnecessary refinement cycles
• Embed scaled‑manufacturing thinking from the outset, not as a downstream…