Am I the only one who, when being interviewed, doesn&#x27;t mind whiteboard coding?<p>At interviews where I&#x27;ve later been given an offer, it&#x27;s usually a relatively small algorithmic design challenge, where the specifics don&#x27;t matter, just the pseudocode.<p>In interviews I&#x27;ve given involving whiteboard programming, I&#x27;ve always emphasized that it doesn&#x27;t have to be valid or even semi-valid code for any language, just a semi-rigorous pseudocode expression of an idea.<p>I think, &quot;if done correctly&quot;, whiteboard coding is a good filter for those who can think algorithmically, who can catch the bugs that aren&#x27;t typos, but incorrect assumptions.<p>That said, that sort of mindset may not be what you need for your role. Need to consider that.<p>---<p>Tangentially, one of the better technical interview experiences I&#x27;ve had involved chatting for a while, the interviewer describing an actual problem they&#x27;d had (relevant to the role and the company&#x27;s product), and discussing my approach to the problem. (and passing or failing the interview wasn&#x27;t dependent on using the exact same approach...)