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

marsbitPublished on 2026-02-27Last updated on 2026-02-27

Abstract

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.

Related Questions

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.

Related Reads

Anthropic Ban Controversy, OpenAI's Hundred-Billion Financing Dispute: What Is the Overseas Crypto Circle Discussing Today?

In the past 24 hours, the crypto market has witnessed a range of discussions from macro trends to ecosystem-specific developments. Key topics include the controversy over AI and national security boundaries, debates around OpenAI's record $110 billion private fundraising, and the potential impact of AI tools on tech employment. Anthropic refused a Pentagon request to remove safety restrictions on autonomous weapons and mass surveillance in its models, leading to a terminated $200M government contract and a divided public response. OpenAI secured massive funding from investors like NVIDIA and Amazon, though its significant losses sparked concerns about a potential tech bubble. Block's 70% engineering team layoffs, attributed to AI efficiency gains, intensified debates on AI's effect on jobs. In ecosystem news, Ethereum community showed optimism as Vitalik Buterin outlined a roadmap with specific timelines for ZK-EVM integration by 2026-2027. Morpho outperformed AAVE, with some attributing it to simpler governance. Solana integrated with SoFi bank, enabling 13.7M users to hold SOL directly. Base ecosystem saw experiments with AI Agents for trading and social interactions. Other notable events included Paradigm's planned $1.5B fund expansion into AI and robotics, Bitwise's XRP ETF application, and OpenAI firing an employee for insider trading on prediction markets. Hyperliquid emerged as the only profitable Digital Asset Treasury project, and regulatory discussions around prediction markets continued.

marsbit34m ago

Anthropic Ban Controversy, OpenAI's Hundred-Billion Financing Dispute: What Is the Overseas Crypto Circle Discussing Today?

marsbit34m ago

Gas Fees and Transaction Security: Avoiding Asset Drainage by Malicious Contracts

Blockchain transactions require gas fee as fuel, but malicious actors exploit this mechanism to drain assets through deceptive practices. Common traps include: 1) Unlimited token approvals, where users grant open-ended access to smart contracts, enabling unauthorized transfers; 2) Gas fee hijacking, where attackers manipulate transaction parameters or embed infinite loops to force excessive gas payments; 3) Fake approvals/transactions via phishing sites that mimic legitimate dApps to steal assets. Key preventive measures: - Apply minimal approval principles, authorizing only necessary token amounts and revoking unused permissions. - Manually set gas limits and prices using wallet advanced settings, avoiding defaults during high network congestion. - Verify contract addresses, transaction details, and DApp authenticity before confirming any transaction. - Use separate wallets for daily interactions and large holdings to isolate risks. If compromised: - Immediately freeze the wallet and revoke all suspicious approvals. - Preserve evidence (TxID, contract addresses) and report to platforms. - Seek professional assistance for large losses—avoid paying "recovery fees" (common secondary scams). Recommended tools: Approval checkers (e.g., Revoke.cash), block explorers (Etherscan), and real-time alert systems. Stay vigilant by scrutinizing every transaction and rejecting unsolicited links.

marsbit2h ago

Gas Fees and Transaction Security: Avoiding Asset Drainage by Malicious Contracts

marsbit2h ago

Trading

Spot
Futures
活动图片