Four months ago you opened a req for a senior engineer. Since then you've added a second agency, turned on a job board you'd never used, and told your recruiter to "cast a wider net." The pipeline looks busier. The role is still open.
Here's the uncomfortable diagnosis: this was never a volume problem. It's a pool problem, and no amount of extra sourcing fixes a pool that's the wrong shape.
Why more channels don't help
Every sourcing channel you're likely using, LinkedIn Recruiter, referrals, a new agency, a job board, is searching the same finite set of people: senior engineers in your metro area or willing to relocate to it. That set doesn't grow when you add a channel. You're just running more queries against the same small population, most of whom are already employed, already mid-interview somewhere else, or simply not interested in uprooting their life for your offer.
Add up the constraints on a truly senior hire: 8+ years, strong system design judgment, the ability to make calls without hand-holding, and willingness to move for a comp package that competes with what they already have. In most US metros, that's a tiny slice of people. You are not short on sourcing effort. You are short on candidates who exist in the pool you've drawn.
The part nobody says out loud
A fourth channel gives you the feeling of progress: more resumes, more screens, more activity on the dashboard. But activity isn't the same as expanding the actual number of qualified, available people. If the pool is capped at 200 people in a 50-mile radius, three more channels are just 200 people searched three more ways.
Meanwhile the skill you actually need, deep technical judgment at the senior level, has never been geographically bound. The engineer who can own your system design decisions doesn't need to live near your office to do that well. Companies that have internalized this aren't running a novel experiment: GitLab operates across 60+ countries and has built senior engineering functions entirely on that premise.
What actually moves the needle
If your req has been open past 90 days, the honest question isn't "which channel haven't we tried." It's "which pool are we drawing from, and is it big enough to contain the person we need." For most companies still hiring locally-first for senior roles, the answer is no, and it was no on day one.
This isn't an argument for lowering your bar. It's an argument for widening the map you're searching. Senior engineers who can operate independently, communicate async, and own outcomes exist well outside your commuting radius, and often outside your borders entirely. Central European engineering markets in particular have produced deep benches of exactly this profile: strong CS fundamentals, English-fluent, used to distributed team structures, and priced sanely relative to a market where remote senior roles now carry a median comp around $142K.
Four months of silence on a req isn't bad luck or a weak recruiter. It's a signal. The pool you're searching was never going to contain enough of the right people, no matter how many times you search it. The fix isn't another channel. It's a different map.
Top comments (0)