The questions dont require google; but what do you do when you don't know a specific thing? You search for it.
The notion that a candidate must remember the name of a thing or a specific algorithm is just ridiculous. When was the last time you implemented some fancy sorting or tree traversal algorithm from memory?
and if a guy thinks he's able to parse that amount of information in less than a minute, why should I refuse it? The end goal is to hire problem solvers, people with analytical thinking and capable of learning autonomously.
In most companies, the development process is collaborative - spikes, code reviews, informal meetings; why would you evaluate a candidate for such a team solely on what narrow knowledge he brings to the table when the power is down?
The notion that a candidate must remember the name of a thing or a specific algorithm is just ridiculous. When was the last time you implemented some fancy sorting or tree traversal algorithm from memory?
and if a guy thinks he's able to parse that amount of information in less than a minute, why should I refuse it? The end goal is to hire problem solvers, people with analytical thinking and capable of learning autonomously.
In most companies, the development process is collaborative - spikes, code reviews, informal meetings; why would you evaluate a candidate for such a team solely on what narrow knowledge he brings to the table when the power is down?