> I've tried everything and I've had the best results by talking, digging into the details. That's always the second interview I do: "tell me about your favori

> I've tried everything and I've had the best results by talking, digging into the details. That's always the second interview I do: "tell me about your favorite project", then asking questions about details, possible alternatives and pros/cons, fundamental limitations, anticipated issues, real production issues, etc etc, going as deep as possible. This works really well and filters out people who do leetcode but don't pay attention to details in their work or have no real experience (if you're looking for one). However, the couple of times I hired people who nailed this part but failed the coding, they also failed at coding at work. So both interviews are necessary in my opinion.