The short version

We run an HFT trading stack across global crypto markets. One of the things that stack spits out is market data: order books, trades, derivatives, the lot — captured cleanly and quickly because we need it that way to trade.

Turns out it’s good enough that other people pay us for it, and now it’s a product in its own right: one of the best crypto market data services anywhere.

We need a Data Quality Engineer to make sure the data is complete, accurate and behaving as expected, both live and historically, and to give us the dashboards, visibility, and alerting to prove it.

The Role

We are looking for a Data Quality Engineer with strong analytical instincts and an unusually high attention to detail. You should care about whether data is correct, not merely whether a pipeline is technically running.

You will own the systems we use to monitor and understand the quality of our live and historical market data products. That means building dashboards, defining quality metrics, investigating anomalies and making it obvious when something has gone wrong before a client has to tell us.

Prior experience in high-frequency trading is not required. Experience working with data products, real-time systems, financial data or other high-volume datasets is highly valued.
We like people with an entrepreneurial spirit and the belief that any problem, no matter its complexity, can be understood and addressed.

Preference is given to individuals who are either located in, or open to self-relocating to, London, valuing the benefits of an in-person working environment among peers with similar interests.
This position offers a distinct chance to take ownership of the quality and visibility of a rapidly growing market data product. You will collaborate closely with the engineering, trading and commercial teams, assuming responsibility for specific areas from the outset.

The role affords ample opportunity for proactive engagement in shaping your duties and making meaningful, enduring improvements to how we monitor, validate and communicate data quality.

What you will work on

• You’ll own the dashboards and quality controls that tell us whether the data clients depend on is correct.
  

• Build and maintain dashboards covering live exchange feeds, historical datasets, venue health, latency, gaps, completeness and data delivery.

• Define the metrics that actually describe data quality. Not just whether a service is up, but whether the numbers coming out of it make sense.
  

• Validate and reconcile order books, trades, funding rates, derivatives data and other market data across CEX and DEX venues.
  

• Investigate gaps, stale feeds, duplicates, crossed books, schema changes, unusual prices and all the other ways exchanges do exchange things.
  

• Build automated checks for both live and historical data, and make failures easy to understand rather than producing incoherent alert spam.
  

• Work with engineering to identify the root cause of issues, verify fixes and make sure the same problem does not quietly return.
  

• Own the internal visibility around client-facing data quality, so we know something has slipped before a client does.
  Help define and report against the SLAs behind our APIs, feeds and historical datasets.

Requirements

• 2+ years working with data quality, data analytics, QA, data operations or data engineering in an environment where other people depended on the output. Not coursework, not a dashboard nobody looked at.
  

• Strong SQL and enough Python to analyse datasets, automate checks and investigate issues independently.
  Experience building useful dashboards and visualisations for operational or data-quality monitoring. We care less about which tool you used and more about whether the dashboard helped someone understand what was happening.
  

• A real instinct for data quality — you notice when numbers are subtly wrong, not just when a job fails loudly.
  

• Comfortable working with large datasets and comparing data across sources, time periods and systems.

• Able to investigate an issue methodically, explain what happened clearly and follow it through until it is actually resolved.
  

• Comfortable on the command line and working alongside engineers, even if you are not expected to build production systems in Rust.
  

• Sharp, curious, low ego and allergic to corporate posturing. You’ll be close to the people who depend on your work, so you’ll hear about it quickly either way.

Nice to have

Any of these moves you up the list, none are dealbreakers:

• Crypto, trading, or market microstructure exposure. If you know what an order book is and why a tick matters, say so.

• Exchange APIs and real-time/streaming systems (Kafka, Redpanda, NATS).

• Time-series stores (ClickHouse, kdb+) and the Arrow/Parquet world.

• Infrastructure-as-code (Terraform) and CI/CD.

How we work

Small team, no layers, no theatre. You'll own things end to end and your work will be in front of paying clients quickly. We're in the office five days a week in London because the best version of this job happens in the same room, fast.

If the data's wrong, it's our problem before it's the client's. That standard is the job.

Location

Based in our London office