Thought I'd fork off from the "
Interviewing programmers" topic to provide a place for stories of how interview
ers go wrong--that's right, you were the one interviewing for a position, and the interviewer, well, you couldn't believe it...
Guidance:
- Hard or open-ended questions do not in themselves a bad interview experience make.
- Probably best not to reveal the identity or company of the interviewer in question; this is about bad interviewing technique or habits, not humiliation.
For example:
I was interviewing for a C++ position and the C++ "expert" put me through his little C++ quiz. No problem, except that he'd occasionally interject with some clearly false argument to the contrary. I learned as the interview proceded that he used to deal with his know-it-all students that way--by claiming falsehoods to be true. As the interview continued, it occurred to me that some of his "false knowledge" didn't appear to be game playing but what he thought to be fact. Annoying and weird to interview with a true know-it-all (who really doesn't).
(In the following months that I worked with him this behavior continued, often with him spouting something that was easily refuted either from memory or a quick web search. I pretty much gave up on listening to anything he said.)
Channel 10: Black Friday Deals on Windows 7 Machines
ASP.NET: Presenting in Europe Next Week
WindowsClient: You know your post rate has gone down...
Silverlight: Geek Profiles – Scott Guthrie
