Why automated recruitment tools fail

Why automated recruitment tools fail

It's no secret I've been on the job hunt for a couple of weeks now. The hunt for a great team to work with is as much a challenge for me as it is for companies. Recruiters are supposed to somehow help relieve frustration on both sides of the spectrum by taking care of the sourcing and screening bits on behalf of the company and establish connections with the company on behalf of candidates.

Recruitment companies have recently been going to great lengths to automate this process, usually by partnering with some SaaS solution offered by a 3rd party vendor[1] as a way of being more efficient at delivering top quality candidates.

My story

I recently made an attempt to reach out to a recruitment agency; despite all the warnings from my peers not to touch those with a 10-foot pole. It turned out to be an interesting experience to say the least.

Shortly after providing my name, email and resume, I was provided with a link to begin an automated test consisting of 20 questions which aimed to screen out poor candidates. According to the instructions, the top 1% of candidates could complete the exercise in roughly 20 - 30 mins which at first seemed like a rather interesting proposal. As I grabbed my morning coffee, I prepared myself for an hour long exercise aimed at evaluating my skill.

However, what I was confronted with was what I can only describe as hilariously bad, but don't take my word for it -

Here are some of the most interesting questions verbatim so you can make your own conclusion

The questions

It's worth mentioning that my application was for an Android developer position so all of the multiple choice questions were geared towards that. I retyped the questions in an effort to protect their privacy because their UI is just too obvious to anyone that's seen it before.

My goal here is to inform not shame.

For an Alert dialog, what is the order of buttons, if added? 


The repeating option here was not an error on my part. I guess all questions required 4 options. This is arguably just a super nitpicky question. Developers work alongside the documentation precisely because no one should have to memorize tiny details like this.

How should a package be named as a best practice?

[ ] Don't start the package name with a domain you own like com.mydomain

[ ] Don't start the package name with com.example

[ ] Start the package name with com.android

[ ] All of the above

There isn't even a correct answer here[2]...

Correct way to provide current context in anonymous inner class is/are

[ ] Use Context.this instead of this

[ ] Use getApplicationContext() instead of this

[ ] Explicitly use the name 'MenuScreen.this'

[ ] All of the above 

This question is asking a largely subjective question in multiple choice form. A more interesting interview question may have been to justify which methods you would not use and why.

Perhaps the least relevant of all was this

The Debug Perspective in Eclipse does NOT give you access to the following tab:

[ ] Debug - Displays Previously and currently debugged Android applications and its currently running threads

[ ] Variables - When breakpoints are set, displays variable values during code execution

[ ] Breakpoints - Displays a list of the set breakpoints in your application code

[ ] Devices - Shows the list of devices and AVDs that are connected to ADB.

Eclipse as an Android development IDE has not been the de facto standard of Android development since the first stable release of Android Studio in December 2014[3]. And this is not even taking into consideration the fact that it was in early access/ beta since March of 2013. While I couldn't find any concrete numbers showing developer adoption, Google did mention this in the 2016 Google I/O keynote -

92% of the top 125 apps use Android Studio

Asking this sort of question in 2016 serves as more of an indication to the candidate that you are a company that he/she should not be interested in.

The test concluded with the final 2 questions being generic coding challenges which in all honesty was largely reminiscent of test taking.

Why these tools fail

Given the experience I have just had with this tool; and all the regret I now feel in not listening to my friends and colleagues, I will now actively avoid any company that uses these systems when applying for jobs moving forward. Unsurprisingly, my research has shown that I'm not alone[4] in this opinion. At the end of the day, I can really see two kinds of candidates being screened out using these tools.

  1. Candidates that don't know anything about their field. [Which is good]
  2. Candidates with any kind of professionalism and self-respect. [Which is very very bad]

If you are a company or hiring manager that relies on these kinds of tools in order to bring the best people in, you are probably better off just screening the candidates yourself.

I do somewhat understand the reluctance that some people might have in "Humanizing" their recruitment staff. They have earned an especially bad reputation by being extremely aggressive when approaching candidates and trying to meet their quotas. A hilarious recount that a friend of mine shared recently demonstrates this perfectly

So a recruiter called me on the ​company phone​ while in the middle of a meeting of me and the CEO. The CEO answers the phone and hands it to me and I am just there listening to that recruiter selling themselves. I had to hold myself back from telling her to go f*ck herself but I think I will do that now since she added me on LinkedIn. The best part is that she was saying that she was ​returning my phone call​ but I never f*cking called her since I'm not even looking for a job! We had a bit of a laugh with the CEO but that was f*cking unacceptable.

The well warranted profanity aside, this shows the state in which we find ourselves when job hunting today. Candidates are treated as replaceable code churning machines and anything less than perfect is considered a defective product in a soulless process devoid of empathy.

In my experience, the best companies that attract the best people take a more novel approach to hiring. In fact, one company I recently reached out to actively hides their recruitment email address behind a cleverly constructed scavenger hunt across unindexed portions of their website designed to test candidates. I was told that this effectively reduces the number of applicants to about a dozen at the most. Another simply reaches out and tasks the candidates to develop a small app using specific tools. These are highly focused on testing the specific needs of the company. It properly asks

Is candidate X the right fit for my team?

Rather than the conventional does candidate X have the best test scores?

Most companies tend to forget that a companies recruitment strategy is an extension of the company which reflects the company culture and a bad one can affect the company's credibility and reputation in the industry[5]. A good recruitment platform is one that gets the candidates excited about the job that they are applying for and helps put the company's best foot forward, which is more than I can say about my experience today.


In conclusion, think that my experience speaks for itself here. Reaching out to recruiters doesn't have to be a painful experience[6]. Tools like this only serve to make it this way.

Footnotes and References

  1. Capterra.com. (2016). Best Recruiting Software | 2016 Reviews of the Most Popular Systems. [online] Available at: http://www.capterra.com/recruiting-software/ [Accessed 9 Aug. 2016]. ↩︎

  2. One might be tempted to suggest that com.example.* is the correct answer given that it is a reserved package on the play store. However the play store is not a part of the android API. Therefore I don't think that it's rules constitute java naming conventions. ↩︎

  3. Wikipedia. (2016). Android Studio. [online] Available at: https://en.wikipedia.org/wiki/Android_Studio [Accessed 9 Aug. 2016]. ↩︎

  4. Forbes.com. (2016). The Failure of Automated recruiting. [online] Available at: http://www.forbes.com/sites/lizryan/2014/09/04/the-failure-of-automated-recruiting/#368408b4a977 [Accessed 9 Aug. 2016]. ↩︎

  5. CultureIQ. (2014). Is Your Company Culture Affecting Your Reputation? - CultureIQ. [online] Available at: https://cultureiq.com/company-culture-affecting-reputation/ [Accessed 9 Aug. 2016]. ↩︎

  6. HR, C. (2016). Recruiting: 3 Ways to Improve the Candidate Experience | CEB Blogs. [online] Cebglobal.com. Available at: https://www.cebglobal.com/blogs/recruiting-3-ways-to-improve-the-candidate-experience/ [Accessed 9 Aug. 2016]. ↩︎

Subscribe to Another Dev's Two Cents

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.