[RobertWild]

MWittman: Amusing list. Funnily enough, they are questions that have been asked of the Google Answers team

Peter: Barbara's list is a good one.

Try to ask a mix of the following:

Technical questions of various difficulty levels with definite answers (Tests knowledge)

Eg: What's the difference between a relational database and a flat file one. Give an example. (You wouldn't believe the number of "database people" who have no idea of this.)

Technical questions of various difficulty with various optional answers (Tests Problem solving creativity)
Scenario questions of conflicting demands (Tests prioritisation skills)

Also, 1 or 2 really off the wall questions - this is not intended to get a right answer, it's more intended to show you an applicant's thinking process about how they would find a solution to a problem that they have no idea on. Chances are, if there is an interviewing team, you will need to warn them of what you are doing.