How I find people
most recruiters never see.
This document explains how I actually work — not the version that fits a job description, but the operational system I've built over four years of hiring in some of the scarcest technical talent markets in the world: cryptography, ZK protocol engineering, DeFi infrastructure, and now AI.
Recruiting is a
signal problem.
Most recruiting processes are optimized for volume. More outreach, more applications, more pipeline. That logic works when the talent pool is large and the role is well-understood. It fails completely when you're hiring a ZK protocol engineer, a cryptographer, or a backend engineer who has built trading infrastructure on open protocols.
In those markets, the best people aren't on LinkedIn. They don't apply to jobs. They're skeptical of recruiters. And they can tell within two sentences whether you understand what they actually do.
The job isn't to run a better process. It's to develop better signal — about the role, the candidate, and the ecosystem — before a single message gets sent.
How a search
actually runs.
This is the sequence I run for every new search, regardless of role type. The specifics change. The structure doesn't.
Embedded kickoff — not a brief
I don't start with a job description. I start by understanding the team's failure modes: who didn't work out, why it took so long to figure that out, what was compromised on in previous hires, and what the non-negotiables actually are versus what sounds good on paper.
Ecosystem mapping before sourcing
Before opening any sourcing tool, I map where the target population actually lives — GitHub organizations, research forums, Discord communities, conference speaker lists, event attendee networks, open source contribution graphs. The sourcing strategy follows from this map.
Signal definition — what does good actually look like?
I work with the hiring team to define what genuine competence looks like in this specific role. Not generic seniority signals, but role-specific indicators: contribution patterns, problem types, depth of open source work. This defines the sourcing filter before I look at a single profile.
Targeted outreach — specific, not scaled
Every outreach message references something concrete about the person's work. This is slower than mass outreach and produces dramatically higher response rates — consistently 85–90% across searches in skeptical-of-recruiters talent pools.
Recruiter screen — designed for the role
I build custom screening questions for each search that filter on genuine depth before engineering time is spent. The goal is to make the process respectful of the candidate's expertise while giving the team high-confidence signal before the technical loop begins.
Pipeline management and stakeholder rhythm
Structured weekly syncs, pipeline health tracked against agreed metrics, and problems flagged early. If a search is going to take longer than expected, I say so at week three, not week ten.
Matter Labs (zkSync)
19 specialist roles.
zkSync is one of the leading Ethereum Layer 2 scaling solutions, built on zero-knowledge proofs. Hiring for this team meant finding people who understood ZK cryptography, distributed systems performance, and protocol design at a level where the global candidate pool is measured in hundreds, not thousands.
I built sourcing infrastructure around where this community actually lives: Ethereum Magicians forum, ZK-focused GitHub organizations, academic paper authorship on ZK proof systems, conference speaker lists (ZKSummit, ZKProof), and contribution graphs on open source cryptography libraries.
Beyond sourcing channels, the screening process needed to change. I designed recruiter-led screening questions calibrated to algorithmic depth — questions I could ask in a first call that gave the engineering team confidence before they invested interview time:
✓ Strong signal: Instant recall, correct ordering (log n → √n → n), often extends into follow-up reasoning unprompted
✗ Weak signal: Correct answer but slow, uncertain on ordering, can't explain the underlying logic
0x / Matcha —
embedded from day one.
0x builds open infrastructure for decentralised exchange. Matcha is their consumer-facing DEX aggregator. The roles were technically specific in ways a standard job description couldn't capture: backend engineers who understood trading protocol internals, search infrastructure outside the Google ecosystem, and mobile engineers who had shipped real Web3 trading products.
Active interview processes across 7 concurrent engineering roles within weeks of starting. ~85–90% outbound response rate. 40–60% conversion from outreach to interview. All pipelines built from zero.
Where the talent
actually lives.
When standard channels don't work, the question is: where does this community actually congregate? The answer is different for every technical domain. Here's the ecosystem map I've built across the roles I hire for most.
- Ethereum Magicians
- ethresear.ch
- ZKSummit speakers
- ZKProof community
- Academic ZK papers
- privacy-scaling-explorations
- L2 ecosystem Discords
- Protocol contributors (Uniswap, 0x, Aave)
- DEX tooling GitHub orgs
- Web3 trading Discord servers
- DeFi-focused hackathons
- OpenSearch / ES community
- ETHGlobal winners
- On-chain contributor history
- Hugging Face contributors
- ArXiv authors (applied ML)
- Inference / training infra GitHub
- Papers With Code leaderboards
- NeurIPS / ICML attendees
- ML engineering Discords
- AI Twitter / X clusters
The ecosystem map comes before the sourcing tool. Understanding which community to enter — and how to enter it credibly — is most of the work.
Nine tools.
Built to find signal.
The manual version of ecosystem sourcing works. The AI-assisted version works at a different scale and with more precision. I've built a suite of recruiting intelligence tools that layer AI on top of four years of technical ecosystem knowledge — eliminating low-signal work so the high-judgment work gets more time.
in AI or Web3?
I'm looking for founding or first-recruiter roles where the work is building the system, not just filling the pipeline. AI infrastructure, DeFi, and frontier technical teams.