Why don't developers respond to recruiters? (a survey)

Why don't developers respond to recruiters? (a survey)
Post Author: Aaron Decker |
Date published: September 18, 2019

It seems like when speaking to developers about recruiters I often hear the same thing: developers feel like they are being spammed constantly with jobs that have little to do with their experience or interests.

However, I wanted to really understand a bit more what developers actually think (instead of just collecting anecdotes) so I decided to do a survey and try to look at numbers.

I asked r/programming and r/cscareerquestions and I got 50 people to respond, which I think is a pretty good mix of types of programmers and experience level.

My first question: “How often do you respond to recruiters”?

1 EZ7Dbn0aYU2Sctfo1He2Jw

This is fairly unsurprising to me. Most people respond very little: about 2–10% of the time, while others almost never respond and a few respond fairly often. I, myself fall into the camp of responding most of the time (maybe half of the time, honestly) with a polite “not interested at the moment” unless it is something that looks like outright spam.

Just as an aside, what is clearly spam to me? When I see something like this:

Clearly spam, or maybe even a scam. Clearly spam, or maybe even a scam.

2nd Question: “What percentage of jobs have you gotten using recruiters”

1 yuYG1MXuqPRThmwjZN9GKw

This was a little surprising to me: almost 60% of respondents have never found a job using a recruiter. Most developers in this case it seems are not using recruiters to find jobs. So that means the majority of developers are either applying directly to jobs or being referred to them by friends.

This sounds right if I think about it. On the team I am on now, half of the team is composed of people somebody had previously worked with and referred internally. Obviously, you are going to trust a former co-worker more to give you the honest lowdown on a job over a complete stranger who will be compensated for placing you.

Question 3: “When you don’t respond, why is that (most often)?”.

This was a little bit difficult to clean up the data because I let people type in a custom “Other” box. This will be the subject of another blog post (because I got so many interesting responses). But here is a cleaned up data set:

You might need to zoom in for this. You might need to zoom in for this.

I’ll summarize the top 5 reasons and explain them:

  1. Mismatched skillset: this just means e.g. a .NET dev was asked about a Java job. Or a frontend dev was sent a backend dev job.
  2. Clearly sent in bulk: clearly spam, the company looks sketchy, they are asking for bunch of canned information. Obviously impersonal.
  3. Job in another state: just like what it sounds. You live in Washington and you get a message about a job in New Jersey.
  4. Mismatched level: you are a junior dev and sent a message about a architect role. Or you are currently working as a tech lead and sent a message about a junior dev opportunity.
  5. Off-putting language: typos, grammar issues, “Coding Rockstar”, any kind of stuff like that.

Another big runner up that you could combine is “Uninteresting company / Uninteresting project”. I know many developers will avoid certain industries like the plague. Government contracting, insurance, banking are all pretty unpopular anecdotally because most developers seem to really hate bureaucracy and coding is ultimately a pretty creative endeavor.

What can recruiters do about this?

I think that looking at this data there is a clear disconnect between developers and recruiters. It seems that recruiters that are struggling should focus on getting educated. Learn more about the industry you are recruiting for. Obviously spamming out jobs en-masse works, or people would not do it, but is that sustainable?

Even if you are a good recruiter and you are sending targeted messages and working with quality companies, could you get a higher response rate if you knew more about technology, tech culture, and developers? My answer would be yes! In a previous interview with a senior recruiter that I wrote up here he explicitly says he notices that an uptick in responses when he does things “not in a cookie cutter fashion”.

Join me next time when I go through the detailed responses developers wrote about their recruiting experiences. I also have a survey of recruiters I will be writing up soon.


A quick note!

Was this article helpful? Want more content like this? Please sign up to the list!

Also, if you are interested in learning technical topics through a video course specifically created for recruiters, don't forget to check out the courses I offer.

The main course "How to Speak Software Engineering Jargon for Recruiters" is specifically designed to help new tech recruiters get up to speed fast on technical topics.


Written By Aaron Decker

I'm a full stack developer specializing in Node.js and React. I have worked as a Tech Lead and hired teams, and as a Senior Software Engineer at multiple fortune 500 companies building large products. I also did a brief stint teaching programming courses as an Adjunct Instructor at a local community college.