Why Is Sourcing Such A Pain In The A$$, Part 3

“Boolean is bullsh*t”

Before you lose your mind on this one, hear me out. The best sourcers & recruiters are absolute masters of Boolean. Give us a little AND, OR, NOT, some “quotes” and (parenthesis), then watch the magic happen.

Skills, industries, locations, companies, whatever. The results get granular. Specific. Far more targeted. Far less candidates replying “what the hell dum dum did you even read my resume?”

There’s a learning curve, of course. So everyone who put in the time is super proud of their skill.

????Question is: why the hell are we writing code in 2022?

That’s what we’re doing. Because all the crappy sourcing tech makes us. Still.

No matter how you slice it (or how proud you are of your Boolean wizardry), there’s always gaps. Keywords you left out. Bad combinations that filtered things out. Aspects you didn’t think of.

Every time, no matter how good you are.

Not to mention: it takes so damn looooong.

Meanwhile in the software engineering world, everything is 10x easier than a decade ago. They keep building better and better tech. It writes the damn code for them.

So why can’t we use natural language processing to tell our tools what we want with regular words? And machine learning to make it more and more accurate over time?

????Eliminate the gaps.

????Save a ton of time.

????Get junior sourcers up to speed a hell of a lot faster.

Ok ok. I’m talking my book. Sourcewell does exactly this. It’s cut down our own sourcing time by 50%. Same with our beta clients.

Hit me up if you’re interested. Or just demand that the tools you use now get their sh*t together.

James Hornick

Partner at Hirewell. #3 Ranked Sarcastic Commenter on LinkedIn.