Most recruitment teams waste 60%+ of their sourcing hours on candidates who were never going to convert. After placing talent across DeFi protocols, L2s, AI infra companies, and crypto exchanges, here are the patterns we see killing pipelines:

1. Filtering for Exact Token/Chain Experience

A Solidity dev who shipped on Arbitrum can ship on Base. A Rust engineer from a TradFi HFT desk can build on Solana. Yet most JDs demand "3+ years in [specific chain]" — eliminating 80% of qualified candidates who'd ramp in weeks.

Fix: Filter for transferable primitives — smart contract design patterns, consensus knowledge, zero-knowledge math — not specific chain experience.

2. Posting on LinkedIn and Waiting

The best Web3 talent isn't job-seeking on LinkedIn. They're in Telegram groups, contributing to GitHub repos, speaking at ETH events, and lurking in governance forums. If your sourcing strategy is "post and pray," you're fishing in the wrong pond.

Fix: Source where builders actually are — protocol Discord servers, Gitcoin contributors, Devfolio hackathon winners, and niche Twitter/X communities.

3. Ignoring Time Zone as a Dealbreaker

Remote-first doesn't mean timezone-agnostic. A smart contract auditor in UTC+8 reviewing PRs from a team in UTC-5 creates 16-hour feedback loops. We've seen this single issue tank eng velocity on multiple protocol teams.

Fix: Define your collaboration window upfront (minimum 4-hour overlap) and source within that band.

4. Comp Benchmarking Against Web2

AI/ML engineers and protocol developers operate in a different comp market. If you're benchmarking against FAANG base salaries without factoring in token vesting, protocol incentives, or the premium for regulatory uncertainty, your offers will get ghosted.

Fix: Benchmark against recent placements at comparable protocols and stages. Comp in crypto moves quarterly, not annually.

5. No Technical Screen Before the Hiring Manager

Sending unvetted resumes to your CTO or Head of Engineering burns trust fast. After 3-4 bad candidates, they stop engaging with your pipeline entirely.

Fix: Run a 30-minute technical pre-screen covering architecture decisions, past project depth, and basic domain knowledge before any candidate reaches the hiring manager.

---

These aren't edge cases — they're the norm. If your pipeline is slow or your offer-accept rate is under 50%, at least one of these is the reason.

We built Wen Hire specifically to solve this. We source, pre-screen, and shortlist so your team only talks to candidates worth their time.