What You Own: one venue, stage by stage:

• Scoping. Read the venue's specifications; list what the platform has and what is missing; estimate the setup.Scoping.
• Connectivity. Design it with infra: colocation or proxy, lines, addresses, multicast groups, firewall rules, failover.
• Protocol adaptation. Adapt our market data and order entry connectors to the venue's binary protocol: SBE, FAST, ITCH and OUCH, Eurex ETI and EOBI, LSE native, or the custom binary protocol a venue publishes for itself; sessions, recovery, throttles, reject handling.
• Product and risk parameters feed. Pull the venue's raw product definitions and risk parameters, margin rates, price limits, lot and tick tables, position limits, in whatever form they are published, and deliver them complete to the team that normalizes them; you are their source on what the venue's fields mean.
• Historical data. Convert the venue's archives and captured feeds into our format at volume; validate against live captures.
• Latency tuning. Measure the path with hardware timestamps against the venue's figures and the strategies' budget; tune host placement, NIC and kernel bypass settings, pinning, the connector's hot path, gateway choice; record the baseline for ops.
• Certification. Pass the venue's conformance tests and ours: replay, soak, order-flow scenarios, failover.
• Operations preparation. Write the operating instructions for the desk and ops: sessions and timings, limits, start and stop, failure modes and what to do in each, who to call at the venue. Walk the desk through the first day before it happens.
• Go-live. First live trade, hypercare, handover.

What This Role Is Not:

• Not the core engine: the engine developers in the same team own it; you adapt and assemble.
  
• Not configuration: a venue needs code, in C++ and Python; an LLM writes much of it, you specify, review and test all of it.
• Not normalization: another team maps the venue's products and risk parameters onto our model; you deliver the raw feed they map from.
• Not 24/7 operations: the desk and ops run the venue after handover; you write what they run.
• Not strategy work: researchers decide what and how to trade; you make the venue tradable.
  

What We Look For In You:

• Solid understanding of data structures, algorithms, and object-oriented programming in C++
• Understanding of Linux system internals
• Decent level of written and spoken English to work in an international environment
• Performs well in a remote/hybrid team with variable, project-based responsibilities

Nice-to-have: 

• In-depth knowledge and expertise with low latency/real-time development with sub-microsecond latency.
• LockFree containers and thinking pattern
• C programming knowledge (written drivers for Linux system, worked with the core etc.)
  

Why Should You Join Our Team?

• Full focus on results with no bureaucracy
• Great challenges with fast feedback loops
• A welcoming group of highly qualified international professionals
• Cutting-edge hardware and technology
• Work remotely from anywhere in the world
• Access any of our global offices anytime
• Flexible schedule
• 40 paid days off
• Competitive salary