Earlier quoted context omitted.
What is absolutely baffling to me is that companies assign coding tests as a pre-qualifier for the usual whiteboard interview despite the coding test being a far more adequate measure of the abilities of an engineer. I've had interviewers tell me that my coding samples went above and beyond what they usually receive (exhaustive docstrings, tests that make sense) and yet rather than discuss, say, how my code worked or…
> What is absolutely baffling to me is that companies assign coding tests as a pre-qualifier for the usual whiteboard interview despite the coding test being a far more adequate measure of the abilities of an engineer. A coding test doesn't tell you how well a candidate can collaborate. Can you toss them an idea, and have them successfully expand it and put it to use? Can you give them a couple of half ideas, and the…
My solution for this is a pair programming interview:
http://www.quora.com/What-are-the-best-programming-interview...
Like a whiteboard I'm there for everything that happens and can judge collaborative ability. And like a coding test, I'm seeing what people really do.
I may also do some whiteboard work, as being able to talk over an idea is also part of the job. But that's not in the "please do something arbitrary that you will never have to do in real life" vein. I try to make the whiteboard work as much like real work as possible.