From the Other Side of the Interview

Part of my job includes interviewing candidates for developer positions (Flex, Java, ColdFusion, etc.). In the past two weeks I've sat through some of the most painful ones I can remember; not because of the candidates' skills, but their presentation.

Some examples:

1. One person came in with a one page resume. Five typos, including one in the title. They claimed to be great at communication and document creation. Uh-huh.
2. During one of the longer interviews, the candidate openly stretched and yawned as he formulated the answer to a question. Sorry to keep you awake.
3. One claimed to be an expert Java developer. I asked what a Singleton was. They are not an expert Java developer.
4. Another claimed to be an expert at Flex communications. I asked what an AsyncToken was. They are not an expert at Flex communications.
5. Yet another said they were a ColdFusion expert, but had not tried that new-fangled CFC stuff yet. They are not a ColdFusion expert.

So some gentle advice for those seeking employment from someone who's been on both sides of the interview table:

1. Spell-check your resume. Then get someone to read it over for mistakes. Then get someone else to read it over for mistakes. Then get someone else to read it over for mistakes.
2. Don't exaggerate your skill set. I'll see through it, as will any competent technical interviewer. And they'll likely be royally pissed if you wasted their time with any blatant dishonesty.
3. Watch your manners. I know it's a nerve-racking experience, but you're presenting yourself to people for the first time and you've got one shot to make a good impression. Something like an open yawn is offensive on many levels.
4. The interviewer wants you to do well in the interview. We want to fill a position and we hope you're the right candidate for the job. If you sense the interviewer does not have this attitude, think about whether this company is the right fit for you.
5. The interview is a conversation, not an interrogation. Ask good questions about the company and your future role. We like that. But also listen carefully to our questions and answer them directly. If you don't know the answer, then say so. It's easier to overlook ignorance than dishonesty.

Hope this helps somebody. Hopefully the next person I interview;)

Oliver