[jaffoneh]

Thanks for pointing out this from the point of view of someone who conducts interviews. However, let me address your points:

1) I absolutely understand that "thinking out loud" is just a way for the interviewer to know how I think. The problem with that, however, (at least for me) is that now I have two tasks a) to write code and b) to tell what I am thinking without saying anything wrong. I know that it is ok to say something wrong, at the end, you don't get the answer immediately but I am under pressure to show you my best and that what comes to mind.

2) Maybe I didn't show that clearly in the post but I do think it is ok to ask technical questions, I just think you need to also give the interviewee a chance to tell you more about who they are, what projects they worked on, and what kind of technologies they applied. This is essential for many reasons including a) it gives me the confidence before the technical question, b) it tells you a little bit more about what I am able to do, and c) it gives you a better understanding of the interviewee since the question you just asked doesn't tell you enough about me or my talents (in my opinion)

That has been said, you raise some good points. Thanks for taking the time to reply!

[MattLaroche]

I feel for you. I have failed a few interviews; I choked in the interview because I didn't simulate the interview environment in practice by whiteboarding and talking through problems alone. I recommend you read Steve Yegge's post about interviewing at Google (http://mlaroche.blogspot.com/2011/10/algo-interviews-are-ove...) - especially with regards to smart people having bad days interviewing. When I realized I'd make mistakes at interviews and still actually be a good person and good hire, I stopped choking and I stopped grasping at straws on interviews.