Rather than just asking the candidate a few questions, I prefer to give them a task and a set time to do it in. The tasks that we use here (obviously I can't tell you what they are) test that he has sufficient clue about data structures, algorithms, and the language. We do *not* expect anyone to finish any of them, but can get a great deal of information by seeing how far they got and how they approached the problem.
The code they write can often lead to some quite interesting discussions.
In reply to Re: Evil Interview Questions
by DrHyde
in thread Evil Interview Questions
by kyle
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |