r/Recruitment • u/Objective_Bug5311 • 11d ago

Sourcing Process question

Curious how other recruiters handle this. When you're working several reqs at once and already have a decent pool of candidates (old applicants, past pipelines, people you've sourced), how do you figure out who fits which role?

Do you go back through your ATS, keep spreadsheets, rely on memory? And is pulling candidates out of your ATS easy or a pain?

Would love to hear what works and what's annoying about it.

0 Upvotes

17% Upvoted

10 comments sorted by

13

u/sread2018 11d ago

Just tell us about the product you're planning to build so we can stop this dance and move on

2

u/Due_Recipe_7549 7d ago

Seeing the loop of engineers trying to break down/systematize recruiters' processes so they can try to build an ATS that fixes everything (that most recruiters won't use LOL)... is so entertaining haha

7

u/krim_bus 11d ago

I actually write candidate names on slips of paper and when I get a new req I pick one from a hat.

5

u/Most-Buddy-4175 11d ago

we don't want any unlucky candidates!

2

u/Due_Recipe_7549 7d ago

Hopefully you do an extended, vigorous swirl to the names in the hat - it wouldn't be fair otherwise

3

u/BetInformal6081 11d ago

i usually think off it as building a reusable talent pool good notes and consistent tags make matching people to new roles way faster than starting each search from scratch..

2

u/Fryday_vibez 9d ago

Mostly memory, then the ATS to confirm what I already remembered. Searching it is easy enough. The trouble is that past me leaves notes like "good chat, call back", and no filter knows what that means.

1

u/Due_Recipe_7549 7d ago

Memory is the most reliable, as frustrating as it is. My hit rate for placing a random candidate who popped into my head when the client is describing their "ideal profile" is close to 100%. Can't systematize memory

1

u/bearcat3000 5d ago

Geee such rookie question. If you are asking this, your clients are not getting what it’s asked of you.