The technical interview

Phlegmak

Deity
Joined
Dec 28, 2005
Messages
10,966
Location
Nowhere
I have reached the point where I now believe that long technical interviews are close to useless. It's perfectly fine to have a short technical interview where you can tell if a programmer actually knows what he says he knows or not. This should take no more than 20 minutes. However, I have had extremely long (6 hours at Lehman Brothers) technical interviews which are nigh useless. I answered your first 30 questions mostly perfectly, you should know if I'm qualified already or not! Stop torturing me! Also, programmers, such as myself, shouldn't need to memorize every single thing. The internet exists for a reason, other than wasting time on forums. And that is that it is the greatest source for technical documentation in existance. So what does that mean? If I don't know something and I have to learn it, I simply google it, learn it, then do it. These technical interviewers that have multiple hour long interviews have lost sight of this in a really bad way.

Moronic response, noted here to help ensure no one says it: "The internet is for porn!"
My response: "Wrong."
 
Indeed. We recently had a position opening and I assisted with technical interviews for four candidates. I got what I think was a good sense of the candidate's level of technical abilities (relating to my area) on roughly 30min of questioning.

Six hours is just crazy.
 
Top Bottom