Skip to content
Roadmaps / Engineering

HFT Quant Developer

Builds the market-data handlers, order-book engines and simulators a high-frequency team runs on.

The job

An HFT quant developer builds the software a high-frequency, market-making or execution team runs on: market-data handlers, order-book engines, execution schedulers, and the simulators researchers use to decide whether a strategy works. A simulator that fills orders more often than the exchange would makes a losing strategy look profitable, and slow or non-deterministic code makes results impossible to trust. Things go wrong with optimistic fill models, latency, and replays that do not match live trading.

Supports
High-frequency trading, market-making and execution teams
Stages
5 to learn, then proof of work
Two routes
Free resources, or SelfMadeQuant programmes and projects

The roadmap

The same stages either way. The free route uses university courses, lectures, books and papers that are free online. The SelfMadeQuant route maps each stage to our programmes and ends in projects on real market data.

  1. Stage 01 · Foundations

    Programming foundations

    Clean, tested code and the data structures interviews ask about.

    • Python
    • Data structures and algorithms
    • Testing and design
  2. Stage 02 · Core

    Modern C++ and performance

    The language of the hot path, and how to measure what is slow.

    • Modern C++
    • Memory and cache
    • Profiling
  3. Stage 03 · Core

    Systems and networking

    What happens between the network card and your code.

    • Operating systems
    • Concurrency
    • Networking
  4. Stage 04 · Specialist

    Market data and order books

    Exchange feeds, book building and matching rules.

    • Exchange feeds
    • Order-book engines
    • Queue position
  5. Stage 05 · Specialist

    Execution and simulation

    Schedules, replays and fill models a researcher can trust.

    • Execution schedules
    • Replay simulators
    • Fill models
  6. Stage 06 · Proof of work

    An ITCH order-book engine and replay benchmark

    Write a C++ parser for Nasdaq TotalView-ITCH 5.0 and an order-book engine, replay a full sample trading day and record per-message latency and throughput. It answers how fast a single-threaded book can process a day of market data and which data structures dominate the cost.

Practise the interview

Questions this role gets asked, each with a hint and a worked solution.

  1. Why are virtual function calls harder for the compiler to optimise, and what would you do on a hot path?
  2. Design a class that ingests a stream of trades and returns the k most-traded tickers at any moment.
  3. Compute a rolling average over a stream of trades without storing the whole history.

Start the SelfMadeQuant route free: a free account opens one complete topic from each primer and the interview question bank. No card needed.

Start free