Phenotype vs. Genotype Evaluation
Hire and back people for who they fundamentally are, not the sector experience on their resume.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 75%
When evaluating potential partners or founders, it's tempting to pattern-match on visible experience — someone worked in crypto, so they must be the crypto hire. Benchmark calls this confusing 'phenotype' (the expressed, visible trait) with 'genotype' (the underlying trait that actually predicts success). The firm's own history shows partners succeeding wildly outside their apparent specialty — consumer investors becoming enterprise investors, and vice versa — because what actually matters is an underlying genotype of roving curiosity and wide dynamic range, not a resume match to the hot sector of the moment. The model's mechanism is to actively resist lowering selectivity just because someone's background superficially fits an area.
Origin
Extracted from Acquired
Core principles
- 01Visible experience (phenotype) is not the same as underlying capability (genotype)
- 02Curiosity and dynamic range predict success better than sector tenure
- 03Let entrepreneurs and markets pull expertise, don't staff to a thesis
- 04Resist lowering the bar for a resume match
- 05Generalists can become deep specialists quickly when the genotype is right
How to run it
- 1
Separate the two signals
Explicitly distinguish what a candidate has done (phenotype) from who they fundamentally are (genotype: curiosity, judgment, adaptability).
- 2
Notice the bias
Catch yourself getting excited purely because someone's resume says 'crypto expert' or 'AI expert' during a hot cycle.
Watch out This mistake reportedly happens about once a week even inside an experienced firm — don't assume you're immune.
- 3
Test for wide dynamic range
Look for evidence the person has moved fluidly across unrelated domains and built real relationships each time.
- 4
Let expertise be pulled, not pushed
Allow genuine sector depth to develop naturally from where founders and markets are going, rather than hiring to pre-fill a thesis.
- 5
Re-apply the test over time
Periodically check whether current team composition reflects real genotype fit or just accumulated phenotype coincidences.
In the wild
In 2014 the partnership was almost entirely consumer investors (Twitter, Uber, Snapchat, Instagram). A new partner with enterprise exposure joined not because of a deliberate enterprise thesis, but because the first deal that walked in the door was an enterprise company.
→ Over years the firm's visible composition shifted heavily toward enterprise, entirely driven by where founders and markets led, not a hiring plan.
A partner led a major crypto-adjacent investment despite having little prior crypto expertise at the time.
→ The investment succeeded because of underlying judgment and curiosity, not pre-existing sector credentials.
Common mistakes
Hiring for resume pattern-match
Choosing someone because they 'have experience in areas X, Y, or Z' mistakes phenotype for genotype and can quietly lower selectivity.
Building a thesis-driven team
Staffing to a pre-set sector thesis contradicts the generalist, curiosity-first genotype that actually predicts success.
Assuming sector tenure equals insight
Long experience in a market doesn't guarantee the underlying judgment that makes someone valuable.
Is it for you?
Best for
Leaders hiring for judgment-heavy roles where domain can shift quickly (investing, product, strategy).
Not ideal for
Highly regulated or technical roles where specific credentialed expertise is a hard requirement.
From the transcript
“we make a mistake repeatedly probably once a week in the portfolio of confusing phenotype and genotype meaning we hire people because of the phenotype…”
“there's no great venture capitalist in my view that isn't aspiring to be wide dynamic range”
From the episode
Benchmark Part II: The Dinner