Data foundations
Make observations usable.The work starts with reliable inputs: consistent identities, precise timestamps, and a clear account of what was known when. Data quality is part of the research.
Technology / Precision under pressure
Deep thinking.
Fast systems.
Good engineering closes the distance between understanding a market and acting in it. Speed matters. So does knowing exactly what your system is doing.
01 / The engineering problem
One continuous research loopResearch systems
Make experiments repeatable.Connect exploration to reproducible evaluation. A result should be traceable to the data, assumptions, and code behind it, so another person can question it and build on it.
Trading infrastructure
Make decisions actionable.High-frequency trading brings research into contact with time. Event-driven systems, efficient execution paths, and observability make latency a problem we can understand and improve.
Control & feedback
Make behaviour visible.Design for the unexpected. Risk constraints, monitoring, and the ability to understand a decision belong alongside the execution path. Every outcome should inform the next experiment.
02 / How we think
Performance is
a systems problem.
A faster component is useful only when the full decision improves. We care about the path from an arriving observation to a controlled response, and the trade-offs at every step.
That makes the boundary between research and engineering an interesting place to work. A better data model can improve a forecast. A better execution model can change what is worth researching.
We look for people who enjoy crossing that boundary.
For the curious. For the exacting.
There are harder problems
worth working on.
Bring your questions, your craft, and a different way of seeing things.
Build with us