treat it as such, then, and state it up front. i tend to introduce it as something like "a code question to see how you think" (or something to that effect).

treat it as such, then, and state it up front. i tend to introduce it as something like "a code question to see how you think" (or something to that effect). and then set the tone by asking a question that is simple on the surface, but people rarely get 100% right on their first iteration. they usually come to an acceptable answer somewhat quickly, and then i discuss it with them. that sets up a dialog for the other questions, even if the subsequent ones are more cut and dry types of questions. edit: in fact, almost all of my questions are like this. i rarely do stuff like a "reverse a string". reversing a string is somewhat trivial and doesn't provide layers or interaction. i prefer to have a question that allows me to see how someone thinks and interact with them to see how smart they are and how well we might be able to work together.