C++ Software Engineer - Low-latency systems

Company | Financial markets infrastructure firm (exchange & trading technology)

Size | ~250 people globally

Technology | C++, Linux, Networking, Python

Hybrid | 3 days a week in the office

Offer | Various levels considered Mid & Senior

Benefits | Private medical, pension, discretionary bonus, enhanced parental leave, life assurance, income protection, electric car scheme, cycle to work, flexible hours

The Work

Not every C++ job sits this close to a live market.

You’ll be building the software that processes trading activity in real time, systems that must stay reliable under heavy message throughput and respond in microseconds, not milliseconds.

Your work will sit inside a core engineering team responsible for the platform that powers electronic markets across Europe.

You’ll spend your time solving problems like:

• Processing thousands of market events every second
• Designing software that stays stable under extreme load
• Improving latency, performance and system resilience

You won’t be working in isolation either. You’ll collaborate daily with engineers focused on infrastructure, product and quality to ensure every release is stable and production-ready.

And the problems are genuinely technical.

You’ll work on event-driven systems, networking protocols and real-time architectures where small design decisions have a measurable impact on performance.

The engineering team is compact and experienced. You’ll have the freedom to explore solutions, challenge ideas and contribute to architectural discussions, not just implement tickets.

What you’ll need

This environment suits someone who enjoys deep technical problems and systems that must perform under pressure.

You’ll likely bring:

• Experience building or maintaining real-time or event-driven systems
• Solid Linux development experience and understanding of networking (TCP, UDP or multicast)

And you’ll probably recognise some of the following:

C++, Boost, Python, Git, SQL, messaging systems, distributed architectures.

Exposure to financial markets technology such as FIX or other trading protocols is useful, but not essential if you’ve worked on other high-throughput systems.