I've interviewed lots of developers and recommended 'hire' to about 15 people in the last several years and not once did we get it wrong.
All it takes is a short problem to solve at home, which can be easily googled and one hour architecture interview, where we discuss the technical architecture of a hypothetical 'real world' service.
It takes about 20 minutes to determine if the candidate has the experience with the technologies listed in the resume.
Little experience is not necessarily a show stopper.
True that the language we hire for (Clojure) filters out a lot of people ahead of time, but knowing the language is not exactly what I look for..
What I look for is 'passion' - does the candidate love programming and can the candidate articulate technical issues with ease.
The other question I try to answer - will the candidate enjoy working in our team and will we enjoy working with him/her.
Smart people will shine in a certain way, even if they bomb specific questions - they have an opinion, they try, they ask the right questions.
I'd be sad if we missed on some of the people in our team because of automated (inhuman) puzzle interviews.
We're not looking for a problem solving machine, we're looking for a partner to create something great together, someone who shares our passion for hacking and someone who we'd love to work with.
I share TFA's opinion that leetcode-style interviews are not the way to go and I hope the industry comes back around and focuses on the human side more.