HFT Architecture builds short-horizon price prediction and the trading system around it. Beside the path that trades runs a slower one that people look at: control, oversight, replay and dashboards. This role builds what they look at. It is fully remote: you can work from anywhere in the world.
What you will do
- Build the interfaces of the slow path: what the system is doing now, what it did, and where to stop it.
- Draw measurements so they can be read: dense charts, tables aligned on the decimal point, a figure next to its sample and its limits.
- Build replay views: a day of order-book data and the system's decisions on it, stepped through.
- Keep an interface honest under load. A screen that lags behind the data shows the past and calls it the present.
- Work from the data outwards. The numbers decide the layout.
What you need
- Web interfaces you built and shipped, with real data behind them.
- TypeScript and one modern framework known in depth.
- Data visualisation done by hand, in SVG or canvas, not only through a charting library's defaults.
- Performance you measured: rendering thousands of points, streaming updates, a frame budget you kept.
- An eye for a number that is displayed wrongly: a rounding, an axis, a stale value.
Good to have
- Trading, monitoring or other operational interfaces, where a person acts on what the screen says.
- Streaming data over WebSocket.
- Accessibility for data: a chart that can be read without its colours.
Read before you apply
The charts in this article are the kind of drawing the role makes: Why Your Market Maker Loses Money. The application form asks you to say, in one sentence, what one of our articles is about.
How we hire
- You apply on this page, with a link to your work.
- A technical conversation about an interface you built.
- One practical task close to the work, small enough to finish in an evening.
- A decision, with the reason.