in reply to Interview with a Programmer

Actually, at my company we prefer more complete answers. We often give detailed scenarios and ask how they would go about solving the problem. We also give them a 50 question test covering much of the basics.

The QA session should get their blood running enough to show their enthusiasm. We do put them through a lot, but we are very nice about it. If they don't like it, then they won't want to work for us and we can move on to the next prospect.

It's also important to note that we begin serious QA over the phone, before they ever come down. You can eliminate much of the 'lies' and 'exaggerations' before you waste a lot of anyone's valuable time.

Replies are listed 'Best First'.
Re^2: Interview with a Programmer
by joseph_porter (Initiate) on Dec 27, 2008 at 07:17 UTC
    If you're trying to prepare for a programmer interview, check out: http://www.programmerinterview.com/