The obvious reason for this approach to me is that Google is leveraging their reputation in order to solve difficult problems rather than actually looking to hire anyone. The answers this particular interviewer appeared to answer seem to be the kinds of things that a developer would want to know but might not be able to see the answer to.
The idea here that Google might be leveraging knowledge from a hopeful dupe, is echoed by their annual code challenges. The company wants to know things. It's hungry for knowledge.
My feeling that leading on applicants is the best way to be ignored when you need one because when you cry wolf, only the wolves answer the call eventually.
The idea here that Google might be leveraging knowledge from a hopeful dupe, is echoed by their annual code challenges. The company wants to know things. It's hungry for knowledge.
My feeling that leading on applicants is the best way to be ignored when you need one because when you cry wolf, only the wolves answer the call eventually.