Head of Platform Reliability

Cielo Talent; New York (NY); On-site; USD 180,000 - 240,000; Full time

Job summary

Quant is seeking a Head of Platform Reliability in New York to own the reliability of a regulated money chain infrastructure in production. You will define service levels, set the error budget policy, and hold authority to stop a release when the budget is spent.

You will build and lead the team that runs it, on a rotation you design, aiming for proper design over patchwork fixes and a deep understanding of where reliability issues originate.

Qualifications

• Led site reliability or production engineering where failure had consequences.
• Ran error budgets in practice and defended release decisions.
• Managed honest continuous coverage with sustainable rotations.
• Experience debugging and optimizing Kubernetes, Terraform and observability tooling.

Responsibilities

• Own the reliability of the platform and define service levels.
• Set the error budget policy and have authority to stop a release when budget is spent.
• Build and lead the engineering team that runs the platform, on a designed rotation.

Skills

Site reliability leadership

Error budget management

Rotation design

Production engineering

Tools

Kubernetes

Terraform

Observability stack

Job description

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

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.

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.