I've been conducting interviews, we've experimented with adding some coding challenges and it's helped. Not live. But simple pass/fail write some methods to do

I've been conducting interviews, we've experimented with adding some coding challenges and it's helped. Not live. But simple pass/fail write some methods to do a thing. This typically will filter out brand new folks. But I do think you can have discussion, a technical interview back and forth - I'm talking details around guarding against nil classes, backwards compatible migrations, scale problems, real-world issues the interviewee has encountered. Types of tests they need. Maybe a situation where they missed a use-case. If they are able to articulate a discussion like this, I'm pretty confident I don't need to run them through leetcode doing BFS/DFS binary tree junk.