Strong hiring starts before the vacancy exists.
Kristina Golovko
MindDesign
The talent pool system
Signal
Identify strong people proactively
Relationship
Build connection before urgency
Timing
Engage at natural transition points
Opportunity
Convert relationship to hire
A talent pool is not a database. It's an ongoing relationship with people you haven't hired yet.
Why this matters
A talent pool that works is one where candidates remember you positively when a role opens — because you've had a real interaction with them before that moment. A talent pool that doesn't work is a spreadsheet of LinkedIn profiles that get cold outreach when a role opens.
The difference between these two is the relationship layer. Strong candidates who have had a genuine, relevant conversation with your company — even one that didn't lead to a role — are far more likely to engage when something relevant opens.
Building a talent pool that actually works requires proactive relationship investment before urgency exists. It's a longer horizon than most companies are willing to maintain. And it produces a consistent sourcing advantage over companies that only look when they need someone.
Founder reality
Assess your current talent pool with these questions:
When a strong candidate declines or is passed over, does a relationship continue?
Do we have any candidates in our pipeline who are not actively interviewing?
Can we reach out to people we spoke to 12 months ago — and would they respond positively?
Are we identifying strong candidates before we have open roles for them?
When a role opens, do we have warm profiles to reach immediately — or do we start from scratch?
If most answers are 'no' — every search begins from zero. Talent pools compound over time only if the relationship layer is maintained.
The system
Build the pool as a relationship system. Review and refresh quarterly.
Signal — identify strong profiles before a role exists
Talent pool building is proactive. When a strong profile appears during sourcing for a different role, in a community, or via a referral — document it. Add context: what made them interesting, what role they'd fit, what their current situation seems to be. The pool grows from attention, not from urgency.
Relationship — create a genuine interaction, not a pitch
The first contact with a pool candidate is not recruitment. It's a relevant, non-pressured conversation: sharing a resource, asking a question about their domain, inviting feedback on a technical approach. This creates a positive association that cold outreach during a vacancy cannot replicate.
Timing — monitor for natural transition signals
Passive candidates become more open at predictable moments: company change, role change, new funding at their employer, public signals of professional transition. Tools and networks surface these. When a signal appears for a pool candidate, the timing window for re-engagement opens.
Opportunity — convert pool relationship to hiring conversation
When a role opens that matches a pool candidate, the outreach is fundamentally different: 'We spoke about distributed tracing 8 months ago — I've been thinking of you for something we're now building.' The candidate remembers the company. The conversation starts warm.
Common mistakes
01
Treating the pool as a one-time build
A talent pool requires ongoing maintenance. Profiles become stale. Candidates move. Relationships cool. Review and re-engage the pool quarterly — not only when a role opens.
02
Adding everyone to the pool
A pool with low signal quality is just a large list. Only add candidates who demonstrated genuine fit indicators. Quality over volume — the pool should be curated, not comprehensive.
03
No CRM or tracking system for pool relationships
Relationship history that lives in someone's memory is fragile. When the person managing the pool changes, the pool disappears. Document interactions, context, and timing notes in a system.
04
Going silent and reappearing only with an ask
Reaching out to a pool candidate only when you have a role signals that the relationship is transactional. Occasional non-recruitment contact — sharing a relevant piece, asking a question — maintains the relationship between vacancy cycles.
Example scenario
A deep-tech infrastructure company, growing from 40 to 90 people over 18 months. Built a talent pool 12 months before their major scaling phase.
How the pool was built
Every strong candidate who didn't join (wrong timing, no open role, passed over for another) was added to the pool with context.
Quarterly: head of talent reviewed the pool and sent 5–10 relevant, non-recruitment outreach messages.
Sourcing team added 3–5 new strong profiles monthly, even without open roles.
Pool grew to 85 profiles over 12 months — all with documented relationship history.
During the scaling phase
When 12 roles opened in 6 months, the pool was the first sourcing channel activated. 40% of offers were extended to pool candidates — people who had been in contact with the company for 3–12 months before joining.
The outcome
Average time-to-hire for pool candidates: 4.5 weeks. For new searches: 9 weeks. Offer acceptance rate for pool candidates: 84%. For new searches: 61%.
The best time to build a talent pool was 12 months ago.
The second best time is now. Every strong candidate interaction that doesn't lead to an immediate hire is an opportunity to begin a relationship that will — when the timing is right.
Related thinking
Precision Sourcing
Passive Candidate Psychology
Strong people are rarely actively looking.
Precision Sourcing
Global Talent Without Chaos
International hiring needs systems, not improvisation.
Precision Sourcing
How to Hire for Impossible Roles
Some roles require different sourcing logic.
Continue reading
Signals Before CVs →