You need to do a better job pre-filtering candidates. You are not doing your company a service by letting down a bunch of people over and over. I have a rule:

You need to do a better job pre-filtering candidates. You are not doing your company a service by letting down a bunch of people over and over. I have a rule: Code samples or OSS contributions or it is an auto "no-interview". Even for first year co-op students. From the code it self you can usually judge competence. If the code samples pass most of these http://en.wikipedia.org/wiki/Code_smell http://en.wikipedia.org/wiki/Code_smell then I bring 'em in for an interview. I have yet to meet someone that doesn't know what the difference between a GET and a POST. For me a bad interview is if someone doesn't know what types of things are found in the headers, or doesn't understand the basics of oAuth. Before people come in here and start up with the "you are not mid-thirties with kids" BS, no I'm not. But I know plenty of people that are, and it isn't too hard to get 200 lines of code to someones inbox.