Loading...
Answers
MenuWhat are the pain points felt by external recruiters? How do they deal with these pain points?
This question has no further details.
Answers
since most get paid upon a candidates permanent offer most of the hastle comes from finding the right person. knowing how t filter helps a recruiter incrementally over time leading to repeat customers.
feel free to call one of us to help you get going or guiding you through hurdles. :)
My Answer would be the Indian Context...
By external Recruiters, I would presume that to be Recruiters in a Search Firm / Agency.
The following would be the main pain areas
1. Foreclosure of a position - wherein the position flagged off to the external recruiter has been filled through another source viz. job boards, Employee Referrals, Direct Applicants and such closures are not intimated by the Client on a timely basis – Lack of feedback from the Client
2. Similarly…absence of feedback on the resumes submitted against an open position, on a timely basis. Effort put in sourcing the candidate could go waste as delayed / absence of feedback could result in lack of candidate interest and affect recruiter motivation
3. The candidate referred by the Recruiter for an open Client opportunity, is no longer available, as he/she might have got another job offer..thus resulting in a wasted effort from the Recruiter.
4. Replacement Clause..the candidate successfully placed for an open opportunity, leaves within the time-period of free-replacement (normally a replacement guarantee of 3 to 6 months is offered by the Recruiting Agency for all candidates placed by them), thus resulting in refunding the placement fee collected or adjusting it against future receipts.
5. Non-receipt / delay in receipt of Professional Fees for the services rendered..delaying recruiter incentive and affecting Recruiter motivation.
The above constitutes only an illustrative list and is not exhaustive.
I am open for a call to discuss this further.
As an executive search consultant for over two decades, we have been helping our clients with hiring solutions to help grow their business.
While we have had our share of contingent search assignments- ( where one gets paid only for success), we have often found that most companies look at couple of metrics (as they are perhaps easiest to measure!)
i) Time to fill.
ii) Cost of hire.
And these are rather painful especially since
a) Often we compete with the internal recruiters-with a handicap. They have already done their bit, 'sprayed & prayed ', checked out the most obvious (a la low lying fruit) candidates from the competition & region, and well past an internal deadline.
b) Companies also share the same mandate with multiple external recruiters hoping to get a better spread, and forcing an extra pressure to try harder...and find a candidate who is willing to join 'as of yesterday'!
Ironically not necessarily the best of tactics..as it now becomes instead a 'game of speed from among those immediately available'-who pressed the buzzer first..rather than actually investing in the research and the best practices to identify and attract the best person for the specific role.
My approach has been to educate our valued clients to be sensitive to
1.the 'quality of hire' and
2. the "ROI" of the right hire.
And given a chance to partner them -rather than play a role as a vendor- we have been able to provide an extra edge by giving them
3. Culture fit
4. Great candidate experience -and ensuring
5. Better employer brand equity
And hope to drive home the essence of what Jim Collins said in his book, Good to Great, "People are not your most important asset. The right people are!.
I shall be glad to elaborate. Am just a call away :)!
Related Questions
-
I've already applied for a "dream job". They are forward-thinking and advertise their culture and distributed team.
What can I do now to stand out?
You need to show them that you can solve their problems. The #1 mistake made by most applicants is that they keep talking about themselves: "here are my skills, here's what I've done, etc..." Instead of talking about yourself, talk about them: "You need someone who can jump right in; someone who can start working without making mistakes. You also don't have a lot of time for training. I can get started right away." This is going to require some research. Follow the founders / managers on Twitter. Read their blog posts. Scan their error logs (if they're public). Find out where you're *needed* and highlight that. Generally it's best to do this during the application process. If you've already sent in a cover letter and resume, it doesn't hurt to send a follow-up email that says: "I've been doing some research, and I think I've found some places I could be helpful."JJ
-
What is the best way to find a CTO for my start up?
I'd take a look at the large, established companies in the technology space in which you want to operate. Somewhere at one of those companies is an astute, experienced person who might be ready to get out of the big company environment if you come along with the right idea. E.g. Cisco if you are doing networking, Salesforce if you are doing marketing automation, Intuit if you are doing financial apps. The trick is finding one who not only has the technical expertise and wants to get out, but is well suited financially and psychologically for a startup. I learned the hard way that co-founders who are not in the same boat financially can make for an unhappy parting.KE
-
What 3 questions to pose to a developer, to gauge his expertise level?
If you're not technical yourself, then you might not be able to gauge the efficiency of a candidate's algorithms or critique her code. But there are still some higher-level, more behavioral things that a non-technical interviewer should be looking for in a strong development candidate: 1. What are some tech blogs that you follow? Explain an interesting article to me that you read from one of them. The software development world changes all the time. Best practices are constantly evolving and new libraries are regularly released which make developers more productive. If a candidate doesn't keep up with the latest software news, that might be a red flag that they're not curious or trying to improve themselves. Also, having them explain a technical concept to someone who's non-technical is a great way to gauge their communication skills. Do they seem like someone you could work with and understand easily? Do they care about pausing to make sure you understand, or do they just drone on with jargon? If you feel overwhelmed while they're explaining this answer, imagine how you'll feel when they're telling you why the product has bugs or isn't going to be done on schedule. 2. Tell me about a time you ran into a big roadblock with something you were building. How did you get past it? It's inevitable that a software developer will get tripped up or have to solve some Gordian Knot. Everyone has to bang their head against the wall from time to time. Maybe an API didn't have the data they needed or some function was running too slow and they weren't sure how to speed it up. You're looking to see how they are as a problem solver. Did they come up with a clever but hacky solution? Were they methodical or did they fly by the seat of their pants? Did they go back to the stakeholders and see if the feature's requirements were flexible? Did they work on it for hours and hours trying new things? Did they ask for help from colleagues or on the internet? No right or wrong answers here, but you want to get the sense that this isn't someone who throws up their hands when they hit some friction. 3. Tell me about your favorite project that you worked on. What work are you most proud of? By asking them about the project they're most proud of, you'll get to see what it is that they value most. Maybe one candidate is most proud of a side project they built, even if it wasn't that technically complex, while another candidate is proud of their esoteric PhD project or some specific algorithm they improved. Again, no right or wrong answers, it really depends what type of candidate you're looking for. But it lets you see into their mind a bit, and get at some of the aspects that can make someone a strong development candidate. If you want to talk more specifically about hiring for your team, I'd be happy to do a call!HB
-
I am a non-technical cofounder. Where are the best places to find and attract a technical cofounder?
I have advised a number of Clarity members on this question exactly. LinkedIn can be a great place to find your technical cofounder. I would look for someone who has been at their current company longer than 18 months and has relevant experience or interest in the problem you're looking to solve. Reaching-out "cold" can work, if you keep your message short and relevant. Here's what a technical cofounder will need to see in order to feel comfortable joining you: 1) That you can fund and/or have raised sufficient money to cover the expenses up to and past launching the first version of your product. 2) That - in their assessment - you have what it takes to raise multiple rounds of funding (if the business is reliant on VC) or that you have what it takes to successfully bootstrap the business. 3) That you are realistic or at least credible in your assessment of the opportunity and have done sufficient customer development to ensure there is a viable market for your product or service. 4) That you and the technical cofounder have sufficient personal chemistry so as to want to and be able to survive an incredibly stressful and emotionally intensive journey together. Happy to talk you through any of this in detail in a call and go into the specifics related to your location, background, and type of product or service you're looking to recruit a cofounder to.TW
-
I have started a startup and don't have any experience in startups and putting in my own money, $250,000. How do I find the right technical people?
I think you will likely get many different answers to this question, but my personal believe is that if you are building a software-based business and you don't have experience and you don't already have the right connections, your best shot at success is going to be if you do all the technical work to start with. I would even recommend that if you have zero technical experience right now. You may read about other people that somehow start businesses without doing this, but either A) they are extremely lucky or B) they already have connections/experience/a network that they can rely on. It is going to be a slower process than you would like because you are going to have to get your hands dirty, but this is going to greatly increase your odds for success in the long run.JW
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.