Systems Engineer - Physical Products

As a Systems Engineer / Architect, you are responsible for both the architectural design and the hands-on implementation of complex systems for Helsing’s mechatronic and software-defined programmes. You will act as the visionary who defines how the system fits together, as well as the "builder" who actively makes it work. You will translate high-level operational concepts into robust physical and logical architectures, partitioning complex multi-domain systems across hardware and software. At the same time, you are not an "ivory-tower" theorist—you will spend significant time in the lab integrating hardware, debugging mechatronic issues, and validating that the physical product meets your design intent. Working closely with mechanical, electrical, and AI engineering teams, you will utilise Model-Based Systems Engineering (MBSE) methodologies to track subsystems and define critical interfaces. In this role, you are responsible for bridging the gap between cutting-edge AI software and high-performance physical hardware, ensuring on-time and high-quality technical delivery. The day-to-day includes developing and owning the overarching system architecture for complex, multi-domain platforms (e.g., drones, sensor pods, ground support systems), partitioning them into manageable hardware and software subsystems; acting as the primary owner of the system model, utilising Model-Based Systems Engineering (MBSE) tools (e.g., Cameo, Enterprise Architect) and SysML to document system behaviours, state machines, and interfaces; actively participating in the physical integration of mechatronic systems in the lab and field, working directly with hardware and software to test, troubleshoot, and validate performance; leading multidisciplinary trade-off analyses (e.g., SWaP-C: Size, Weight, Power, and Cost) to determine the most effective, scalable architectural solutions; translating high-level architectures into detailed subsystem and component specifications, establishing clear requirements and interface control documents (ICDs); conducting system-level testing, analysing test data, and supporting complex root-cause analysis on failures to drive rapid design iterations.