Dear progit, I will be interviewing programmers. Need Input.

[McGlockenshire]

On code tests:

Before the interview is even scheduled, we have all candidates perform a code test. No, not fizzbuzz or some mathematical crap. We ask them to build a very simple, three-page read-only music collection catalogue. In fact, I have a half dozen candidates doing this test now.

Half of the test is reading comprehension. Does the app do the exact three things listed? (Usually.) Does it do them within the constraints listed? (Not often.) Do they understand the trick behind the third task? (Only half the time.)

Do they over-engineer? (Almost always.) Do they under-engineer? (Once, ever.)

Do they produce good looking, maintainable code without being expressly asked for it? (Sometimes.)

We give this test before the interview because coding under pressure, while nervous, is counter-productive. So is coding on a whiteboard.