Don't Just Look at Credentials, Use Crypto Principles to Find Web3 Talent

marsbitPublicado em 2026-02-27Última atualização em 2026-02-27

Resumo

Crypto's core ethos champions transparency, verifiability, and trustless systems—yet hiring practices often remain traditional, over-relying on credentials like degrees or prestigious employers. This approach risks overlooking talented builders who prove themselves through action, not pedigree. The crypto space inherently produces verifiable work: public code repositories, on-chain deployments, open-source contributions, and participation in hackathons or DAOs. These outputs serve as direct evidence of skill, bypassing the need for institutional validation. Unlike resumes, which are merely claims, on-chain activity and code commits are permanent, publicly auditable records of capability. However, as AI tools and incentive structures evolve, some contributions may prioritize quantity over quality. It’s crucial to evaluate depth, consistency, and impact—not just activity. A "verify-first" hiring model shifts focus toward tangible proof: prioritize code quality, deployed systems, and contribution history early in the process. Engage talent where they already build—in open-source communities, at hackathons, and within protocol discussions. Credentials still matter, but they should complement—not replace—verifiable work. In a sector built on "don’t trust, verify," hiring should reflect that same principle: trust becomes the outcome, not the prerequisite.

Written by: Ben Wu, a16z

Compiled by: Chopper, Foresight News

The emergence of cryptocurrency is not just about reshaping money or moving databases on-chain. It represents a more profound transformation: from opaque systems to mechanisms that can be directly inspected, verified, and reasoned with. Code is open and transparent, transaction settlement is predictable, and rules are enforced by impartial software.

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

These signals, while convenient, are essentially trust-based. They allow decision-makers to infer ability rather than verify it. This article explains how we can approach hiring in a way that is more aligned with the spirit of crypto and more likely to yield excellent results.

The Funnel of Credentials and Pedigree

Traditional hiring relies on rules of thumb: degrees, previous employers, formal titles. This information is compressed into screening labels, allowing teams to make quick decisions when time and energy are limited. Used cautiously, these shortcuts are not irrational.

But over time, pedigree-based hiring introduces biases: for example, overlooking those who learn through practice rather than conventional paths; overemphasizing institutional background at the expense of actual skills; or delaying the proof of true ability until late in the hiring process (or even ignoring it entirely).

Crypto Already Has Verifiable Signals

A core feature of the crypto industry is that work output is public and verifiable by default. Builders don't need permission from centralized gatekeepers or third-party certificates to prove their ability; they just need to build.

Consequently, crypto talent leaves a persistent, inspectable trail of output, including:

  • Public code repositories, commit histories, pull requests, and code reviews
  • Smart contracts deployed to testnets and mainnets, with verifiable source code
  • On-chain activity viewable via block explorers and protocol interfaces
  • Contributions to hackathons, DAOs, and open-source communities

A resume is, after all, just a claim, while technical work leaves evidence. It can be directly inspected, without relying on endorsements, referrals, or school reputations.

In the crypto world, one's work can be recognized without institutional backing. No matter where you graduated from or who you worked for, the output can be directly examined.

Especially for technical roles, showing your work is far more persuasive than your background. And these contributions accumulate: commit histories are permanently viewable, deployments keep running, contribution histories deepen continuously. Many crypto builders prove their ability through their work long before their resumes reflect it.

Contributors stand out in hackathons before landing formal roles at foundations; builders earn reputations in DAOs without ever holding a title.

Output comes first, recognition follows.

When Signals Become Distorted

As verifiable work becomes more visible, imitation also gets 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 is becoming noisier.

Some contributors prioritize quantity over quality: making numerous minor changes across multiple repositories, lacking follow-through, and rarely advancing to more difficult problems. These changes might be correct and occasionally accepted, but they don't demonstrate deep understanding or sustained responsibility.

Even facing these issues, verification remains effective, but only if the work itself is truly evaluated. Code quality, choice of problems, and long-term contribution history are more important than isolated achievements.

