Earlier quoted context omitted.
Start with simple and fast screens, then progress to more fine-grained tests. A simple programming question will filter out a huge chunk of the candidates (i.e., those not smart enough to code or to cheat), then email screen, phone screen, and then an in-person interview. You should also figure out _exactly_ what qualities are most important in a candidate, and which ones you're willing to overlook. Generally, I test…
We'd love to talk to companies that use coding tests in the hiring process. Do they work? How well? Any insight into the design of good filters screens?
Vast hordes of candidates with err "augmented" resumes get filtered out, as do "experienced" programmers (sometimes calling themselves "architects" and such) who haven't coded in (literally) years.
I would have thought more people would look up the solution online , but apparently even that effort is too much.
So, overall I would say a coding problem is an excellent idea. I am not sure how valid is the "tell me your program letter by letter over the phone" approach yahoo, google etc seem to take in their phone screens.