Simulation Engineer

Job Overview

At Helsing, a defence AI company, we're seeking a Simulation Engineer to join our European teams in Munich, Berlin, London, Paris, Warsaw, or Tallinn. You'll be part of a team that develops a system for simulating large-scale 3D worlds containing hundreds of actors, rendered in real time.

Responsibilities

As a Simulation Engineer at Helsing, you will work on the internals of the simulation stack, including modelling of vehicles and other actors, integration of high-fidelity models from domain experts, sensor and environment simulation, networking, and interfacing with other components in a distributed system.

Key responsibilities include:

• Building and maintaining simulation platform internals: subsystem architecture, replication and multiplayer, performance profiling, and interfaces used by other systems to orchestrate simulation.
• Composing simulated platforms from sensor, communications, situational awareness, effector, and control-loop models, and reasoning about the underlying physics such as flight dynamics, rigid-body behaviour, collision, and line of sight.
• Owning the trade-off between fidelity, throughput, and engineering cost, choosing the right point for each use case and validating the result against subject matter experts, integration tests, or downstream outcomes.
• Integrating 3D models, animations, and effects from Content Engineers into the simulation.
• Investigating simulation bugs to bridge the gap from simulation to a reference model.

Day-to-Day

In this role, you will write production code that shapes both the simulation platform and the models running inside it. You will decide how each piece of work is validated and translate mission requirements from subject matter experts into reusable simulation models.

Requirements

To succeed in this role, you should:

• Have built real simulations beyond toy projects, especially with game engines such as Unreal, Unity, or Godot, including gameplay frameworks, replication, and profiling tooling.
• Write production code and bring proper software engineering practice into simulation work, including version control discipline, resolving ambiguity, and designing for the long term.
• Reason fluently about the trade-off between physical fidelity and simulation throughput.
• Translate input from domain experts into models and behaviours, and know when real-world fidelity is needed and when it is expensive noise.
• Judge a simulation by what it enables rather than by whether it passes its tests.

Nice to Have

While not required, the following skills are desirable:

• Experience with entity-component-system architectures or agent-based modelling.
• Experience with distributed simulation standards such as HLA, DIS, RPR-FOM, NETN, or FMI.
• Background in physics-heavy simulation, for example CFD, finite element methods, multi-body dynamics, or trajectory and 6DoF modelling.
• Experience with RF, electronic warfare, or radar simulation, including propagation and signal processing chains.
• Familiarity with reinforcement learning environment APIs, or with software-in-the-loop and hardware-in-the-loop validation.
• Experience with Rust, CUDA, or MATLAB and Simulink.