High-value builders show depth and continuity, with work that accumulates over time. Once you know how to discern this, low-value builders are easy to spot.

Towards a "Verification-First" Hiring Model

To unearth talent more effectively, more teams can adopt a verification-first approach to hiring:

  • Surface verifiable signals early: Prioritize code quality, live systems, and contribution history, treating the resume as background context, not a gate.
  • Integrate on-chain and open-source data directly into the hiring process: Treat these outputs as key materials in recruitment systems.
  • Embed recruiting in real contexts: Dive into hackathons, DAOs, and open-source communities where the talent already is.

"Verification-first" requires teams to change how they attract talent: no longer waiting for applicants or relying on narrow filters like target companies or elite schools; founders and hiring teams can proactively identify builders who are already producing high-quality work in public: core repositories, deployed systems, governance or design discussions, and infrastructure other teams rely on.

For example, excellent Solidity engineers often appear in:

  • Core protocol and tooling repositories on GitHub
  • Public discussions and submissions for Ethereum Improvement Proposals (EIPs)
  • Contract deployments and on-chain activity viewable on explorers like Etherscan

This logic applies to all ecosystems, including Move-based blockchains, 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 code and deliver under pressure.

Finally

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

Credentials and pedigree 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 context, not the premise.

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

Perguntas relacionadas

QWhat is the core argument of the article regarding hiring in the Web3 space?

AThe article argues that the traditional hiring approach, which relies heavily on credentials like academic degrees and prior company affiliations, is misaligned with the core principles of crypto. Instead, it advocates for a 'verify-first' model that prioritizes directly observable and verifiable work outputs, such as public code repositories, on-chain activity, and contributions to open-source communities, over indirect trust-based signals.

QAccording to the article, what are some examples of verifiable signals that crypto builders leave behind?

AExamples of verifiable signals include public code repositories, commit histories, and pull requests; smart contracts deployed to testnets and mainnets with verifiable source code; on-chain activity viewable through block explorers and protocol interfaces; and contributions to hackathons, DAOs, and open-source communities.

QWhy does the article suggest that the signal from open-source contributions might be becoming 'noisy'?

AThe signal is becoming noisy due to the proliferation of AI tools that can generate code and the increased incentives for making public contributions. This can lead to contributors prioritizing quantity over quality—making many small, superficial changes across multiple repositories without deep understanding, long-term follow-through, or tackling more complex problems.

QWhat practical steps does the article recommend for adopting a 'verify-first' hiring model?

AThe article recommends: prioritizing verifiable signals like code quality and deployment history early in the process; directly incorporating on-chain and open-source data into the hiring workflow; and embedding the recruitment process into real-world scenarios like hackathons, DAOs, and open-source communities where talent is already actively building and contributing.

QWhat is the fundamental crypto ethos that the article says should be applied to the hiring process?

AThe fundamental crypto ethos that should be applied to hiring is 'Don't trust, verify.' This means shifting the focus from relying on trust-based credentials and assumptions to a process that begins with the direct verification of a candidate's skills and accomplishments through their publicly available work.

Leituras Relacionadas

Misjudged A-Shares: Resilience, Expectations, and Confidence

China's A-share market recently faced selling pressure, especially in tech sectors, initially triggered by a global tech sell-off that began in South Korea. However, the article argues this is a case of "mistaken injury" and highlights the market's underlying resilience. This resilience stems from three main pillars: **1) Tech Sector Fundamentals:** Unlike Korea's market dominated by a few memory chip stocks, China's tech sector is diversified across computing, communications, electronics, and semiconductors, supported by dual narratives of global AI supply chains and domestic substitution. Core areas like optical modules and fiber optics continue to show strong earnings growth. **2) "National Team" Support:** State-backed institutions and large corporations have made significant market purchases and announced buybacks, providing liquidity and signaling confidence. This is seen as a stabilizing policy signal, often associated with market bottoms. **3) Broader Market Pillars:** Other major sectors are showing endogenous recovery momentum. Consumer stocks benefit from stabilizing CPI and signs of sector recovery (e.g., liquor price hikes). Cyclical sectors like aluminum have high earnings, potential price increases due to tight supply, and low valuations. The financial sector offers stable dividends and low valuations. The conclusion is that the sell-off was driven by external contagion, not a collapse in fundamentals. With strong policy support and recovering momentum across key sectors, the A-share market possesses the toughness to regain stability.

