I've no issues with challenges during interviews. The problem is that it is hard to make good ones, so you usually get a question with poor specificity. The mor

I've no issues with challenges during interviews. The problem is that it is hard to make good ones, so you usually get a question with poor specificity. The more advanced the role, the more this is an issue. For example, you could explain a problem involving database lock contention and ask the candidate how they would handle structure, indexes and queries to maximise throughput and avoid deadlocks. Or you could give them an example schema and get them to "spot all the errors" without explaining that an error is anything that isn't in 3NF or higher. One is going to give you a good understanding of the candidate's knowledge of the subject, the other is going to give you a noisy true/false signal.