We may be just using different definitions for what it means to prepare / know the solution. Most of the “thinking through the problem” in my experience is mapp

We may be just using different definitions for what it means to prepare / know the solution. Most of the “thinking through the problem” in my experience is mapping the problem to a known class of problems which you have tools for. This is what software engineering is often, making entirely new and untested patterns is rare in my experience (and if it isn’t that could be indicative of an opportunity for improvement). And someone who has studied more will have more examples to map it to, and will likely do so faster. Disregarding a candidate because they have more examples and recognized them faster than someone who had to work through it from first principles is disregarding a candidate who will often provide you an industry standard solution for one who may be unaware someone has solved this problem already. It also seems to be an unrealistic goal, since most engineers I know who do work through things from first principles don’t do so with observers on a whiteboard in 45 minutes.