I ask people what tools they use, how they code, i.e. do they use DreamWeaver, BBEdit, emacs or whatever. Assuming they don't just give a one-word answer, you normally get some kind of idea what their priorities are, how they code, etc.
Then I ask how they validate their code, which is always interesting.
Aside from actually testing them by having them sit down and hammer out a page, I would ask them for specific examples of work they've done, how they've resolved an issue.
For instance, you say "tell us about a job where you were on a strict deadline" or you say "tell us about a really frustrating problem and how you overcame it" or "in the work you've done recently, what's the thing you're most proud of?"
That way you get a lot of insight into the kind of thing they've done, their problem-solving skills and experience, the way they handle stress and frustration, and of course, whether their workarounds/corner-cutting measures are smart or dumb.
