a16z: Don't just look at education and experience, find recruitment methods with more crypto spirit.

Author | Ben Wu, a16z

Editor | Chopper, Foresight News

Original link:

The emergence of cryptocurrency is not just about reshaping money or moving databases onto the chain. It represents a more profound transformation: shifting from opaque systems to mechanisms that are directly inspectable, verifiable, and inferable. Code is open and transparent, transaction settlement is predictable, and rules are enforced by non-subjective software.

But when it comes to hiring, many builders creating these systems quietly forget these principles. Recruitment in the crypto industry is often surprisingly traditional: academic background, big-company experience, endorsements from well-known institutions still dominate early screening.

While convenient, these signals are fundamentally trust-based. They let decision-makers infer ability rather than verify it. This article explains how we can hire in a way that is more aligned with the crypto ethos and more likely to yield great results.

The funnel of degrees and credentials

Traditional hiring relies on heuristics: degrees, former employers, official titles. These pieces of information are compressed into screening tags, allowing teams to make quick decisions when time and energy are limited. Used prudently, these shortcuts are not irrational.

But over time, a credential-oriented hiring approach introduces biases: for example, overlooking those who learn through practice rather than following established paths; overvaluing institutional backgrounds while ignoring actual skills; or postponing genuine proof of competence until later stages of the hiring process (or even ignoring it entirely).

Crypto already has verifiable signals

One of the core features of the crypto industry is that work output is public and inspectable by default. Builders do not need permission from centralized gatekeepers or third-party certificates to prove their ability; they just need to build things.

Therefore, talent in the crypto industry leaves a continuous, inspectable record of output, including:

Public code repositories, commits, pull requests, and code reviews

Smart contracts deployed on testnets and mainnets with source code verifiable

On-chain activity viewable through block explorers and protocol interfaces

Contributions to hackathons, DAOs, and open-source communities

Resumes are, in the end, just claims, while technical work leaves evidence. They can be inspected directly without relying on endorsements, recommendations, or institutional reputation.

In the crypto world, a person's work can be recognized without institutional backing. Regardless of where you graduated or who you worked for, output can be directly examined.

Especially for technical roles, demonstrating work is far more convincing than background. And these contributions accumulate: commits are permanently inspectable, deployments keep running, and contribution history deepens. Many crypto builders have proven themselves through ability long before their resumes reflect it.

Contributors stand out in hackathons before obtaining formal positions in foundations; builders earn reputation in DAOs without ever holding a title.

Output first, recognition follows.

When signals start to distort

As verifiable work becomes more visible, imitation becomes easier. Open-source contributions have long been a strong signal of technical ability, but with the proliferation of AI tools and increased incentives for public contributions, this signal has become noisy.

Some contributors pursue quantity over quality: making many small changes across multiple repositories without follow-up or progression to harder problems. These changes may be correct and occasionally accepted, but they do not demonstrate deep understanding or sustained responsibility.

Even facing these issues, verification remains effective, provided you genuinely evaluate the work itself. Code quality, problem selection, and long-term contribution history are more important than isolated achievements.

High-value builders demonstrate depth and continuity, with work accumulating over time. Once you know how to distinguish, low-value builders are easily seen through.

Moving toward a "verify-first" hiring model

To more efficiently discover talent, more teams can adopt a verify-first hiring approach:

Surface verifiable signals early: prioritize code quality, live systems, and contribution history; treat resumes as background references rather than gateways.

Integrate on-chain and open-source data directly into the hiring process: treat these achievements as important materials within your recruitment systems.

Embed hiring into real scenarios: engage deeply with hackathons, DAOs, and open-source communities; talent is already there.

"Verify-first" requires teams to change how they attract talent: instead of waiting for candidates to apply, or relying on narrow filters like target companies or prestigious schools; founders and hiring teams can proactively find builders who are already producing high-quality work in public: core repositories, deployed systems, governance or design discussions, and infrastructure that other teams depend on.

For example, great Solidity engineers typically appear at:

Core protocols and tool libraries on GitHub

Public discussions and submissions for Ethereum Improvement Proposals (EIPs)

Contract deployments and on-chain activity visible on explorers like Etherscan

This logic applies to all ecosystems, including Move-based chains, Rust engineers, zero-knowledge systems, and various application protocols. Hackathons are high-value talent pools; events like ETHGlobal and Solana Breakpoint gather builders who can write code and deliver under pressure.

Finally

This is not about replacing one set of credentials with another. It is about shifting focus from indirect evidence to direct evidence.

Education and credentials still matter, but they are most effective when combined with observable output. In an industry centered on transparency and execution, crypto hiring should start with verification. Let "trust" be the background, not the prerequisite.

This is the core tenet of the industry: Don't trust, verify. Now, apply it to finding the best talent.