[kaosmonk]

I'd suggest you rather talk with people you interview about underlying concepts and how would they approach and/or solve a real life use case/task/problem. Talk about their experience using this or that tool, IDE, alg, etc. Rather let them talk about their experience and then start going deeper with additional and specific questions about their experience in order to find out how well they understood the task they've been working on and how they researched and used certain toolset, why they've decided to go with certain approach, what were their thoughts about what they did once the task got completed, what would they change/improve etc. You may go as deep as needed with questions in order to see what areas does their knowledge spread across and to actually test how well they understand and know about certain topics that are of your interest.

I don't mind coding tests and whiteboard sessions myself but am finding coding tests not to be that informative on someone's knowledge since the implementation doesn't count as much as someone's understanding of what needs to be done and how well someone is able to grasp all the shortcomings of going with one approach vs going with some other.

At the end, it's always easy to google out the perfect solution to the problem (and/or quickly test several solutions in order to find the most convenient one for the given task) but if you don't understand underlying concepts and are not able to grasp what exactly you need to do no googling will help you with that.