&gt; By the time I get to the whiteboard stuff, I&#x27;m looking for someone to want to engage with me, not an attempt to stump them.<p>Dredging this comment, because while this article is not about whiteboard coding, it would inevitably be mentioned.<p>I think many people, including many interviewers, completely miss the point of whiteboard coding.  I think this article needs to be shared: <a href="http:&#x2F;&#x2F;darrenkopp.com&#x2F;posts&#x2F;2013&#x2F;04&#x2F;19&#x2F;Post-mortem-of-my-failed-interview.html" rel="nofollow">http:&#x2F;&#x2F;darrenkopp.com&#x2F;posts&#x2F;2013&#x2F;04&#x2F;19&#x2F;Post-mortem-of-my-fai...</a><p>The key point is that the interviewer is, or should be, a friend. He should not be out to stump a person or out to get him; he should genuinely want a person to succeed at the interview. If not, it&#x27;s better just to reject the person outright.  White board coding should be seen as a way for person to engage in collaborative problem solving, which is something that we do on a daily basis.  Can you explain your thought process? Can you admit your stuck? Can you have an intelligent discussion about your solution, listen to feedback, etc.  The problem should be challenging and relevant, but it should not be a test of coding skill.