Last week, I posted 7 interview questions for C# programmers. I guess I forgot that people can’t see in my brain. So, let me be very explicit this time. The “weed out the losers” questions are meant to do just that. Weed out people who have absolutely no business even applying for the job.
You would be amazed at how many people interview for a job who have all kinds of cool buzzwords on their resume, but when you ask them about it, they know nothing about the subject. I’m not sure if this is the recruiter who is representing them trying to help them out by beefing up the resume to get them in the door or if they actually do this themselves. But, as someone who interviews, I have to have a way of making sure the applicant I’m interviewing is worth interviewing in the first place. Hopefully, I can do this over the phone in less than a half an hour.
So, with that said, if your favorite question isn’t on this list, it is probably because it is a question I would save for some future interview.
Also, to those of you who may think that a technical interview doesn’t really tell you if the programmer is a good programmer or not, I have this to say…
You are right. And when I was a younger programmer and was being interviewed with technical questions, I felt the same way. But now that I’m on the other side of the table, I find that way too often, the people who can pass a technical interview are a lot more likely to be good programmers than the ones who can’t.
And finally, I would not rule out an applicant because he got a couple of questions wrong, or didn’t answer them exactly the way I expected. But if couldn’t answer most of them, that would raise a huge red flag!