Comments on: Revisiting the Technical Interview One of my former companies would give you a programming test that you had an hour to take, then use that as the basis for the technical interview. The correctness of the answers wasn't as important as the thinking behind it and the reasons for the answers (having the right answer always helps, though we still generally asked how they came to the answer for the same reasons). I thought this approach worked pretty well. Plus add on the standard questions about problems they have tackled and what they learned from it and it seemed like we did a pretty good job of picking candidates. One of my former companies would give you a programming test that you had an hour to take, then use that as the basis for the technical interview. The correctness of the answers wasn’t as important as the thinking behind it and the reasons for the answers (having the right answer always helps, though we still generally asked how they came to the answer for the same reasons). I thought this approach worked pretty well. Plus add on the standard questions about problems they have tackled and what they learned from it and it seemed like we did a pretty good job of picking candidates.

]]>