[loumf]

What if I told you before you came in that we'd be coding on whiteboards. That my expectations were calibrated properly for that, and that the problems would be "white-board" sized.

I've done this -- had people talk to me about their anxiety or problems with it, and put them at ease. For some, I have recommended that they just go practice of an hour or so with a friend -- it's really not that hard to code "whiteboard" level code if you code every day and practice it a little. It's such a common tech interview style, that if you are looking for a job, it's worth working a little at it.

Frankly, in a code-editor, my expectations are much higher -- I don't even require you get any framework class or method name right (or even perfect syntax) -- but the compiler will. It gets in the way of the essence of the question -- which is more about collaboration.

[rimantas]

So instead of not doing a stupid thing you still do it but just warn people in advance and even tell them to practice doing that stupid thing, even if it will not be a part of their job?

[loumf]

I don't think it's stupid, but I do think you shouldn't be surprised by tech interviews.

This is for a screen to make sure you are a programmer. If you can't code up a four line function without an editor, there are going to be a lot of jobs you might like that you won't get. Ditto with calling strangers stupid.

[Florin_Andrei]

Advertising it beforehand does not make a stupid thing less stupid.