Simulation Architect – Defence

Il y a 1 jour

Paris, Île-de-France Helsing Temps plein

The role

Evaluating modern combat systems and training tactical AI requires more than isolated component models or a fast software backbone — it requires architecting how operational reality is represented and connected inside a synthetic world. Beyond our core simulation platform, we are building the domain and kill-chain layer of our synthetic environment: specifically, how sensors, effectors, command and control (C2) nodes and communication networks interact as coherent, end-to-end kill chains across Red and Blue forces. To support everything from cloud-scale operational analysis (OA) and AI training to high-fidelity system verification and validation (V&V), our synthetic environment must be fundamentally modular — allowing us to scale scenarios and swap model fidelities without breaking the kill chain.

The role

Evaluating modern combat systems and training tactical AI requires more than isolated component models or a fast software backbone — it requires architecting how operational reality is represented and connected inside a synthetic world. Beyond our core simulation platform, we are building the domain and kill-chain layer of our synthetic environment: specifically, how sensors, effectors, command and control (C2) nodes and communication networks interact as coherent, end-to-end kill chains across Red and Blue forces. To support everything from cloud-scale operational analysis (OA) and AI training to high-fidelity system verification and validation (V&V), our synthetic environment must be fundamentally modular — allowing us to scale scenarios and swap model fidelities without breaking the kill chain.

The day-to-day

  • Architect the end-to-end kill-chain structure of our synthetic environment, defining how sensing, C2 and battle management, communications and datalinks, and effectors interact across Red and Blue forces
  • Design and maintain the interface control documents (ICDs), data contracts and functional boundaries between kill-chain components so models remain strictly decoupled and interchangeable
  • Design multi-fidelity kill-chain contracts that allow any sub-model to be swapped seamlessly across granularity tiers — from fast lookup tables and functional power-and-effect models to physics and signal-level representations — without altering surrounding kill-chain logic
  • Translate real-world military doctrines, operational concepts and multi-domain engagements into clean, abstracted simulation architectures that scale from single-engagement V&V to large-scale constructive OA campaigns
  • Deconstruct, modularise and integrate existing constructive simulation frameworks and partner domain models (e.g. legacy C++ sensor, effector and behaviour models) into our modular kill-chain architecture
  • Collaborate with core simulation backbone engineers to ensure domain-level kill-chain designs map cleanly onto the underlying runtime, time-management and execution infrastructure
  • Define V&V and consistency criteria across fidelity tiers, ensuring that lower-fidelity abstractions remain calibrated and credible against higher-fidelity reference models
  • Connect military operational stakeholders, partner engineering teams and internal AI and platform teams to align all aspects of the synthetic environment domain architecture

You should apply if you

  • Have architected and delivered domain logic, functional interfaces and end-to-end kill chains (sensors, C2, communications, effectors) for military or aerospace simulation environments
  • Design modular, multi-fidelity simulation architectures, abstracting real-world systems so that a lookup table, a functional model and a high-fidelity physics model can share a common architectural contract
  • Apply deep military domain and OA understanding (Red and Blue doctrines, air and land combat systems, sensor-to-shooter workflows) to translate operational reality into formal system and interface designs
  • Navigate, assess and modularise existing simulation frameworks and model codebases (e.g. C++, Python, MATLAB/Simulink) to extract domain logic and define clean integration boundaries alongside software teams
  • Balance the architectural trade-offs between simulation fidelity, computational scalability and operational validity across different use cases (large-scale Monte Carlo OA, AI training, SIL/HIL V&V)
  • Communicate complex architectural and operational concepts clearly across disciplines, aligning software engineers, domain modellers and defence stakeholders around shared interface standards

Note: We operate in an industry where women, as well as other minority groups, are systematically under-represented. We encourage you to apply even if you don’t meet all the listed qualifications; ability and impact cannot be summarised in a few bullet points.

Nice to have

  • Have architected