Disrupt Tech Recruiting II – So You Want Ari Gold?
Join the DZone community and get the full member experience.Join For Free
After publishing How to Disrupt Technical Recruiting – Hire an Agent and reading the subsequent feedback from readers at Hacker News and elsewhere, it is clear that at least some subset of engineers believe two things:
- The technical recruiting industry is at times remarkably flawed, and the financial incentives inherent to the system will not always lead a recruiter to represent the job seeker’s best interests.
- There is some demand for a talent/agent model for tech professionals, and it is a service several would be willing to pay for.
And it is also worth noting that the only agent that engineers
have know is Ari Gold (or at least that is the agent they want). Not
even ONE Jerry Maguire reference? It seems engineers want to hug it out
and care less about being shown the money.
During my dissection of the industry, I somehow overlooked perhaps the biggest flaw that is at the absolute core of the issues with the recruiting industry. I’m a bit embarrassed that I missed it, and it wasn’t mentioned in the threads, so here goes:
Secrecy and privacy of information is THE cornerstone to traditional recruiting.
Why is that? Well think about it. If hiring companies knew every local candidate that possessed the skills they were seeking, many would not use an agency recruiter to handle the process and would simply have HR/managers contact them directly. Likewise, there would be many candidates that distrust recruiters applying directly to jobs if every available job were listed in one single place to search. There would certainly be some companies and candidates that recognize the value the recruiter brings beyond the initial introduction, but if all information were available to both sides we would find much less demand in the industry.
Why do you think recruiters don’t generally list their clients’ names publicly? Why are there so many complaints about recruiters being unwilling to share a deep amount of detail about projects or their open jobs? There are two main reasons.
- To prevent other recruiters from learning about who they represent (NOTE: this is a big one, particularly for recruiters that work exclusively with start-ups that fly under the radar).
- To prevent candidates from applying directly to those companies, thus cutting out the chance for the recruiter’s fee.
So in order to preserve their chances of being paid a fee, recruiters need to keep candidates and companies from knowing about each other until a precise moment where they make the introduction to both sides, and then hope that the company doesn’t respond with some evidence of prior contact and that the candidate doesn’t say that he/she applied to that job yesterday. If either of those two scenarios happen, the recruiter has some incentive for that deal to NOT work out, even though it is his/her client! Let’s assume that company has one vacancy, and my candidate applied to it a day before I discussed it with him/her. My incentive instantly goes from wanting my candidate to get the job (so I can get a fee) to a financial incentive that the candidate isn’t successful (so the job will still be available for another candidate I can find). That is a very dark and unfortunate set of incentives inherent to the system.
It’s very easy to see how the incentives are built in this model. Recruiters have the incentive to help out their client companies to fill jobs, but only if the hire comes from my agency. The recruiter has the incentive to help a candidate find a job, but only if he/she takes a job at one of our clients. This is the unfortunate symptom of contingency work, and thankfully in my current business model (which isn’t contingency) I don’t have these same incentives to the same degree. Who are contingency recruiters really providing a service to anyway?
Why do you think recruiters see LinkedIn as both a blessing and a curse? We use it to find new candidates and keep in touch with past candidates and clients, yet we realize that everyone else now has access to the same information and companies can much more easily find candidates. As a recruiter, you are probably likely to list your contacts as ‘private’ for this reason.
The agent model would not have this privacy incentive built into the system. I could see an argument made where an agent might not want other agents to know who he/she is representing, but I think that is a much smaller problem than what we have today. When one of an agent’s talents is seeking work, there would be a campaign of open information to try and get the talent noticed. Having a business model based on privacy and secrecy is much less attractive than an agent model with openness.
Enough about what’s broken, let’s talk about solutions.
Based on the discussions, here are the services that the talent knows they want:
- Negotiation in job changes – Engineers seem to agree that an agent would probably be better at negotiating compensation packages. Another added benefit to having an agent in act as a proxy in negotiations is the preserved comfort factor after you potentially start the job. Picture a very trying or heated negotiation between an engineer and a start-up CEO that comes to an eventual agreement, and then the two must work in adjacent cubicles the following Monday. A buffer would have helped prevent any potential awkwardness.
- Job identification and coordination – Many in the community made it pretty clear that they are not interested or skilled in cold calling and introducing their services to potential clients. Having an agent do the legwork to identify potential employers and then to contact them and schedule meetings on the talent’s behalf will save lots of time to do other things. For consultants paid hourly, remember that every hour spent on job search is an hour you can’t bill to a client.
- Competitive salary/rate information – There seems to be a general distrust for websites that provide market information, and engineers may be somewhat insulated when it comes to what others with similar skills are earning. An agent would have some solid evidence regarding street value of any talent and would do the research necessary.
- Marketing/PR/Selling – It has become clear to me over the years that there is a sizable percentage of talented engineers that are uncomfortable talking up their own skills, and that was mentioned a couple times as another asset of an agent. Marketing and PR would probably mean different things for different career levels, but it could include work to increase the talent’s blog traffic, booking a presenter’s invite to a users group/meetup, or strategy on how to build the talent’s brand.
There were some services and advantages that were somewhat surprisingly not mentioned:
- Handling incoming job solicitations – All of the complaints about recruiter spam and cold calls are gone for the agent’s talent. Forward calls, emails and LinkedIn spam to your agent, and he/she will investigate. Put your agent’s name on your website and LinkedIn profile. If the opportunity is legitimate and meets the criteria the talent sets for sharing, your will get the details. If not, you never have to waste your time hearing about it.
- Interview coaching – Not just your standard fare interview coaching you can find on web sites, but also any inside tips on the specific interview. This could include past experiences others have had with the company, some research on the background of the people you are meeting, and anything else that will be helpful to the talent. Remember that the agent is representing you at this point and not the company. As one reader noted, a good agent would not want to do companies a disservice by providing specific interview questions (as that would harm the agent model, the hiring company, and the agent himself/herself), but it is fair to offer the talent some guidance on what format to expect and who they will be meeting.
- Internal company information – As your representative, the agent should be providing talent with details on both their current employer and any that you may be considering for future employment. The information learned from discussions with others in the business will be helpful to the agent’s entire stable of talent. Consider it the type of info you may find on Glassdoor, but from verified sources.
- Career advice in non-search situations – Are you thinking about moving from code into management, or considering taking a leadership position on a project doomed for failure? Considering a jump into contracting, or thinking about abandoning your current independent consulting project to join a start-up? Want to talk about it? The value of this advice could be quite large yet difficult to quantify.
- Negotiation of promotions or raises – Changing jobs is not the only scenario where negotiation may take place. An agent could help you get the best deal from your current employer, either through direct negotiation or by coaching you on how to maximize your chances of getting a good number.
- Resume creation/curating – This one isn’t a huge service but it’s a few hours out of your work year.
- Transparency! – The agent model is completely transparent to everyone involved. The agent represents the talent, and the talent pays for that representation. There is no question about the agent’s loyalty as there is in contingency recruiting models (is the recruiter representing me or the company?).
Some potential issues were identified in the comments
- Would there be any conflict of interest when representing multiple candidates? Doubtful. I guess there could be a rare situation where two talents vie for the same position, and in that scenario the agent would simply represent both fairly and let the best person for the job win. The agent would probably have no financial incentive favoring either candidate. Transparency would be important (revealing the situation to both talents).
- Would there be backlash by hiring entities against candidates who use an agent? It’s hard to tell, but it’s conceivable that there would be some organizations that might react hesitantly at first. However, the key here is that an agent would be providing a service to a company for free (or if not completely free, definitely much less expensive than recruiters). It would be hard to think that firms would not be very pleased with a cold call from an agent stating that there is a qualified candidate interested in your company, and you will get all the normal recruiter services for the process with no recruiter fee at the back-end.
- How much would the agent need to know about technology? This one comes up quite a bit in criticisms of technical recruiters and then in the discussion of an agent. The agent needs to know enough about tech that he/she won’t misrepresent the talent, and will not waste time marketing talent to positions that are not a technical fit. An agent should also have some sense of tech trends, what skills are in demand, and the overall market for different types of talent. The biggest complaint seems to be wasting time with discussions of jobs that are not a fit or being sent on interviews that are not appropriate. An agent would not have the same incentive to send you everywhere imaginable, as that incentive is not built into the agent model.
- Would the service be just for contractors? No, not the way I see it. The pricing model for contractors is very easy to consider, as paying a percentage of hourly rate to the agent is already a common practice for staffing firms (what is called ‘margin’). The value of an agent’s service to engineers with salaried positions seems very obvious in helping to manage the overall career as well as the career moves.
How do we compensate the agent?
This is a bit tricky and I believe that the pricing model might be different for contractors and talent in direct salaried positions. For contractors, the existing model (a ‘per hour’ cut) is well-known and accepted. I think the main difference is an agent would have some fixed transparent rate ($x/hr or y%/hr. Many recruiting firms do not reveal the full bill rate to the contractor, which tends to cause distrust when the contractor finds out the actual rate. Having a fixed percentage or dollar per hour figure would make the relationship much more comfortable for both sides.
For talent in permanent salaried positions, there needs to be more discussion. My vision would be some flat annual representation fee for service with an additional charge/bonus for times of active job search (where the level of services and time invested would increase). The job search fee could have several models built in – perhaps an hourly rate, flat fee per week/month, flat fee per job search, or some percentage of salary. The problem with the percentage of salary model is that it gives some incentive for the agent to suggest you take the highest paying job even if that is not best for your career. Another model would be a negotiation bonus above some level set and agreed upon by the agent and talent. “For anything I get you over 120K, I get a one-time bonus of 50% of the difference.” That leads to some incentive to take the highest paying job, but it also gives more motivation to negotiate.
The reason I include an annual representation fee into the discussion is it helps to eliminate an agent’s incentive for candidates to change jobs, and it allows the agent to justify investing time with the talent to discuss career-related issues that come up. In the traditional recruiting model, the recruiter hopes everyone is looking for a job at all times. An agent would have much less of a financial incentive for you to change employers, so the agent wouldn’t be as likely to suggest you leave a job that is right for you.
Traditional contingency recruiting incentives are:
- Privacy and secrecy of client company and candidate information.
- Only help client company when it results in a fee. Only help candidates when they take jobs at my clients.
- A desire for people to leave jobs as often as possible.
Agent model incentives:
- Keep the talent happy so they remain your talent.
Let’s keep the dialogue going on this. Based on lots of direct feedback, it seems the community could be on to something. Agree, disagree, suggest?
Published at DZone with permission of Dave Fecak, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
File Upload Security and Malware Protection
Explainable AI: Making the Black Box Transparent
Cypress Tutorial: A Comprehensive Guide With Examples and Best Practices
Execution Type Models in Node.js