&gt;There&#x27;s a difference between being able to come up with a solution in 1 hour vs being able to come up with a solution in 1 hour on a whiteboard, with no internet access, and with someone breathing down your neck the whole time.<p>You can usually fit about 15 lines of code on a whiteboard which tends to bias questions to simple logic questions. Why do you need internet access? Also why does someone have to breath down your neck? They could leave you alone for 45 minutes and come back.<p>&gt;Otherwise, I feel you&#x27;d be better served by an interview that more closely emulates the actual working environment that your employees work under.<p>Why do you feel this way?<p>I think that programmers should have as many programming related patterns memorized as possible - For e.g. How to compose different kinds of programs when given different resource restrictions, or having basic algorithmic concepts in their head so they can quickly choose one over the other. A programming test should immediately indicate if the candidate has such things on the tip of their tongue or not.<p>In much the same way as you don&#x27;t open a high school physics textbook when you go about building an airplane, you don&#x27;t want someone who has to google basic programming knowledge that they should just have in their head.<p>IME, when you start with a very high level of intrinsic knowledge it&#x27;s much easier to make connections and come up with unique solutions, because your not constantly &#x27;searching&#x27; for things. Instead you&#x27;re just &#x27;picking&#x27; the right building blocks. Or maybe trying to quickly eliminate obviously bad choices. Ofcource there is much more nuance, but you can&#x27;t state everything in a single comment ! :&quot;)