Monthly Archives: October 2009

Learning About HR

Related to my last post about setting up an automated phone screening application, I thought I’d ask HR professionals on LinkedIn what they thought about they idea. As of now, here are some sample replies:

  • “The hiring process is already de-humanized why add more humiliation/ tortire [sic] to it”
  • “I can’t imagine interviewing my candidates via an automated voice system. It’s far too impersonal and I think many of them would find it insulting.”
  • “Quite frankly, if I were to encounter an automated pre-screening system like this, I would hit the off button before the first question is finished.”
  • “I wouldn’t feel comfortable in using a system such as you suggest. [...] A voice automated system might put off too many candidates to make it worth the investment to get to the qualified candidate a little quicker.”
  • “What kind of a person who is interested in Human Resources would use a machine to perform this work. This type of machine is ideal for checking on your packages and airline arrival time. People are not packages or planes.”
  • “Why on earth would you want to dehumanize an already stressed out sector of the population?! As an employer, I would never insult my potential employees by using a system as such.”
  • “As a recruiter I really strongly dislike this idea. I would never use it. And I think it adds another layer of torture for both candidates and recruiters.”

There are clearly some really strong feelings of revulsion about this idea. I especially enjoy comments that allude to yet another layer of torture, which seems to acknowledge that recruiting is already torturous. Also I think there’s a lot of speculation on how much people would hate it. I would like to find some job seekers who have been out of work for a while and ask them: “would you avoid working for a company that put all applicants though an automated phone screening process?” I think that if anything, an applicant will commit to 20-30 minutes of recording answers only for a job they really want, as opposed to the minimal investment in blitzing out your digital resume to 300 openings a day.

A Free Phone Screen/Interview App With Twilio

I have thoroughly enjoyed working with Twilio for the last 6 months or so on an open-source project that will soon be released (can’t wait!). Now that my part in that project has wrapped up, I’ve got some extra time to play around with my own projects and look for my next job. Over on the Twilio support forums, someone recently requested help, and it caught my eye:

I have to conduct a lot of phone interviews every year for my company with fairly standard questions. Would there be a way to use Twilio to manage this in an automated fashion? I don’t want to spend the time actually conducting the interviews but would rather listen to them when I have a chance. [...]
During the call, I would like to have the user enter the # sign or something when they have finished answering the question, to prompt the next question. This way, I could have my 10 standard questions recorded in Mp3, and then have the whole process managed through Twilio ideally where i enter the interviewee’s phone number and a time for the call ideally.

Someone posted a link there that lead me to this service: VoiceScreener which starts at $169/month. Yikes! Twilio, on the other hand, is 3¢/minute and $5/month/phone number. I got to thinking: this is incredibly easy to set up with Twilio’s API; why not just whip it up? So I did.

Here’s a demo where you can try a sample phone interview and here’s where you can download the code. To install and customize it, just follow these directions:

  1. Unzip the file to a directory on a web server that runs PHP 5
  2. Edit the file inc/config.php with your own Twilio authentication credentials and the email address that will receive reports.
  3. I have included my sample MP3 files in the files directory, but you should replace them with your own. The file names should be self explanatory: intro.mp3, thanks.mp3, conclusion.mp3, and question_XX.mp3, where XX is a two-digit number.

As it is written now, this works without any database at all because we can use Twilio’s REST API to query the call details and list of associated recordings. This project is more of a starter and proof of concept, although for simple interview scenarios it would work just fine. Other possible upgrades (some requiring a database) could be:

  • Account for unanswered questions in the report
  • Allow interviewers to hang up in the middle of the interview and call back later to pick up where they left off
  • Allow the interviewer to review their answer and re-record
  • Allow for question branching, where the user enters a touch-tone response for yes/no on some answers and is asked only relevant questions from then on
  • Set up multiple types of interviews
  • Show the text of the question in the interviewer’s web browser  while they are listening to it on the phone using AJAX
  • Make the interview conclusion a menu, as in: “To hear more about the company, press 1. To hear more about this position, press 2…”

If you are interested in having me work on this for you, please contact me and I’d be happy to help you out. If you have any suggestions or improvements, please send them my way too.