That's really his one question he'd ask to someone working in R&D, and writing code?
How about asking somebody about the problem domain he'll be addressing? Past experiences on that field, or related fields?
Recognising bad code might be nice, but I'd pick someone with 20 years of real and relevant experience over someone just new that can say "whoa, that looks like bad code!"