Defence Systems Integration Engineer

There's a layer of engineering that doesn't get talked about enough - the one that makes everything talk to everything else.

We're working with a European defence‑tech company whose autonomous platforms are operationally deployed with allied military clients. As their sensor and C2 integration portfolio grows, they need an engineer to own the interoperability layer - the protocols, pipelines, and partner‑facing interfaces that connect their systems to the broader defence ecosystem.

The role:

You’ll design and maintain ingestion pipelines for heterogeneous external track sources - radar feeds, sensor networks, and tactical data links - normalising data into a coherent internal model consumed by downstream guidance and fusion systems. On the other side, you’ll expose the company’s own systems to partner C2 infrastructure, owning those integrations end‑to‑end from interface review through to live joint test campaigns.

This isn’t a back‑office role. You’ll be in the room - and in the field - when integrations go live, debugging protocol mismatches in real time alongside partner engineers during demonstrations and trials.

As the partner portfolio scales, you’re accountable for keeping the architecture coherent, documented, and maintainable.

What you’ll bring:

• 4–7 years in systems integration, C2 systems, radar data processing, or tactical data link engineering
• Hands‑on, production‑grade experience with at least one of: ASTERIX, CoT, or SAPIENT
• Proven experience integrating with radar systems and/or C2 platforms in an operational or near‑operational context
• Strong Python and/or C++ for protocol parsing and middleware development
• Solid understanding of binary and XML protocol parsing, UDP/TCP/multicast networking, and geospatial coordinate transformations
• Experience producing and maintaining ICDs or interface specifications for external partners

Familiarity with adjacent NATO/tactical standards (STANAG 4586, Link 16, JREAP‑C) is a plus. A defence or dual‑use background is strongly preferred.

Why this:

Real operational deployments. A growing partner portfolio across Europe and beyond. Architectural ownership from day one - not a cog in a large systems integrator.

Based in France.