The particular thing I like to test in an interview is "How are you at communicating something that (should be) in your wheelhouse -- Asking questions, explaini

The particular thing I like to test in an interview is "How are you at communicating something that (should be) in your wheelhouse -- Asking questions, explaining your thought processes, discussing tradeoffs, etc". For a recent graduate of a CS program, that's probably "Solve a data-structure/algorithm based problem". For anyone who isn't a recent CS graduate, there's probably a better question to ask. Mostly what I'm going for is: (1) How does the candidate communicate something they know that others might not. (2) How good is the candidate at what they claim to be good at, for the purposes of calibrating their resume. People have cargo-culted an interview process from a time when developers were largely CS majors hired somewhere out of undergrad, and then stayed at one large company for a few decades, often because it is what they went through. But this process doesn't translate to mid-career or non-CS-major hiring.