Frontend Developer
HFT Architecture
Get hot jobs first on Telegram
New positions appear faster in our channel
- Location
- United States
- Job Type
- full-time
- Work Format
- 🌍 Remote Worldwide
- Salary
- USD 150,000–190,000 a year
- Posted
- November 20, 2026
Job Description
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
Open our Consulting page and explain in one sentence what a client receives during the first week of working with us. This short question helps us filter out bot submissions.
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.
🎯 Who is this job for?
This role is suitable for a Middle+ to Senior Frontend Developer with experience building and shipping data-driven web interfaces using TypeScript and a modern framework.
The candidate should be skilled in hand-built SVG or canvas visualisations, performance optimisation, streaming WebSocket data, accessibility, and accurately presenting dense numerical information.
They should be familiar with monitoring, trading, operational, or control interfaces involving real-time updates, large datasets, replayable data, charts, tables, and screens that support time-sensitive decisions.
💬 Potential Interview Questions
How would you design a TypeScript frontend architecture for monitoring, control, replay, and dashboard interfaces?
I would separate data ingestion, domain state, and presentation into clear layers, using strongly typed models for market data, system status, orders, and limits. Components would consume normalized state through focused selectors so high-frequency updates do not unnecessarily rerender the entire application.
How would you render thousands of order-book or time-series points efficiently?
For large datasets, I would use canvas or carefully optimized SVG, avoid creating one DOM node per point, and apply viewport-based rendering or level-of-detail reduction. I would measure frame time, memory usage, and update frequency to keep rendering within the target frame budget.
When would you choose SVG over canvas for a dense financial visualization?
SVG is useful when individual elements need interaction, accessibility, or straightforward inspection, while canvas is better for very dense or frequently updated data. A hybrid approach can use canvas for the data layer and HTML or SVG overlays for labels, selections, and controls.
How would you handle streaming updates from a WebSocket without making the UI lag?
I would buffer and batch incoming messages, process them on a controlled schedule, and render at a bounded rate rather than updating the UI for every message. The interface should expose data freshness and explicitly distinguish the latest received timestamp from the latest rendered state.
How would you ensure that a dashboard does not display stale data as current?
Every displayed measurement should carry timestamps, sequence numbers, or freshness metadata, and the UI should show connection and processing status. If updates stop or fall behind, the interface should visibly indicate the stale state instead of silently retaining old values.
How would you build a replay view for a day of order-book data and trading decisions?
I would model replay as a deterministic timeline with indexed events, checkpoints, and a current cursor, allowing stepping, seeking, pausing, and playback speed changes. Derived views should be computed from the replay position so the order book, decisions, and metrics remain consistent.
How would you prevent rounding or axis-formatting errors in financial data?
I would keep values in precise domain representations and apply formatting only at the presentation boundary, using explicit rules for tick size, decimal precision, units, and sign conventions. Tests should cover boundary values, very small values, large values, and values near rounding thresholds.
How would you make a chart accessible without relying on color alone?
I would use labels, patterns, line styles, symbols, contrast-compliant colors, and accessible summaries or data tables. Keyboard navigation and screen-reader descriptions should expose the selected series, values, timestamps, thresholds, and important state changes.
How would you design safe controls for stopping or changing an operational trading system?
Destructive actions should clearly communicate scope, current state, and consequences, with confirmation or an intentional interaction pattern for high-risk operations. The UI should show pending, successful, failed, and timed-out states and prevent users from mistaking a requested action for a completed one.
How would you measure and improve frontend performance for a real-time monitoring interface?
I would define targets for input latency, frame rate, update-to-display latency, memory growth, and time to interactive, then measure them with browser profiling and application telemetry. Improvements might include batching updates, reducing allocations, memoizing derived data, virtualizing tables, and moving heavy computation to Web Workers.
📋 Job Summary
HFT Architecture is hiring a remote, full-time Frontend Developer to build high-performance control, monitoring, dashboard, and replay interfaces for its quantitative trading systems. You’ll work with TypeScript, a modern frontend framework, SVG or canvas visualisations, streaming WebSocket data, and performance-focused rendering for dense charts and real-time updates. Work from anywhere in the world for USD 150,000–190,000 per year, with the opportunity to shape mission-critical interfaces where accuracy, clarity, and speed directly matter.
Required Skills
Never miss a JavaScript opportunity
Subscribe to get similar jobs and weekly insights delivered to your inbox
Hiring JavaScript developers?
Post your job to 10,400+ registered developers. Starting free.
See PricingRelated jobs
Is this your listing? Claim or request removal