Senior Software Engineer, Networked Systems (m/f/d)

TYTAN Technologies The PACE is fast. The expectations are high. The contribution matters. Working at TYTAN is more than a job, this is a mission. We push boundaries, think big, and hold ourselves to the highest standard. Our mission and values guide everything we do, and we're looking for people who are driven by ownership, embrace challenges, and are energized by meaningful work. If you're motivated by impact and thrive in dynamic environments, you'll fit right in. At TYTAN , we aim to set a global standard in autonomous air defense with AI-driven, cost-efficient systems that counter unmanned aerial threats at scale. We protect people. We protect critical infrastructure. We protect European sovereignty. We are seeking an experienced and hands-on Senior Software Engineer, Networked Systems to join the Core team within our Platform Team. Everything we build is a node: from small embedded devices to full compute systems and ground infrastructure. Together they operate as one network, in the field and over denied, degraded and intermittent links. You design how this works end to end: how nodes find and connect to each other, how trust propagates, how they communicate, and how every node exposes what the application stack needs. And you build it: the network itself, the node agent that runs on every node, the node API and the SDK. Your roadmap to make an impact System design: Own the end-to-end design of how our systems connect and communicate: topology, links, transports, delivery semantics and failure behaviour. When a new requirement lands, such as operating a system beyond line of sight over LEO satellite or cellular links, you design how it works: latency budget, link selection and failover, security, and what keeps working when the link drops The network: Build it: addressing plans, routing, segmentation and multi-homing across tactical radio, cellular, satcom and wired links, with dynamic routing and link selection for nodes that move and links that fail Secure links: IPsec/IKEv2 or WireGuard overlays with certificate authentication from hardware-backed keys, including rekeying, NAT traversal and behaviour on link loss Trust: Design how trust propagates from production to the field: device identity, certificate lifecycle, mutual authentication, authorisation tiers, revocation and signed commands that keep working without backend connectivity Node agent: Design and build the agent that runs on every node and exposes identity, health, software state, connectivity and updates through one API, served locally, over the network and in compact form over constrained links. Devices too small to run it are represented through their parent node Node API and SDK: One resource model for every node type, versioned and backward compatible across a fleet that never updates all at once, with SDKs generated from the contract for the languages our teams use Discovery and directory: How nodes find each other with and without infrastructure, and a directory that survives restarts and shows what should exist versus what is present, at fleet scale without polling every node Communication: Build on proven middleware and transports instead of reinventing them, define delivery semantics per traffic class, and engineer QoS so command and control traffic survives congestion on constrained links Network as code: Configuration templated, version controlled, validated in CI and shipped as part of the system release Verification: Network emulation that reproduces measured field link profiles, fault injection in CI, and network test campaigns at test ranges and flight tests with root cause from packet captures Direction: Write the design documents and contracts that embedded, backend and application engineers build against, and review designs Degree in Computer Science, Electrical Engineering, Telecommunications or a related field, or equivalent experience 5+ years building networked or distributed systems in production, combining software engineering with hands-on network engineering, including technical ownership of a core component other teams depend on Designed a networked system end to end, and can reason through a new connectivity scenario from first principles: topology, latency budget, failure modes and security Expert in Rust, Go or C++, working proficiency in Python, and comfortable reading and writing C++ Strong networking across the stack: IP addressing and routing, UDP, TCP and QUIC internals, congestion control, multicast, NAT traversal, MTU and fragmentation; fluent with Wireshark and tcpdump Expert Linux networking: iproute2, policy routing, network namespaces, VRFs, bridges, VLANs, nftables, tc and netem Production experience with IPsec (strongSwan or libreswan) and WireGuard, including PKI-based authentication Routing: OSPF and BGP (ideally FRRouting or BIRD), and how latency, loss and link quality shape routing and protocol design in dynamic networks Applied security: PKI and certificate lifecycle, mTLS, hardware-backed keys (TPM or secure elements) and authorisation models Built services that run on devices: Linux daemons, systemd, local IPC and resource-constrained environments Experience with middleware such as DDS, ROS 2, Zenoh, ZeroMQ, NATS or gRPC, including discovery, flow control, serialisation and QoS API and contract design consumed by many teams: schema evolution, versioning and backward compatibility Written design documents that other teams implemented against Willingness to travel to test sites and flight tests (around 20%) Nice to haves Systems built for denied, degraded, intermittent or limited (DDIL) connectivity: defense, robotic fleets, autonomous vehicles, space Beyond-line-of-sight operation over LEO satellite, cellular or long-range radio links Integration of MANET or mesh radios (e.g. Silvus, Doodle Labs, Persistent Systems) and MANET routing such as OLSR or B.A.T.M.A.N. Network emulation with EMANE, CORE, ns-3 or Linux netem Time synchronisation with PTP/gPTP Replication and