It really surprises me how many companies will do an "algorithmic interview" and hire a developer that doesn't actually know what they're doing at the actual job. As many have already answered here, a conversation-style interview is way more effective. Ask the candidate real world questions, and about projects they've worked on in the past. If they're struggling on a question, have them talk their way through it and see their thought process on how they'd go about solving it. It's perfectly valid to answer with "I'd probably Google how to do ____ and then check the documentation for ____" because that's how most people realistically work. The most important thing is how willing they are to learn and figure out new problems, rather than how many algorithms they've memorized.
Jason Knight
The less code you use, the less there is to break