&gt; Am I the only one who, when being interviewed, doesn&#x27;t mind whiteboard coding?<p>I&#x27;m sure you&#x27;re not, but my experience is completely opposite of yours. I&#x27;m still relatively early on in my career (I&#x27;ve had 3 software jobs, but have grown up coding since I was 12), but every job I scored was one that didn&#x27;t use a whiteboard&#x2F;paper problem during an interview.<p>I got a lot better at whiteboards with practice; but early on, every whiteboard problem I received resulted in me blanking on even the most basic concepts. I would have no idea how to solve problems on a whiteboard that I explicitly solved in a codebase the week prior. Then I&#x27;d step out of the interview and the solution would just hit me.<p>It&#x27;s like state-dependent learning, in a way. As I got tested more on whiteboard coding, I figured out that whole problem-solving process better, and I do pretty well on them now. Still, I continue complain about those problems. They feel like a completely foreign, perpendicular challenge compared to having a discussion, answering questions, or writing code to solve the same problem. It&#x27;s not a skill I&#x27;ve ever used outside of interviews, nor is it a situation that has ever been simulated at any workplace I&#x27;ve been at.<p>There&#x27;s nothing wrong with evaluating a candidate&#x27;s whiteboard presentation skills. If the goal is specifically to evaluate technical or algorithmic knowledge, it&#x27;s worth taking into account that testing for that knowledge on a whiteboard can introduce a side-effect that bottlenecks the candidate&#x27;s ability to present their answer.