Drimva

Keyrock

Rust Engineer - Trading Systems

Brussels +32 · Remote · Full-time · Posted Jul 15, 2026

Location
Brussels
Rome
Zug
Porto
Istanbul
Eindhoven
Geneva
Milan
Amsterdam
Manama
Madrid
London
Berlin
Antwerp
Copenhagen
Vienna
Prague
Athens
Budapest
Paris
Frankfurt
Dublin
Warsaw
Sofia
Luxembourg
Remote
Zurich
Lisbon
Tallinn
London OR Brussels
Rotterdam
Krakow
Zagreb

About the job

Designs, operates, and improves low-latency trading infrastructure for Keyrock’s Capital Markets division, with a focus on performance, reliability, and operational excellence.

What you'll do

  • Design, develop, and optimize mission-critical trading systems and own trading-stack components from architecture through production operation.
  • Collaborate with quants, traders, and engineers to improve trading performance and resilience; troubleshoot production issues across exchange connectivity, execution, and market data.
  • Set technical direction, raise engineering standards, mentor engineers, and use AI-assisted workflows to automate operational tasks and evolve agentic tooling.

What they ask for

  • Production-grade Rust experience building high-performance, concurrent systems.
  • Hands-on experience in a systematic trading environment, such as HFT, market making, or quantitative trading.
  • Strong AWS and Linux expertise, including latency-sensitive infrastructure, debugging, and production troubleshooting.
  • Proficiency in Python or another scripting language; familiarity with trading protocols and exchange connectivity.

Nice to have

  • Tokio proficiency.
  • Familiarity with agentic engineering tools and concepts, including LLMs, MCP APIs, AI-First IDEs, harness engineering, and workflow automation.

Tools

Rust, Tokio, AWS, Linux, Python, FIX, REST, WebSocket

AI focus

Use AI-assisted workflows and autonomous agents, automate operational tasks, and help evolve agentic tooling; the posting names LLMs, MCP APIs, AI-First IDEs, harness engineering, and workflow automation.

Model-written summary · the original posting is authoritative

First seen Oct 29, 2026 · Last verified Nov 5, 2026 (UTC)