I&#x27;ve had my fair share of bad interviews too. Just recently I was interviewing for a full stack position with a company that tried to get me to recite &quot;what happens when I type google.com into my browser&quot;. I asked them where they had gotten idea from and showed them this: <a href="https:&#x2F;&#x2F;github.com&#x2F;alex&#x2F;what-happens-when" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;alex&#x2F;what-happens-when</a>. They decided ask me another question soon after.<p>Sometimes the questions aren&#x27;t even related to data structures or algorithms. I&#x27;m OK with those because at least you can somewhat prepare for them. I&#x27;ve once had an interviewer ask me obscure questions about Netscape 6 (this was 2016 btw).<p>&gt; I much prefer “homework” projects, even if they involve me working “for free”, because I feel like they ask for actual programming skills rather than the “guess the algorithm” lottery of phone screens and whiteboard coding.<p>Me too but when you&#x27;re interviewing with 3+ companies at the same time while working at your current job, it gets difficult. There was one time where I had spend my Saturday afternoon maybe 6-8 hours completing their &quot;homework&quot; project. I got a call back from them a few days later for a follow up interview and they flat out didn&#x27;t even bother to ask about the project I had completed for them. What was the point?<p>Tech interviews suck.