The crypto industry was built on transparency and verifiability, yet when it comes to hiring, many builders fall back on old habits: degrees, FAANG resumes, and prestigious titles still dominate early screening. In a new post, a16z calls for a fundamental change—moving from trust-based to verification-based hiring.
The Credential Funnel
Traditional recruiting relies on heuristics: diplomas, previous employers, official titles. These shortcuts save time, but over time they introduce blind spots. They overlook people who learn by doing rather than following a conventional path; they overvalue institutional pedigree and undervalue actual skills; and they postpone—or skip—direct proof of competence.
Crypto Already Has Verifiable Signals
In crypto, work output is public by default. Builders don't need permission from centralized gatekeepers or third-party certificates. They just build. The traces they leave include public code repositories, commit histories, pull requests, and code reviews; smart contracts deployed on testnets and mainnets with verified source code; on-chain activity viewable through block explorers; and contributions to hackathons, DAOs, and open-source communities. A resume is a claim; technical work leaves evidence. No matter where you studied or whom you worked for, your output can be inspected directly.
For technical roles, showing work speaks louder than background. Many builders earn their stripes at hackathons before getting a formal title; others build reputations in DAOs without ever holding an official role. Output first, recognition follows.
When Signals Get Noisy
As verifiable work becomes more prominent, imitation becomes easier. Open-source contributions, once a strong signal of ability, are now diluted by AI-assisted bots and incentive-driven quantity chasers. Some contributors make many small tweaks across multiple repos without ever tackling harder problems. Those changes may be correct but don't demonstrate deep understanding or sustained responsibility.
Verification still works—if you evaluate the work itself. Code quality, problem selection, and long-term contribution history matter more than isolated outputs. High-value builders show depth and continuity; low-quality ones become easy to spot once you know what to look for.
Toward a Verify-First Hiring Model
a16z recommends teams adopt a verify-first approach: surface verifiable signals early—prioritize code quality, live systems, and contribution history over resumes; integrate on-chain and open-source data into the hiring pipeline as primary materials; embed recruitment in real contexts—tap into hackathons, DAOs, and open-source communities where talent already gathers.
Instead of waiting for applications or filtering by target companies and elite schools, founders can actively seek builders who have already produced high-quality work in public: core repositories, deployed systems, governance discussions, or infrastructure that other teams depend on. For instance, top Solidity engineers are often found in core protocol repos on GitHub, participating in Ethereum Improvement Proposals, or deploying contracts visible on Etherscan. The same logic applies across ecosystems: Move-based chains, Rust engineering, zero-knowledge systems, and application protocols. Hackathons like ETHGlobal and Solana Breakpoint are proven talent pools full of builders who deliver under pressure.
This is not about replacing one set of credentials with another. It's about shifting focus from indirect proxies to direct evidence. Degrees and past employers still carry weight, but they work best when paired with observable output. In an industry built on transparency and execution, hiring should start with verification. Trust becomes context, not a prerequisite. That's the core creed: Don't trust, verify.