Some roles require different sourcing logic.
Kristina Golovko
MindDesign
The rare role system
Scarcity
Acknowledge the real market size
Signal
Define what rare looks like
Mapping
Find where scarcity concentrates
Engagement
Build trust before the ask
Rare roles require a longer engagement horizon. The search begins before the vacancy is open.
Why this matters
Not all scarcity is search failure. Some roles exist at the intersection of very specific technical depth and very limited market supply. Protocol engineers, quantum systems researchers, rare language runtime specialists, firmware security researchers — the global pool is sometimes measured in hundreds, not thousands.
For these roles, the standard hiring timeline is wrong. The standard outreach is wrong. The standard evaluation is wrong. What works for abundant talent markets creates friction in scarce ones.
Hiring for impossible roles requires acknowledging the reality of the market, building relationships before the vacancy opens, and treating the search as a long-horizon engagement — not a 6-week sprint.
Founder reality
Before labelling a role 'impossible', pressure-test the assumptions:
Have we mapped the actual global supply of this expertise — or are we estimating?
Are we requiring all qualifications simultaneously, or could some be developed on the job?
Have we engaged the communities where this expertise concentrates — or only searched mainstream channels?
Are we willing to consider adjacent expertise and train into the specific gap?
Is the compensation and opportunity competitive for this specific talent pool?
Some roles are genuinely rare. Others feel rare because the search hasn't reached the right markets yet.
The system
These stages apply when standard search logic has been exhausted and the role requires genuine precision.
Scarcity mapping — understand the actual size and shape of the talent pool
Before investing in an extended search, size the market. How many people worldwide have the specific combination of skills required? Where are they? What are they working on? This prevents both premature resignation ('there's no one') and poorly directed search effort.
Signal redefinition — broaden signal to include adjacent expertise
When the perfect profile doesn't exist at scale, define adjacent signals. A compiler engineer without direct experience in the exact language may have transferable depth. A researcher with adjacent domain expertise may ramp faster than the search timeline. Signal redefinition expands the effective market.
Ecosystem engagement — enter the community before you need someone
Rare talent communities are small. Being known in them — through technical publishing, conference participation, open-source contribution, or community support — creates warm sourcing that cold outreach cannot replicate. The best hires in rare domains come from relationship, not search.
Long-horizon engagement — build the relationship before the vacancy
Impossible roles benefit from a 6–12 month engagement horizon. Identify the 10–15 people globally who are most qualified. Begin low-pressure relationship building now. When a vacancy opens, the outreach reaches people who already know your company — which fundamentally changes the response rate.
Common mistakes
01
Expecting a rare role to fill in standard timelines
A role that targets the top 200 people globally will take longer than a role targeting a pool of 20,000. Planning timelines without acknowledging scarcity produces missed deadlines and unnecessary pressure.
02
Cold outreach to people who are deeply embedded in small communities
In rare talent markets, reputation travels. A generic cold message from an unknown company in a tight community creates a negative signal. Enter the community before you recruit from it.
03
Over-specifying requirements
Impossible roles often become possible when one or two requirements are adjusted. Distinguish must-haves from preferences. Every unnecessary requirement reduces the pool.
04
Competing on compensation alone
Rare experts are often motivated by problem quality, peer quality, and technical challenge — not exclusively salary. The opportunity must be compelling on its technical merits for this cohort.
Example scenario
A distributed systems company, Series A. Hiring a principal engineer specialising in Byzantine fault-tolerant consensus protocols. Estimated global pool of practitioners: under 500.
The 9-month approach
Month 1–3: Talent map built. 47 people identified globally with direct protocol expertise. 12 at target seniority.
Month 3–6: CEO published two technical pieces on the company's consensus work. Shared in relevant academic and open-source communities. Three of the 12 targets engaged organically.
Month 6–8: Informal conversations initiated — not recruitment, but technical exchange. Two became warm contacts.
Month 8–9: Role formally opened. Warm contacts prioritised. One accepted offer.
The outcome
Hire made without competitive bidding. Candidate joined partly because of the technical credibility the company had demonstrated over the preceding months. Total time from map-build to accepted offer: 9 months. Time from formal open to accepted offer: 6 weeks.
Impossible roles require a longer clock — not a louder search.
The companies that consistently hire rare talent do so because they invest in community presence and relationship building before the vacancy opens. By the time the role exists, the candidates already know who you are.
Related thinking
Continue reading
Passive Candidate Psychology →