Chiming in to agree with you - where I work there are different coding competencies that are assigned per interviewer (e.g. good understanding of data structure

Chiming in to agree with you - where I work there are different coding competencies that are assigned per interviewer (e.g. good understanding of data structures and algorithms, good problem solving when dealing with ambiguity, knows how to write code that's readable/maintainable/extensible for future use cases without overengineering, etc). I explicitly tell the candidate what I'm looking for at the very start of the technical portion of the interview. I'll say something like "this is a difficult problem and you might not finish, but that's intended since I want to see your problem solving skills", or "this problem is meant to be a little simpler so don't overthink it, I'm focusing on how you structure your code to be readable and easily modifiable if we want to change behavior or add a feature". I suspect that knowing exactly what I'm evaluating, instead of thinking they need to excel at everything, takes a bit of pressure off and allows the candidate to perform better.