We're partnering with Quant, a global leader in digital transformation and technology solutions, seeking a Head of Platform Reliability to join their team.

About Quant:

Almost all the money in the economy is commercial bank money. Deposits, sitting on bank balance sheets, moving through payment systems designed decades before anyone had a reason to make money programmable. Almost none of it moves on chain.

Quant builds the infrastructure that changes that. Our technology lets a bank issue, move and settle its own money on programmable rails while staying connected to the systems it already runs on. That constraint is the reason this has taken as long as it has.

Central banks and commercial banks have built on our platform, including work on the digital pound and the digital euro. We are now building our team in New York.

Head of Platform Reliability

Chain infrastructure carrying regulated money, in production, for institutions that hold it to the highest possible standard.

You would own its reliability. That means defining the service levels, setting the error budget policy, and holding the authority to stop a release when the budget is spent — a call that stands regardless of seniority.

You would build and lead the engineering team that runs it, on a rotation you design. We would rather you designed it properly than inherited something and patched it.

Chain platforms fail differently from the systems most reliability engineers have run. State is expensive, restarts are not a strategy, and a surprising amount of what looks like infrastructure turns out to be protocol behaviour. If that sounds interesting rather than daunting, we should talk.

You will need

• To have led site reliability or production engineering somewhere failure had consequences.
• To have run error budgets in practice — used one to stop a release, and defended the call
• Honest experience of continuous coverage — what burns people out, what does not, and the difference between a rotation on paper and one people can live with
• Kubernetes, Terraform, and an observability stack you have actually debugged, rather than configured.

Useful, not essential

• Blockchain nodes in production.
• Banking, payments, or somewhere else an auditor asked you to prove something.

There is more to this than we can put in an advertisement. If it sounds like your kind of problem, apply and we will tell you the rest on a call.