> But in general, I think the idea of the whiteboard interview is a chance to see someone "think out loud", to see them reason through a problem. This is exact

> But in general, I think the idea of the whiteboard interview is a chance to see someone "think out loud", to see them reason through a problem. This is exactly why I do this kind of stuff as well when interviewing. It's not about syntax or the ability to recall (regurgitate?) a function, but how does someone approach a problem and where can the conversation go from there. If you sent someone pre-work to write an array matcher, you'll see a final result, but not how they think through it, and you'll miss potential queues to further the conversation.