You were replying to me, but I agree 100% with all of that, and it doesn&#x27;t contradict anything I said, so I&#x27;m not sure what else to say.  I guess I could just be more clear in saying that, for me personally, I&#x27;m not &quot;complaining about hard computer science problems&quot;, I&#x27;m just thinking about how to optimize use of time.  Personally, whether I&#x27;m the interviewer or the interviewee, I&#x27;m not partial to interview processes that take all day.   That and I&#x27;m not partial to asking people to implement difficult algorithms on the whiteboard.  My take is this:<p>1. If you&#x27;re doing whiteboard stuff, keep it high level, see if the conceptual understanding is there, and move on.<p>OR<p>2. Give the candidate a computer, editor &#x2F; IDE, compiler, google, etc., and let them work they way they work, implementing $WHATEVER.