The best way to interview someone is to give him a block of broken code and ask him to fix it (nothing that shouldn’t take 5 minutes for someone who knows what he is doing) AND a white board pseudo-code problem to solve.
Whenever I interview and someone asks me an obscure C# function my standard response is “I never used it, are you using that?” Followed by my own questions I like to keep handy about obscure C# info
Good technique. I shall remember that. I have had many interviews where the lead programmer had a vexing problem and asked me the subject matter (in the effort to catch a clue on the problem). When I detect that, I borrow from an old commercial, smile, lean back, and say “Hire me and I’ll tell you.” :)
I hate whiteboard coding interviews. Enough that I’ve taken a sub-notebook computer with me to interviews. One in particular: they asked me to write some code on the whiteboard, knowing it would take some time; I popped open the computer and Eclipse, told them (several people at once) to just continue the interview while I coded. Fielded four lines of questioning and still had running code in 10 minutes. Got the job (turned it down).