Stand out for this role — generate a tailored resume and cover letter in about a minute.
Quant seeks a Protocol Engineering Lead to own the production readiness of smart contracts and rollup architecture. You will coordinate external audits, manage the release train from development to deployment, and decide on upstream integration versus divergence, while communicating chain behaviour to reliability and security teams.
The role requires deep Solidity/EVM experience, experience with forks of large upstream codebases, and the ability to explain complex chain events to non-technical
We're partnering withQuant, a global leader in digital transformation and technology solutions, seeking aPlatform Reliability Technical Leadto 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.
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.
By clicking the link above or any third-party link within this posting, you are leaving this site and going to a third-party website where the third-party website's terms and privacy policy apply