marsbitHá 24m

Misjudged A-Shares: Resilience, Expectations, and Confidence

marsbitHá 24m

The Clarity Act's Journey Through Congress: The Thorny Path of Bipartisan Compromise in the U.S.

The U.S. Congress is struggling to advance the crypto market structure bill known as the Clarity Act, with bipartisan compromise proving difficult. Key hurdles include unresolved disputes over "yield" products and, more critically, the inclusion of strong ethics provisions for elected officials—a non-negotiable demand for many Democrats. While a compromise on yield was reached in May, securing only limited Democratic support in committee, the separate Senate Agriculture Committee version later passed with no Democratic votes due to the ethics impasse. As Republicans push for a full Senate vote in July, demands for ethics rules have expanded, and other contentious issues like developer protections and concerns from law enforcement and large banks further complicate negotiations. Despite consensus on the need for legislation, the path forward is unclear. Recent discussions between senators and White House officials aim to find acceptable ethics language. Some lawmakers question whether a compromise text can garner enough bipartisan support, with one Democrat stating the current proposal lacks the strong ethics provisions required for their vote. Potential short-term goals for the crypto community include symbolic Senate action before the August recess, a longer-term aim for passage by 2026, or establishing a detailed framework that addresses ethics and other compromises. The process remains arduous, relying on the traditional, vote-by-vote effort to build bipartisan support.

marsbitHá 43m

The Clarity Act's Journey Through Congress: The Thorny Path of Bipartisan Compromise in the U.S.

marsbitHá 43m

Are Kalshi and Polymarket Founders at Odds? This Business Rivalry Is More Brutal Than You Think

"The Rivalry Between Kalshi and Polymarket Founders Turns Bitter and Litigious" The intense feud between Tarek Mansour, CEO of Kalshi, and Shayne Coplan, founder of Polymarket, has escalated far beyond typical business competition into personal animosity and regulatory battles. Both lead billion-dollar prediction market platforms, but their approaches differ sharply. Kalshi positions itself as the compliant operator, securing U.S. regulatory approval before launching. In contrast, Polymarket initially operated offshore, allowing U.S. users to access its platform via VPN, which drew regulatory scrutiny. The conflict reached a peak in November 2024 when FBI agents raided Coplan's New York apartment. While Coplan publicly blamed political motives, his team privately suspected Kalshi was involved. According to sources, Kalshi's lawyers had previously reported Polymarket's operations to federal prosecutors, highlighting its accessibility to U.S. users despite a ban. This incident fueled mutual accusations and underhanded tactics, including social media smear campaigns and attempts to sabotage each other's major business deals. Their rivalry also played out in Washington, influencing regulatory debates. Kalshi actively lobbied against Polymarket's practices, framing them as illegal and unethical. Polymarket, after facing a CFTC fine and investigation, later acquired a licensed U.S. firm to launch a domestic app, regaining a foothold. Despite the hostility, both companies have seen massive growth, with combined trading volumes soaring. However, increased regulatory scrutiny, particularly around insider trading on Polymarket's platform, continues to pose challenges. The founders' deep-seated mutual disdain ensures their battle for market dominance remains as much a personal vendetta as a commercial one.

marsbitHá 52m

Are Kalshi and Polymarket Founders at Odds? This Business Rivalry Is More Brutal Than You Think

marsbitHá 52m

Trading

Spot
活动图片