Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Stupid Recruiter Tricks Vol. 2: Salary Talk and Candidate Control

DZone's Guide to

Stupid Recruiter Tricks Vol. 2: Salary Talk and Candidate Control

In my continued efforts to expose recruiting behaviors and the incentives behind them, I introduce the industry concept of candidate control and its role in the recruiter/candidate relationship.

· Agile Zone
Free Resource

Reduce testing time & get feedback faster through automation. Read the Benefits of Parallel Testing, brought to you in partnership with Sauce Labs.

While training for my first job as an agency recruiter, I was directed to ask all candidates for their current salary. It was uncomfortable at first, partially because of the vast disparity between my income as an entry-level recruiter and the salaries of experienced software engineers in the late 90s during the dot com boom. Discussing compensation with strangers can make people uncomfortable, whether in casual settings or in negotiations with employers. Children (many in the US anyway) are taught not to ask people how much they make, and this cultural element may contribute to why some are reluctant to discuss. Even as an experienced recruiter, I rarely get a rapid-fire response to money questions.

Recruiters gather as much data on candidates as possible, and are trained to use a strategy to prevent spooking anyone. Initial calls start with harmless questions about candidates’ interests and experience, eventually graduating to more sensitive topics once rapport is built.

In my early years, candidates unwilling to respond to the “How much do you make?” question were told that I needed numbers to proceed. Some candidates shared data, some refused again or ended the call, and others asked why I needed to know. Nobody needs to know someone’s salary history to hire them (or recruit them for hire), do they?

One scripted rebuttal was “I don’t want to waste your time”. This phrasing is no accident (“waste your time”, not “waste my time”) and infers that candidates derive benefits by answering, although recruiters are likely more concerned about wasting their own time. The time reference alludes to the possibility that a candidate goes through interviews but gets an offer below expectations.

The most popular theory behind the recruiter’s insistence upon learning salary information is probably the one eloquently expressed by Patrick McKenzie (aka “patio11”) in his epic >6000-word 2012 post on salary negotiation, where he suggests that candidates being interrogated for numbers (though not specifically by an agency recruiter) should think “You’re lying to me to attempt to get me to compromise my negotiating position.” I believe there are more exceptions than Patrick does to the often quoted “never speak first” rule of negotiation, and I feel informed candidates with market knowledge shouldn’t fear providing salary history. The number provides one data point as to what someone was willing to work for in the past, but candidates familiar with market values don’t need to accept less than market for their services.

As a recruiter, couldn’t I work with a candidate without knowing their current salary or their expectation? It probably depends on the hiring company, but most of the startups I have worked with are willing to play along without salary data and I’ve made successful placements blind to salary history.

The better explanation for a recruiter’s behavior when candidates deny salary info requests is that the refusal indicates a lack of candidate control.

Candidate Control

As I’ve written beforecandidate control is the notion that a recruiter gains influence over a candidate’s actions during the interview process, culminating when the recruiter gets the candidate’s acceptance to a job offer. Considering that an agency recruiter is only paid if a candidate takes their job, time spent with candidates unlikely to accept an offer is wasted (using entirely short-term thinking).

How Candidate Control is Achieved

One method of gauging and achieving control is through small incremental requests with multiple positive responses over time, with the theory that this repetition will somewhat condition the candidate to be agreeable to future suggestion particularly at offer. The first requests are small and necessary to the hiring process: schedule a phone call, send a résumé, respond to basic background questions, etc. Eventually the requests are not vital and in some cases just self-serving for the recruiter: call immediately after an interview with feedback, requests for references early in the process, asking for referrals or introductions to contacts, etc. Compliance is a good sign for the recruiter.

Examples of the highest levels of control might be when candidates give recruiters proxy to accept offers over $SALARY or to let the recruiter provide resignation notification to the candidate’s current employer. Yes, this happens.

What Every Job Seeker Should Know

Candidate control isn’t something to fear for most job seekers, but it’s helpful to be aware of how recruiters are trained to gain influence and close deals. This doesn’t necessarily mean recruiters are all coercing candidates to accept jobs they shouldn’t, but candidate control could lead to that outcome.

When a candidate refuses recruiter requests (whether reasonable or not) early in the process, recruiters assume that candidate will prove difficult to persuade when interviews and offers are at hand. If a candidate is unwilling to provide information, a recruiter who insists on control may simply abort the process.

The aforementioned “I don’t want to waste your time” rebuttal might really mean “I don’t want to waste my time with candidates I can’t control who therefore are less likely to accept my offer“.

Got a question about recruiter behavior that might make for a Stupid Recruiter Tricks column? Leave a comment below.

The Agile Zone is brought to you in partnership with Sauce Labs. Discover how to optimize your DevOps workflows with our cloud-based automated testing infrastructure.

Topics:
recruiting ,recruiters ,job search ,career advice

Published at DZone with permission of Dave Fecak, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}