Chapter 01. Sourcing as a System
How to Use This Chapter
Read this chapter as a full system setup. If you have an urgent vacancy, do not try to fix everything at once: first compare your process with the table below, find one weak area, and move to
the relevant chapter.
Remember in One Phrase
Sourcing works when the team manages hypotheses, facts, and feedback — not simply when it
increases the number of profiles viewed.
| If Your Task Is | Go to Section | What You Get |
|---|---|---|
| Understand why search is not producing results | Diagnosing sourcing failure | A list of likely causes before blaming the market |
| Explain a systemic approach to the client | Random search vs. systemic sourcing | A short contrast for the conversation |
| Quickly outline a process for a new role | Process | The sequence of steps from brief to iteration |
Quick Chapter Map
1. First, separate random searching from systemic sourcing.
2. Then work through the 10-step process.
3. After that, check the failure diagnostics.
4. Finally, choose the next chapter based on the weakest area.
Minimal Start
In 30 minutes, gather the current role, the last 10–20 profiles reviewed, 3–5 client rejections,
and one recent message to a candidate. Mark where the process broke: brief, hypothesis, source,
message, evaluation, feedback, or metrics. Do not change everything at once: choose one area for
the next iteration.
Principle
Sourcing is market research, candidate searching, relevant communication, initial qualification,
and funnel management. It is not a list of links or a mass outreach.
Example
A recruiter spends three hours searching for a Senior Backend Engineer, saves 12 profiles, writes
to five people and receives no replies. Conclusion: "there are no candidates." A systemic sourcer
starts differently: clarifies that the role involves high-load transactional systems, finds donor
companies with a similar architecture, tests several job title groups, reviews open projects and
conferences, and builds messages around the candidate's relevant experience. The second
strategy may yield fewer profiles viewed, but more evidence.
Random Search vs. Systemic Sourcing
Random Search Systemic Sourcing
Starts with the tool Starts with the role and observable traits
Uses a single job title Builds variants of job titles and skills
Scrolls until exhausted Works in iterations
Evaluates "by eye" Uses evaluation maps and calibration
Says "there are no candidates" Shows the market map and funnel data
Sends generic messages Sends relevant, personalised messages
Works alone Closes the feedback loop with the client
Process
1. Define the business problem behind the vacancy.
2. Split requirements into must-haves, nice-to-haves, useful signals, and noise.
3. Translate requirements into observable profile traits.
4. Build 3–5 search hypotheses.
5. Map companies, adjacent talent pools, professional communities, and sources.
6. Test queries in short iterations and keep a log.
7. Evaluate profiles before first contact.
8. Write briefly, respectfully, and to the point.
9. Track responses, interested responses, qualified responses, and reasons for
rejection.
10. Review the funnel and strategy every week.
Sourcing Failure Diagnostics
The role remains vague.
A mandatory requirement cannot be seen in a profile.
The client rejects without specific reasons.
Search is limited to one job title or one source.
The Boolean query is too narrow or too broad.
Messages talk about the company, not the candidate's reason to respond.
Feedback takes more than 1–2 working days.
It is unclear who owns the candidate contact.
The team does not track the response rate and the qualified candidate rate.
The recruiter cannot explain the market through facts.
Common Mistake
Assuming a low response rate proves the absence of candidates. A low response rate can indicate
weak relevance, a poor message, an incorrect salary range, an overheated market, a weak
employer value proposition, or a slow process.
Self-Check
Can you explain in five sentences which market you tested, why it is relevant, what you found,
what changed after feedback, and what you will test next?
Key Takeaways / Where to Go Next
Take away the key maturity criterion: every team member should understand which hypothesis you
are testing and which fact will change the next step. If the problem starts before the search,
move to Chapter 2. If the role is clear but it is unclear whom to search for, move to Chapter 3.
