Protocol Engineering Lead

Protocol Engineering 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.

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.

Protocol Engineering Lead

Most people who write smart contracts never have to keep them running afterward. This job is the other half.

Quant's protocol work — permissioned EVM, rollup architecture, contracts that issue and settle regulated money — is moving from build into production. We want the person who owns it there. The release train from written to audited to deployed. External audit coordination on every release, and the remediation that comes back from it. The decisions about what we take from upstream, what we hold, and where we diverge on purpose.

You would also be the person who explains why the chain did something nobody expected, to people who are not protocol engineers. That is a larger part of the job than it sounds.

The pool of people who can do this is small and we know it. If you are near the edge of it, apply and let us make that call.

You will need

• Deep Solidity and EVM experience, on contracts that held real value and went through external audit.
• Real understanding of rollup architecture. The mechanics rather than the vocabulary.
• To have maintained a fork of a large upstream codebase, and to know what that costs over time.
• To be able to explain chain behavior to reliability engineers, security engineers and eventually to a bank.

Useful, not essential

• Permissioned or enterprise EVM deployments.
• Settlement, payments or tokenization rather than consumer applications.
• Public contributions. We will read them.

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.