Research Engineer.

The foundation had carried its protocol work through engineering-led iteration, and was now formalising a research function to take on the harder open problems — bridge security proofs, cross-chain liveness, and the cryptographic primitives underlying the next major upgrade. The role reported to a newly appointed Head of Research and was the first hire underneath them. The brief was for a senior contributor who could run a research workstream end-to-end, not a junior researcher who needed supervision.

The hardest constraint was the dual profile. Pure researchers tend to operate in publication time and rarely ship production code. Pure engineers tend to optimise for shipping and avoid the open-ended exploration the work required. The foundation needed someone genuinely fluent in both modes — comfortable writing a security proof and comfortable landing the corresponding implementation in a protocol upgrade. Geography was flexible; the dual profile was not.

The cryptography-and-engineering bench is one of the smallest serious benches in the industry. It draws from a handful of academic groups, from the research arms of the larger Layer-1 foundations, and from a thin layer of senior individuals who have spent careers moving between the two modes. Most of the visible names are either tenured inside their current employer or actively turning down approaches. The movable population sits in two adjacent pools: researchers a few years into industry who are starting to feel the limits of a pure-research role, and engineers with serious cryptography credentials who have been doing implementation work and want to widen the surface.

Our read on the brief was that the lag was reputational, not financial. Senior research engineers are well compensated wherever they sit, and money rarely shifts the decision. What shifts the decision is the perceived quality of the research agenda and the credibility of the team they would join. The foundation had both, but neither was legible to the market — the Head of Research was new in seat, the upgrade roadmap was not yet public, and the strongest signals were inside private technical conversations. The bulk of our work was translating that legibility into the search.

We composed the shortlist around the dual-profile constraint and weighted toward candidates with a visible record of shipping research into production. We deliberately excluded candidates who looked strong on either side alone, even where the comp expectations would have been easier.

• Researcher with a cryptography PhD who had spent three years inside a Layer-1 foundation and shipped a consensus-layer upgrade end-to-end.
• Engineer from a zero-knowledge proving systems team with co-authorship on two papers and a track record of landing the corresponding implementations.
• Senior individual from a cryptography research lab moving toward applied work, with prior production experience inside a digital assets custodian.
• Researcher embedded inside an Ethereum-aligned R&D group who had quietly maintained Bitcoin-side work and was looking to consolidate.

The hire came from the second archetype — an engineer from a zero-knowledge proving systems team whose co-authored work had directly informed the foundation's roadmap. The match was unusually legible to both sides; the conversation moved quickly from credentials to research agenda within the first interview. The decision turned on the foundation's willingness to scope the first six months around a single open problem the candidate cared about, rather than a broader brief.

The close landed in week nine, slightly longer than is typical for our work, which reflected the candidate's existing equity vesting and a deliberately patient conversation about start date. Comp was not the lever — the lever was the research agenda and the latitude to set it.

“This brief reinforced something we already suspected about senior research hiring: the search is rarely about finding the candidate, and almost always about translating an internal research agenda into something a senior researcher can recognise as worth their next three years. The foundation had the substance; we spent meaningful time helping them make it legible. That work happened before any candidate conversation began, and it was the reason the close, when it came, was uncomplicated.”

— Craig Oliver