Design Lead.

The foundation had been an engineering-only organisation through testnet. With mainnet approaching, the leadership team had reached the conclusion that the next twelve months would be won or lost on whether the product surface — bridges, wallets, the developer-facing tools — felt trustworthy rather than threatening. The hire reported to the CEO and would own the design function from a blank sheet: hiring designers, setting the visual and interaction language, and shaping how the protocol presented itself to its first cohort of users.

The brief was specific about the kind of leader the foundation wanted. Not a pure brand designer; not a pure systems-and-components designer; certainly not a generalist. The foundation wanted someone who had operated inside the crypto-native UX problem space before — wallets, on-chain primitives, bridge flows — and who understood that a Bitcoin-aligned product had a different trust posture than an EVM-native one. The role carried a meaningful equity allocation and was scoped as a hands-on lead rather than a manager-only seat.

Senior design leadership inside crypto-native organisations is one of the more uneven benches in the industry. The visible names cluster in two groups: brand-led designers from consumer fintech who came into crypto in the last cycle, and product designers who grew up inside one of the larger Layer-1 foundations and have not worked outside that environment. Neither group is a clean fit for a Bitcoin-aligned protocol with a serious product surface to build. The movable population sits in a smaller third group — designers who have worked inside crypto wallets, custodians, or institutional-facing platforms and who carry both the trust posture and the systems discipline the brief required.

The lag in the market was that the Bitcoin-aligned cohort within that group is thin, and most of it is currently engaged inside a small number of companies — large custodians, established wallet teams, and a handful of newer Layer-2s. We knew going in that the search would need to reach into adjacent product categories where the trust posture was right and the protocol fluency could be built quickly. That widening was deliberate and was set with the CEO before any candidate conversation began.

The shortlist was composed around the trust-posture filter rather than the protocol-fluency one. We presented candidates who could be in the work within a quarter and who had the seniority to lead the function from day one.

• Designer from a tier-one crypto custodian who had led the redesign of the institutional product and carried strong systems discipline.
• Design lead from a non-custodial wallet team with a meaningful Bitcoin-side product surface and prior agency-side brand experience.
• Senior product designer from a stablecoin issuer who had owned the consumer-facing flows end-to-end.
• Independent design lead with a portfolio of crypto-native engagements and a track record of building first design hires inside protocol foundations.

The hire came from the second archetype — a design lead from a non-custodial wallet team whose Bitcoin-side work was already legible in the candidate's portfolio. The match on trust posture was immediate; the match on agency-side brand experience was the second factor the CEO was weighing. The decision turned on a working session — not an interview — in which the candidate walked through a redesign of one of the foundation's existing bridge flows. That session settled both sides.

The close landed in week six. The candidate had been considering a competing in-house role at a larger company and the foundation moved quickly to confirm scope, equity, and reporting line ahead of the final conversation. The trigger at the close was the autonomy to build the function from the ground up.

“The instinct on this brief was to widen on Bitcoin fluency and tighten on brand pedigree; we did the opposite. Bitcoin fluency turned out to be teachable — the candidate was inside the technical detail within weeks — while trust posture, taste, and the experience of building a design function from a blank sheet were not. The engagement was a reminder that for a first-design-leader hire, the filter is not the surface fluency the protocol team thinks they need. It is the underlying disposition that will shape every subsequent design hire and every interaction the product surface ever has.”

— Craig Oliver