Senior Software Engineer, Distributed Simulation (C++)

Job description

Job responsibilities

• Design and build the C++ services that federate independent simulators into a single simulated world — time management, entity registry and ownership, join/resign lifecycle, and state distribution
• Own the wire layer: protocol encoding and decoding, multicast and unicast transport, and the interoperability work required to make simulators built by different teams and vendors talk to each other
• Make simulation runs deterministic and reproducible enough that a result is evidence, not a demo — including time control, replay, and the instrumentation that explains a divergence
• Build and generalize the scenario and laydown authoring tooling that engineers and operators use to describe what they want to run
• Build the content and resource catalogs that let users save, tag, search, and reuse environment and scenario definitions instead of rebuilding them each time
• Chase down performance: profile hot paths, control allocation and copying, and hold latency and throughput budgets under load with hundreds to thousands of entities
• Integrate with the rest of the platform — the Go services that provision and schedule compute, the gRPC/protobuf APIs that expose it, and the web UI the team owns
• Set the technical direction for this area, write the design docs that make it reviewable, and raise the bar through code review and mentorship as the team grows

Job requirements

• 7+ years of professional software engineering experience
• Deep, current production experience in modern C++ (C++17 or newer) — you are fluent in ownership and lifetime, move semantics, templates, and the standard library
• Experience building networked, concurrent, or real-time systems in C++, including multithreading, synchronization, and the failure modes that come with them
• Strong systems fundamentals: memory layout and allocation behavior, cache effects, sockets and UDP/TCP, serialization, and Linux
• Demonstrated ability to profile and optimize a real system, and to reason about latency and throughput with numbers rather than intuition
• Experience owning an ambiguous, cross-cutting project end-to-end and driving it to production
• Experience working directly with the engineering teams who consume what you build — integrating them, unblocking them, and taking their feedback into the next version
• Comfortable working in at least one other language alongside C++ — the surrounding platform is Go and TypeScript, and you will touch both