Platform Reliability Technical Lead
We're partnering with Quant, a global leader in digital transformation and technology solutions, seeking a Platform Reliability Technical Lead 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.
Platform Reliability Technical Lead
When the engineer on shift cannot work out why the chain is doing what it is doing, they call you.
This is the deepest technical seat on the team. Final escalation across the whole production estate, and the person who sets how the team works: runbooks that are current, alerting that fires on something real, postmortems that change something.
You would work closely with the protocol engineers, because the hard problems here tend to be protocol behavior rather than infrastructure, and they get solved faster when both sides are on the same call.
Very little of what you find in production will have a precedent you can look up. This role exists so that someone excellent can stay technical rather than move into management.
You will need
- Serious depth in reliability or production engineering. You are already the person others escalate to.
- Kubernetes, Terraform and Helm at the level where you debug them.
- Distributed systems where state matters and restarting is not a strategy.
- To write things down. If the only record of how the platform works is in your head, nothing has been fixed.
Useful, not essential
- Blockchain node operations.
- You have read consensus client source to explain a production behavior.
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.