Quantitative Developer

Quant Developer (C++); Remote (UK/EU)

This role is right for a developer who's genuinely annoyed by a 200-nanosecond regression. Who reads a perf profile the way other people read a menu. Who has opinions about cache lines that they will share whether asked or not.

If that sounds like you, keep reading. If it sounds like a friend who won't stop talking about lock-free queues at dinner, send this their way.

The Company

It's trading firm operating at the sharp end of high-frequency and low-latency markets. Every microsecond shaved off the tick-to-trade path shows up directly in P&L, which means the code written here is the thing that's actually live, actually trading, actually making or losing money in real time.

They're looking for a Quant Developer to sit at the intersection of trading, research, and serious engineering, turning ideas from the quant team into production C++ that runs fast enough to matter.

What the Role Actually Involves

• Taking strategies out of a researcher's notebook and turning them into clean, fast, production-grade C++
• Owning the tick-to-trade path and treating every nanosecond like it's theirs to lose
• Profiling relentlessly — finding the slow thing, fixing the slow thing, repeating
• Building the bridge between "here's an idea" and "here's an idea running live in the market"
• Watching over live strategies with proper observability (Grafana, Prometheus — the works), so nothing goes sideways quietly
• Sitting close to the trading and core engineering teams, because the best fixes usually come from actually talking to the people using the code

What They're Looking For

• ~5+ years of real C++ experience (C++17+) in systems where being slow is the same as being wrong
• Someone who knows their way around multithreading, concurrency, and lock-free structures without needing to look it up
• Comfort with the modern toolkit: profiling, CI/CD, instrumentation
• Must Have: Prior experience working in HFT/ latency-sensitive trading environments, with good tenure. Candidates without this will not be considered (client's words, not ours)

Extra Credit

• Network programming chops (TCP/UDP, multicast, FIX)
• Time spent near financial markets or algo trading that didn't scare them off
• Cloud infra experience (AWS) for research or backtesting
• Python or Bash scripting for tooling and automation
• A diagnostic or visualization tool built purely out of being tired of squinting at logs

What This Isn't

• A "your code goes through six committees before it ships" job
• A big, slow, risk-averse engineering org where speed is a slide in a deck, not a metric on a dashboard
• A backend role dressed up with "trading" in the title

Why This Role Exists

The firm would rather have a handful of excellent engineers who genuinely care about performance than a large team that doesn't. Whoever takes this on will own real strategies end to end, work directly with traders and researchers who know exactly what they need, and see the results of their work show up in the market the same day it ships.