The point of the interviews is seeing the value of a SW developer as a thinker and try to see their thinking process. Up to that point, I agree. However, not-so-complicated questions can be enough, and if interviewers try to make interviews more sophisticated, the interview degrades, in my opinion. Interviewers can ask an engineer for a way to find loops in a list, hoping that they find Floyd's "Tortoise and Hare" algorithm. Well, you either know the algorithm or you don't, but for sure you don't come up with it in 20 minutes (I believe Floyd himself didn't either). So are we measuring how the engineer thinks or how much they have prepared for the interview?