Dipesh Majumdar

Blog and Paintings

See your resume from the recruiter's perspective

February 28, 2012

Recently while screening through a few candidates' resumes, I stumbled upon one interesting observation. I saw most candidates try to include as much technology as they can in their resumes.
The job seeking candidate thinks this will create a good impression on the interviewer.
For example if he works in java, then he also mentions oracle, mssql under database, linux and windows under operating system and so on.

His stance - "I write code in java for the front end application that interacts with the backend database (oracle and sql server) and the whole thing resides in windows and sometimes in linux OS. So it makes sense to mention all these components in my resume."
Consider a while from the recruiter's perspective. The confusion starts with the panel which does the initial screening and categorizes the resumes according to technology. HR remains confused as to which interviewer the resume should be given to. Then the interviewer is confused in deciding the questions to be asked.
Then undecided, the candidate is called and asked - "Which area are you strongest in and you intend to work?" Soon the interviewer finds that the candidate is actually a java guy.
The resume is then forwarded to a java specialist. Then the actual interview starts.
Ambiguity in resume breeds wastage of time, confusion, irritation and lots of negative impression. Ambiguity is seen as a means of hiding ignorance. Had the candidate only mentioned about Java and showed in the actual interview that he also knew a few things about the back-end database then he would have created a better impression.
The key is promise less and deliver more.

Go Back