Crypto Operations Lead

Must haves:

• Crypto-native operator. Deep, first-hand experience operating an institutional-grade crypto treasury under self-custody - built in DeFi protocol operations, in a CeFi crypto institution, in security engineering, or some combination of these. Crypto operations is your discipline, not a layer added to a TradFi treasury background
• Fluent with Gnosis Safe and Zodiac modules (Roles Modifier, Delay Modifier, Guards) and the operational discipline they require: permission scoping, allowlists, function-selector and parameter scoping, clear-signing, calldata verification. Able to reason about and anticipate failure modes in nested-Safe and module-based architectures
• Deep self-custody bias and an internalised crypto-OpSec mindset. Comfortable articulating the precise risks and rewards of self-custody vs. centralised custody. Treats exploits and key compromise as one-and-done events that must be anticipated and mitigated - owns the work of fixing the risks they identify, rather than flagging them for someone else to solve
• Comfortable operating treasury across a multi-entity, multi-jurisdiction structure - you understand how corporate structure and inter-entity boundaries constrain what can be done where, and design processes that respect those constraints
• Hands-on operator and builder - you design the framework and you run it. Writing runbooks, defining alert taxonomies, running drills and executing signings are yours to do. So is designing the framework they live inside
• Engineering rigour in what you build - documentation, runbooks, deployable infrastructure, tested recovery paths. The standard is that anything you ship can be picked up and operated by someone else without your involvement
• Strong bias toward automation and leveraging technology - the default response to a manual process is code or tooling, not a checklist. Crypto treasury operations at scale cannot be safely run by hand
• Proactive, structured, available. Comfortable with remote / async operations and with on-call expectations in true emergencies. Detail-oriented to the level a mis-typed allowlist destination demands.

Should haves:

• Track record executing liquidity moves and hedges at scale across both DeFi venues (DEXs, AMMs, lending, yield) and centralised counterparties (market makers, exchanges, OTC desks)
• Familiarity with the broader monitoring and response stack (Tenderly, Defender, Hypernative, Forta, Hexagate, Den, PagerDuty, or equivalents)
• Track record of designing and operating structured, auditable workflows in fast-moving environments, and bringing teams along while doing so.

Hiring process:

• Introduction call with the Talent team
• Interview with the CFO
• Task + Assessment (1-2 hours of work)
• Interview with Program Lead
• Interview Co-founder

Note: A background check might be required for this role. The steps may change along the way if we see it makes sense to adapt the interview stages, so please consider the above as a guideline.