When I interview someone about design problems, I'm most interested in their approach to decomposing the problem and their ability to express their thoughts and

When I interview someone about design problems, I'm most interested in their approach to decomposing the problem and their ability to express their thoughts and keep a track of their ideas as well as interact with me. In a way, you're almost looking at the interviewee as a teacher except they're obviously having to improvise on the subject at hand. I'd suggest the best practice is to understand the structure of software you're interested in and write about it.