Staff/Senior Software Engineer - Hydris - Golang (d/f/m)

Start free →

Or apply yourself on the official page →

About the role

New Challenge About Us  Project Q GmbH ("Q") is a Germany-based DefenseTech company with offices in Berlin and Munich. We network market-available sensors, effectors, or situational awareness systems into a tactical IoT backbone that reliably provides armed forces and security agencies with cross-domain information superiority — automated, scalable, and cost-efficient. Our solutions integrate seamlessly into existing defense and maritime infrastructures, delivering fast data fusion and AI-enhanced analytics for robust situational awareness in dynamic environments. We build platform-agnostic systems that enable real interoperability across domains. As a Staff Software Engineer, you'll directly impact the technical direction of our orchestration products – Hydris – the coordination engine for sensors and mission systems, and the interoperability API that underpins it.  You'll work at the layer where heterogeneous real-world systems like radars, AIS receivers, LoRa mesh radios, satellite feeds, and C2 platforms become a single coherent picture. The problems lie in distributed systems, protocols, and data modeling areas. They play out in environments that are bandwidth-constrained, intermittently connected, and operationally unforgiving.  The role is deeply hands-on, but it expects you to shape what we build and how we build it, not just deliver what's specified. What you'll do Core engine development • Design and build the systems that power Hydris. • Go is your primary language. You should be comfortable reading Rust and TypeScript across the codebase, even if you're not writing in them day-to-day. • Own the architecture of a system that must run reliably on edge hardware, in disconnected mesh networks, and at scale — often all of that simultaneously. Protocol and integration architecture • Evolve the schema that defines how every sensor, asset, and mission system talks to Hydris. • Make API design decisions that hold up across our client libraries without creating a maintenance burden. • Continue refining the integration framework that lets Hydris connect to new sensor types, data sources, and command systems. • Set the patterns for how built-in integrations (ADS-B, AIS, ASTERIX, Meshtastic, SpaceTrack, TAK, federation) are structured, tested, and maintained. • Make it straightforward for external developers and system vendors to build their own plugins/integrations to Hydris. Distributed systems • Architect the peer-to-peer mesh and federation layer that keeps Hydris operational in disconnected, denied, intermittent, and limited-bandwidth environments. • Solve the hard coordination problems: conflict resolution across federated nodes, eventual consistency of entity state, and track correlation across unreliable links. • Ensure the system degrades gracefully rather than failing completely when connectivity is lost or constrained. Technical leadership • Set technical standards for the codebase: how we test distributed behavior, how we handle protocol versioning, how we think about backward compatibility in an API-first product. • Review code with a focus on long-term maintainability and operational correctness, not just feature completion. • Make build-versus-integrate decisions and help the team clearly understand the trade-offs. You should apply if you • Have built and shipped distributed systems that run in production, ideally in environments where reliability matters more than convenience. • Are comfortable working across the stack, from Protobuf schema design and systems-level Go, to the TypeScript that puts a map in front of a user. • Have well-formed views about API design and protocol evolution, informed by experience maintaining APIs that other people depend on. • Can operate effectively with a high de

View the official posting →