We just placed a Development Geologist. The role required experience in a specific region of Alberta—not just “Alberta experience,” but actual hands-on work in that particular play.
And it got me thinking about something that happened about 20 years ago.
I met a guy with a dream. He was building a software platform for hiring managers who recruit geologists and engineers in Alberta. The concept? You’d click on a map, and it would generate a list of candidates with experience in that exact region.
Honestly? I thought it was brilliant.
It was like taking everything that’s in my head—all the patterns, networks, and sourcing intel—and turning it into an app.
It never got off the ground.
To all the companies that need strategic sourcing for specialized technical roles, we’ve got you. And to our newest hire: congratulations on your new role as Development Geologist!
Why That Software Idea Failed
I don’t know the full story of why it didn’t work. Maybe funding fell through. Maybe the technology wasn’t there yet. Maybe it was just ahead of its time.
But I’ve thought about it over the years, especially when people ask why they can’t just use LinkedIn or other recruiting software to find specialized candidates.
Here’s what I think: some things are really hard to code.
You can build a database of resumes. You can map locations. You can track job titles and companies.
But can you code for the fact that a geologist who worked the Montney formation five years ago might be perfect for a Duvernay project now, even though their resume doesn’t mention it? Or that someone who spent three years on a specific SAGD operation has exactly the transferable knowledge another company needs?
That context lives in recruiters’ heads. In conversations. In networks built over years.
It doesn’t show up in a database query.
What’s in My Head (That Can’t Be Coded)
When I place a Development Geologist for a specific region, I’m not just searching keywords.
I’m thinking about who worked in that area. When they were there. What companies operated those assets. Who moved where since then.
I know which candidates have deep expertise in specific plays versus broader experience. I know who prefers site-based work versus office roles. I know who’s open to opportunities and who’s happy where they are.
That’s not resume data. It’s market knowledge built from years of conversations and placements.
And honestly? I don’t think you can code that into software. At least not the way it actually works in real recruiting.
Why Geographic Expertise Matters
This isn’t just about geologists.
We recently placed a Control & Instrumentation Technician for a remote location. The client had no relocation budget, so we needed someone local or willing to relocate on their own. That meant understanding who lived where—information that doesn’t appear on resumes.
We’ve filled roles requiring candidates within a 10km radius for sustainability policies. Again, not something you can easily search for in a database.
Site-based energy roles need people who want to be on-site, not candidates you’re trying to convince that it’s not a step backward. That’s about understanding motivations and career goals, not filtering by location tags.
Even that 7-minute reception fill? That worked because I knew who was local, available, and already trusted by the client. No software search would have delivered that.
Geographic expertise matters because real placement decisions involve context that doesn’t fit into database fields.
When Software Works (and When It Doesn’t)
Look, I’m not anti-technology. I use LinkedIn. I use databases. I have systems for tracking candidates.
These tools are useful. They help me stay organized. They’re good starting points.
But they don’t replace market knowledge.
LinkedIn can show me who lists “geologist” and “Alberta” on their profile. It can’t tell me who has the specific regional expertise my client actually needs.
An ATS can filter resumes by keywords. It can’t tell me which candidates will thrive in a site-based role versus an office environment.
Job boards can post openings. They can’t tell me which passive candidates aren’t looking but would be interested in the right opportunity.
Software is a tool. But it’s not a replacement for someone who actually knows the market.
Strategic Sourcing vs. Database Searching
There’s a difference between searching a database and strategic sourcing.
Database searching: Enter keywords, filter results, reach out to matches.
Strategic sourcing: Think about who has the right experience, where they might be now, who in your network knows them, which companies operate in that region, what transferable skills matter for this specific role.
One is transactional. The other requires pattern recognition built from years of placements.
When I’m sourcing for a Development Geologist needing experience in a specific Alberta region, I’m not just looking at current job titles. I’m thinking about career paths, company histories, project timelines, and which candidates have the depth of regional knowledge that actually matters. This is what strategic sourcing recruitment looks like in practice—especially given what’s actually happening in Alberta’s energy sector right now.
You can’t automate that kind of thinking. Not yet, anyway.
The “Old School” Advantage
That software concept from 20 years ago would have been convenient. Click a map, get a list of candidates. Done.
But recruiting doesn’t work that way. Not for specialized roles that require real expertise.
Companies need someone who understands the nuances. Who knows the difference between surface-level experience and deep regional knowledge. Who can have meaningful conversations about what the role actually requires. That’s where strategic sourcing makes the difference.
That’s still human work. And probably will be for a long time.
So yes, you’re stuck with my old-school spreadsheets and whatever mapping process lives in my head.
But for specialized technical roles where geography, experience, and context all matter? That old-school approach still works better than any software I’ve seen.
Need Strategic Sourcing for Specialized Roles?
If you’re hiring for technical positions that require specific expertise, regional knowledge, or hard-to-find skill sets, let’s talk.
Human expertise still matters in specialized recruitment.
Strategic Sourcing FAQs
-
Can’t I just use LinkedIn to find specialized candidates like geologists or engineers?
LinkedIn is a useful tool, but it only shows you what people put on their profiles. It can’t tell you who has specific regional expertise, who’s actually open to opportunities, or who would be the right cultural fit. Strategic sourcing uses LinkedIn as one tool among many, not as the complete solution.
-
What makes geographic experience so important for geologists and engineers?
In energy, not all experience is equal. A geologist who worked the Montney formation has different expertise than one who worked Cardium or Duvernay plays. That regional knowledge affects everything from resource evaluation to drilling decisions. Generic “Alberta experience” often isn’t specific enough.
-
How do you track which candidates have region-specific experience?
Years of conversations, placements, and market knowledge. I know who worked where, when they were there, and what projects they were involved in. Some of this is documented, but a lot lives in memory and professional networks built over time.
-
Is technology replacing recruiters in specialized fields?
Technology is changing how we work, but it’s not replacing the human expertise needed for specialized recruiting. AI and databases are useful tools, but they can’t replace market knowledge, relationship networks, and the context that comes from actually understanding a sector deeply.
-
What’s the difference between a recruiter who uses databases and one who does strategic sourcing?
Database searching is reactive—you look for people who match criteria. Strategic sourcing is proactive—you think about where the right people might be, even if they’re not actively looking. It requires understanding career paths, company operations, and market patterns that don’t show up in search results.