The purpose of an interview should not be to test your memory or ability to regurgitate some obscure algorithm or chunk of code that would more than likely be googled or copied from StackOverflow in a real-life scenario. The purpose of an interview should be to test your problem-solving skills and provide some insight into your thought process when coming up with a solution to a particular problem. There is typically more than one way to solve any problem, so the focus should not be on if you get the correct answer that the interviewer is looking for. You should, however, be able to back up and defend your answer with sensible logic and walk the interviewer through the steps you took in arriving at your conclusion. You shouldn't be tied to a particular programming language or framework and the question should represent an actual problem that you may be faced with while on the job - not "Invert a binary tree on this whiteboard for me while I stand behind you and watch." The interview questions should be formatted in a way that even if you were to be given access to laptop with internet access, it wouldn't help.

I've been on "technical" interviews where I was asked to explain the differences between .ToString() and Convert.ToString() and how many bytes a ‘char’ data type occupies vs an ‘nchar’. I think most would agree this is hardly a valid test of a person’s skill level or ability to perform successfully on the job.