I've worked with third-party recruiters for many jobs I had while contracting. The pitch you mentioned can work, but only in the high-turnover world of contract consulting for big companies. This is NOT going to work for startups, or anything even close.
Contract programmers often switch jobs once a year. That's driven my duration limits set by companies, layoffs and the wanderlust that contractors often have. Big companies don't seem to want to be bothered with in-house recruiters, so they pay third-party companies to do the work. In the midst of that shuffle, a job requirement is handed from a hiring manager (who may not know how to code) to a company HR rep (who may edit it) to the recruiter. What you end up with looks like this:
Req: JAVA Developer
REQUIRED:
- 5-7 Years Java Experience
- 3-5 Years J2EE Experience
- 1 Year JDBC
- 3-5 Years Oracle
- MUST HAVE WEBLOGIC 10.3.5
PLUSSES:
- C/C++
- Perl
Of course, this may or may not have anything to do with what the job actually requires. They may have a taped-together C/C++ and Perl system they're trying to move to JEE/Weblogic They probably haven't really ordered (or gotten approval for) Weblogic, but it's what all the other companies seem to use.
So, the recruiter goes around spamming folks, and manages to find someone who's just hit their 12-month limit at BigCo and is open to find another position. The recruiter gets paid, the contractor may or may not like the position (but gets paid, anyway), and the hiring manager gets bagels brought in, courtesy of the recruiter's firm. Everyone wins, so to speak. That's why the cycle persists.
I'm describing this as someone who played that game successfully for many years. To someone who's working in startup circles it may seem like madness, and it would be if applied to startups. But it's how Fortune 500 companies, for better or worse, find talent.
To put it in startup terms, the third-party recruiter model seems to work well for companies who've found their business model and need people to execute it. For companies who are in a race to iterate and find a product-market fit, it's the kiss of death. Skip the free bagels, delete the emails and find people on your own or with internal recruiters who really know your company well.
I've worked with third-party recruiters for many jobs I had while contracting. The pitch you mentioned can work, but only in the high-turnover world of contract consulting for big companies.
Big companies have a specific reason for going with contract employees. It gives them (the company) a legal separation from the person who would otherwise have been an employee. That person can be unceremoniously dumped out onto the street if things aren't working out, and the company is willing to pay extra for that option.
Startups can't afford to pay a 30% premium on technical help just so it's less risky to fire the bad apples. And anyway they aren't big fat targets for lawyers like big companies are - good luck finding a lawyer to take your case on contingency when you're suing a company that's having trouble making payroll.
Contract programmers often switch jobs once a year. That's driven my duration limits set by companies, layoffs and the wanderlust that contractors often have. Big companies don't seem to want to be bothered with in-house recruiters, so they pay third-party companies to do the work. In the midst of that shuffle, a job requirement is handed from a hiring manager (who may not know how to code) to a company HR rep (who may edit it) to the recruiter. What you end up with looks like this:
Of course, this may or may not have anything to do with what the job actually requires. They may have a taped-together C/C++ and Perl system they're trying to move to JEE/Weblogic They probably haven't really ordered (or gotten approval for) Weblogic, but it's what all the other companies seem to use.So, the recruiter goes around spamming folks, and manages to find someone who's just hit their 12-month limit at BigCo and is open to find another position. The recruiter gets paid, the contractor may or may not like the position (but gets paid, anyway), and the hiring manager gets bagels brought in, courtesy of the recruiter's firm. Everyone wins, so to speak. That's why the cycle persists.
I'm describing this as someone who played that game successfully for many years. To someone who's working in startup circles it may seem like madness, and it would be if applied to startups. But it's how Fortune 500 companies, for better or worse, find talent.
To put it in startup terms, the third-party recruiter model seems to work well for companies who've found their business model and need people to execute it. For companies who are in a race to iterate and find a product-market fit, it's the kiss of death. Skip the free bagels, delete the emails and find people on your own or with internal recruiters who really know your company well.