I feel this is just catering to a major problem the industry has with interviews.<p>Interview questions are largely irrelevant to the main job. When was the last time you needed to code from scratch a mergesort in your job? A binary tree? A LinkedList?<p>Sure, there's <i>some</i> value in asking those questions - can they problem solve, can they communicate their solution effectively, etc... I just think there are way better ways to find out whether a candidate is suitable for a job than to ask them to code up an algorithm they haven't had to do since CS 101.<p>The kinds of technical questions I find more effective are:<p>* How does a cache work?<p>* When would you use a HashMap/Dictionary/Hash/Object over an array/slice/collection?<p>* How would design an HTTP API to do X<p>* How would you design a database table to do Y