There are several articles on the Internet for effective head hunting, covering many basic tips. This article discusses subtle points which are often overlooked in IT recruiting, yet play an important role in improving your chances of finding the right candidate.
The first email should be carefully crafted
An email can be seen as two parts. The subject line and the contents. The subject gets the reader to open the email, while the content plays a part in the decision to pursue it further.
When posting a resume gets 10-20 emails a day, getting a candidate to read the email is not very easy. The subject becomes important; be very specific. A good subject could be – “Oracle Admin in XYZ company (Bangalore)“, or “Project Manager, for a UK Assignment“. BAD subject lines are plenty. “TOP PAY MASTER – CALL FOR YOU“. “This is a very urgent opening for Java Professionals“. Avoid weasel words like “excellent”, and those such as “urgent”, “critical” in the subject, and content.
The contents are equally important, in generating interest. Simple emails, explaining the job position and requirements are always better. It is important for the mail content to be free of typos and be grammatically correct. In our analysis, more than 50% of a sample of 600 emails had grammatical or spelling mistakes.
Another common mistake is to litter the email with different fonts, colors and font-sizes. Choose simplicity, and minimal variation in fonts and colors. You could use bold fonts to emphasize key points, and everything else could be just normal text. Simplicity, like Google.
If you are mailing a candidate individually (instead of mass mailing), include a line on why you think the profile is a good fit.
While telephoning the candidate
Candidates with good language skills can make interviewers overlook technical deficiencies. There is nothing wrong with this, since a large part of the work in an IT Services company involves communication with customers.
If you are asking the candidate for references, immediately follow up with an email mentioning the job profile, your contact details, and a single line of appreciation. People are too busy to remember phone numbers and pass it on. To save time, use a standard template for such emails.
Are the required skills really REQUIRED?
Sometimes when Teams or the Technical Division hands out requirements, they mention all technologies and libraries used in a certain project for which they are seeking candidates. Ideally, one should only mention the basic qualifications, like exposure to a fundamental and core set of technologies (eg: J2EE, Struts and Oracle, or Asp.Net and Sql Server).
There is no point in mentioning the items in bold as a required skill:
.NET, HAF, EIRG (Rapidigm), CSLA (a real example)
There are hundreds of such libraries in the wild, and you need just a day of reading up to get started with them. The idea here is that a candidate who can learn them quickly is a lot better than an idiot who has used them at some point. When you see absurd requirements like this, discuss it with the person who gave those requirements and ask them if they can be learned.
In just about every situation, you are looking for an intelligent guy who knows some basics.
Choose a fair Interview Panel
Avoid egotistic interviewers from the panel. It is important to gauge the technical proficiency, as well as his/her capability to accept different views and suggestions. An adamant, narrow minded panel will not only cause the candidate to walk away; it will also bring the organization to disrepute.
In one of our surveys with job seekers, they rated top irritants with Interviewers (technical):
- Focusing on minor technical details, and not the ability to learn
- Assuming there is only one way to do it
- Programmer Ego!
Observe, don’t just See
If you were in this profession for a while, you would have short-listed thousands of profiles. You may also have a statistic on the number of candidates you placed. But there are other little pieces of information you can identify:
- Do you know that more people post their resumes on Wednesdays, followed by Thursdays? – A logical explanation for this could be that people tend to become frustrated by the mid of the week, due to work pressure and friction. So, Wednesdays and Thursdays are when you can expect more candidates. (In our samples, we found that resume updates on weekends were 70% lower than on Wednesdays).
- Among experienced candidates, many of them update their resumes on weekdays. But better candidates do so from home, late in the night on weekdays or on weekends.
This helps in deciding when to search the databases for new resumes. And perhaps, analyzing the behavior of the system can improve proficiency in a job. You may have noticed many such things, please share them with the readers as comments.
This is the first installment of a three part series. Stay tuned for more.
Meanwhile, if you are a recruiter you may also want to take a look at some resumes for recruiters.