A. Pagaltzis wrote:
Or better yet, ask them to bring along some limited-size chunk of code they wrote; not too trivial, not too substantial. Tell them you expect them to discuss any aspect of their choice about this piece of code.
The traditional approach at my workplace is to send out a test to everyone who makes it to the interview shortlist about a week prior to the interviews. Five questions at most, all asking to have a specific (and hopefully relevant to the position) problem solved along with a few thoughts on the approach taken.
This means there's code to look at for all the reasons you cite, but it's always answering the same problems so there's a relatively level playing field for all applicants.
The last few rounds have involved one question asking to implement a simple HTTP server in C (redirect any request to slashdot.org), some perl to do some sort of text processing, and some SQL related to a footy tipping service. Smartarse answers are acceptable, the point is to have something technical to discuss in the interview.
I believe management is moving away from this now as it is seen as helping to perpetuate a technical culture they don't like.
Matt
