It&#x27;s very important to understand three things about (tech) interview process:<p>1. Hiring at scale is a VERY different problem from hiring slower.<p>When we were looking for 25 engineers a quarter at Box or eBay, there were very few methods that would scale to that level. Asking data-structure&#x2F;algorithms questions is one method that scales. Is it perfect? No. Is it the least evil? Yes.<p>2. An interview is not a test; it&#x27;s a date.<p>Interview depends on the interview-er, as much as it depends on you. You may be fully prepared, but you may still fail interviews for no fault of your own. Just the way you cannot expect to get married with everyone you date, you cannot expect to clear every interview. The more you think of it as a test, the more you will agonize about it.<p>3. You have to prepare<p>Tech salaries are at peak these days. People on the other end know that. As a result, they are <i>not</i> going to give an easy interview. Especially true of hot companies. This is also the artifact&#x2F;reason why it feels that most good companies are discriminating.<p>[About me: I&#x27;ve seen this machine inside and out from all ends, many times over. I now run a bootcamp to prepare candidates for technical interviews: <a href="http:&#x2F;&#x2F;InterviewKickstart.com" rel="nofollow">http:&#x2F;&#x2F;InterviewKickstart.com</a>]