|
|
|
|
|
by igneo676
1684 days ago
|
|
This feels like a fundamental mismatch between his expectations as an internal recruiter vs external recruiters > built the technical recruitment operations in the last 3 start-ups I worked for, so I feel I’m somewhat qualified in the subject matter Sure, your startup might have some very tight requirements for a position and the ability to research candidates before conversations. That's precisely what you should do since time is limited and (presumably) you're not hiring for a TON of positions But an external recruiter needs to match X jobs to Y candidates. It almost doesn't matter what the tech stack is at that point, you probably have an open position to fill that'll match that person. It's a numbers game and it's a "Please respond to me at any cost" game. And often, even if you did research, there are so many false negatives that it didn't even matter to begin with. I've had targeted recruiters reach out to me that are amazed when my current position doing $CURRENT_TECH isn't completely representative of my skills and I'm actually a viable candidate for $NEW_JOB_WITH_OTHER_TECH The only real response here is to cut em some slack or ignore them. Guides like these don't help |
|
Now saying its a numbers game also makes sence yet they (recriuters) are ignorimg the fact that each one of those "numbers" they turn into an interview will require 2 or 3 hours from the developers who will actually serve as a filter... I (personally) am tired of having to interview people who from the first 10 minutes I know won't be a good fit just because the recruiter is playing the "numbers game"