Crypto didn’t emerge only to reinvent money or move databases onchain. It represents a deeper shift away from opaque systems and toward mechanisms that can be inspected, verified, and reasoned about directly: Code is public. Transactions settle predictably. Rules are enforced by software rather than by discretion.
Yet when it comes to hiring, many of the same builders designing these systems quietly forget these principles: Hiring in crypto often looks surprisingly traditional. School pedigree, brand name employers, and familiar institutions continue to dominate early screening.
These signals are convenient, but they’re fundamentally trust based. They ask decision makers to infer capability rather than verify it. So this post lays out how we can approach hiring in a way that’s both consistent with the crypto ethos and more likely to deliver better results.
The credential funnel
Traditional recruiting relies on heuristics. Degrees, past employers, and formal titles compress information, allowing teams to move quickly when time and attention are limited. Applied carefully, these heuristic shortcuts are not irrational. But over time, credential-driven hiring introduces distortions such as missing people who learned by building rather than following a formal path; overweighting institutional affiliation as a substitute for demonstrated skill; or pushing real proof of competence to much later in the process (or filtering it out entirely).
Crypto already produces verifiable signals
One of the defining characteristics of crypto — as with much open source — is that proof of one’s work is public by default. Builders do not need permission from centralized gatekeepers to participate, and they do not need third-party credentials to demonstrate competence. They only need to build.
As a result, talent working in the crypto industry generates a persistent and inspectable record of output, including:
- Public code repositories, commits, pull requests, and reviews
- Smart contracts deployed to testnets and mainnet with verifiable source
- Onchain activity visible through block explorers and protocol interfaces
- Contributions to hackathons, DAOs, and open source communities
A résumé is ultimately a claim. Technical work, by contrast, leaves evidence — so these signals stand on their own. They can be inspected directly, without relying on claims, endorsement, or educational/ institutional reputation. In crypto, one’s work does not require institutional backing to be visible. Output can be examined regardless of where someone studied or who previously employed them.
For technical roles in particular, showing one’s work can be more informative than pedigree. Furthermore, because these contributions accumulate over time —: commits remain inspectable, deployments continue to function, contribution histories deepen — many crypto builders demonstrate capability long before their résumé reflects it. Contributors distinguish themselves in hackathons before holding formal roles in foundations. Builders earn reputations inside DAOs without ever having titles.
Output comes first. Recognition follows.
When signals degrade
As verifiable work becomes more visible, it also becomes easier to imitate. Open-source contributions have long been a strong signal of technical ability. But as AI tooling improves, and incentives around public contribution increase, that signal has grown noisier. Merged pull requests alone are no longer sufficient.
Some contributors optimize for volume rather than substance: many small changes across many repositories, little follow-through, and limited progression toward harder problems. These contributions may be correct and occasionally accepted, but they do not reflect deep understanding or sustained ownership.
Despite these challenges, verification still works — but only when it evaluates the work itself. Code quality, problem selection, and contribution history over time matter more than isolated artifacts. High-signal builders show depth and continuity. Their work accumulates. Low-signal patterns are easy to spot once you know what to look for.
Toward a verification-first hiring model
To harness this talent more effectively, more builders can take a verification first approach to hiring by:
- Surfacing verifiable signals early — such as code quality, shipped systems, and contribution history – and instead treating résumés as context rather than as gates
- Incorporating onchain and open source data directly into hiring workflows — including treating these artifacts as first-class citizens in application tracking systems
- Embedding hiring process more directly in hackathons, DAOs, and open communities where talent already contributes.
Because a verification-first hiring model requires a shift in how teams attract talent. Rather than waiting for candidates to apply or relying on narrow filters like target companies or schools, founders and talent teams can proactively identify builders who are already producing high-quality work in public: core repositories, deployed systems, governance or design discussions, and infrastructure that others depend on.
For example, strong Solidity engineers can often be found through:
- Core protocol and tooling repositories on GitHub
- Public discussions and submissions in Ethereum Improvement Proposals (EIPs)
- Deployed contracts and on-chain activity visible through explorers like Etherscan
The same logic applies across ecosystems, whether you’re targeting Move-based chains, Rust engineers, ZK systems, or application-specific protocols. Hackathons offer especially high-signal prospects, because events like ETHGlobal and Solana Breakpoint attract builders who code and ship under pressure. Recruiters can then further reviewing these prospects’ projects and linked repositories.
Once your team has identified top talent, reference the specific commit, deployment, or design decision that led you to reach out. And selling the opportunity to the candidate is also more of a technical challenge, rather than delivering a generic job pitch.
This is not about replacing one set of credentials with another. It is about shifting emphasis from indirect proxies to direct evidence. Credentials and narratives still matter, but they are most effective when paired with observable output.
In an industry built around transparency and execution, crypto recruiting should begin with verification, so that “trust” serves as context rather than a prerequisite. It’s the industry principle of “don’t trust, verify,” but applied to finding great talent.
The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.
The views expressed here are those of the individual AH Capital Management, L.L.C. (“a16z”) personnel quoted and are not the views of a16z or its affiliates. Certain information contained in here has been obtained from third-party sources, including from portfolio companies of funds managed by a16z. While taken from sources believed to be reliable, a16z has not independently verified such information and makes no representations about the current or enduring accuracy of the information or its appropriateness for a given situation. In addition, this content may include third-party advertisements; a16z has not reviewed such advertisements and does not endorse any advertising content contained therein.
You should consult your own advisers as to those matters. References to any securities or digital assets are for illustrative purposes only, and do not constitute an investment recommendation or offer to provide investment advisory services. Furthermore, this content is not directed at nor intended for use by any investors or prospective investors, and may not under any circumstances be relied upon when making a decision to invest in any fund managed by a16z. (An offering to invest in an a16z fund will be made only by the private placement memorandum, subscription agreement, and other relevant documentation of any such fund and should be read in their entirety.) Any investments or portfolio companies mentioned, referred to, or described are not representative of all investments in vehicles managed by a16z, and there can be no assurance that the investments will be profitable or that other investments made in the future will have similar characteristics or results. A list of investments made by funds managed by Andreessen Horowitz (excluding investments for which the issuer has not provided permission for a16z to disclose publicly as well as unannounced investments in publicly traded digital assets) is available at https://a16z.com/investment-list/.
The content speaks only as of the date indicated. Any projections, estimates, forecasts, targets, prospects, and/or opinions expressed in these materials are subject to change without notice and may differ or be contrary to opinions expressed by others. Please see https://a16z.com/disclosures/ for additional important information.
Disclaimer:
- This article is reprinted from [a16zcrypto]. All copyrights belong to the original author [Ben Wu]. If there are objections to this reprint, please contact the Gate Learn team, and they will handle it promptly.
- Liability Disclaimer: The views and opinions expressed in this article are solely those of the author and do not constitute any investment advice.
- Translations of the article into other languages are done by the Gate Learn team. Unless mentioned, copying, distributing, or plagiarizing the translated articles is prohibited.
