Why don’t those guys call me? These tips provide the necessary information to make a favorable impression the next time you interview with a contracting agency.
So you’ve done your homework and settled on a couple of agencies to help you find contract work. You’ve made your initial contact, and your “exploratory” interview is scheduled at their office in two days. This interview is your chance to tell them exactly what you are about. Just listen to me, and I’ll show you how to have them eating out of your hand!
Let’s do some role-playing. You are David or Debbie, the Dashing Developer, and I am Wade the Technical Recruiter.
Before the interview
You need to do some soul-searching. You must determine (and later explain) exactly why you are interviewing. My objective in interviewing you is to find out the following:
Your availability profile
I will probably ask you these questions very early in our interview. If you are not available when I need you, there is little point in going further. Keep in mind, these questions are examples only, and are in no particular order:
Sound like a lot of questions? You bet. These are things that a recruiter will need to know when deciding whether you are worth calling when jobs need to be filled. Be prepared to answer them.
Your hard skill set
This is the part where I ask you to brag about yourself. Here are some example questions:
My point is that you should come to the interview prepared to discuss all your skills—I may ask about them in detail! Paint me a picture. Don’t just tell me you designed a database for a school. Tell me what it did, who used it, why it was needed, and how happy the principal was when you showed him what it would do. Use proper names for products and languages you used.
Ultimately, I need to turn around and sell your skills to a customer, so I need to see how your experience is perfect for other jobs. Don’t lie, but don’t be shy. This is not pass/fail. I will ask for details, but my true goal is not to catch you lying—I just want to see what types of work you are comfortable with and would enjoy. Remember: This is why they call it an “exploratory” interview. The technical stuff comes on another day.
Your (gulp) interpersonal communication skills
Although they’re not the most critical skills for a programmer, IPC skills are certainly not to be overlooked. Many geek types choose this career precisely because they don’t like dealing with others. Unfortunately, in the job market, working with others is a necessary evil, and my job as a recruiter is to see if you can do it. I am not looking for a smooth-talking public speaker; all I really want to know is whether you can listen attentively, speak concisely, and form grammatically correct sentences.
Just remember these three points, and your IPC skills will be shown in their best light:
Summary
To recap, a technical recruiter uses the exploratory interview to determine when you are available, what kinds of jobs to offer you, and how well you communicate. There is no hidden agenda. The more honest detail you can give about these things, the more comfortable a recruiter will be about calling you soon for a job.