Lessons learned from the recent job hunt
&gt;Firstly, I&#x27;m really glad to say that the interviews I did were not the stereotypical tech interviews. As an industry, it&#x27;s great to see we&#x27;re getting better, and moving away from whiteboard coding, dealing with super abstract problems like inverting a binary tree, or doing things that we&#x27;d generally just use a Search Engine for in our real jobs.<p>I would expect a junior developer out of college knows data structures and algorithms. That includes knowing what a binary tree is. And if you know what a binary tree is, it isn&#x27;t terribly difficult to invert it.<p>Why shouldn&#x27;t a &quot;senior&quot; developer know what a binary tree is?<p>While I don&#x27;t have much regard for leetcode and hackerrank, I wouldn&#x27;t want to hire someone who doesn&#x27;t know about algorithms and data structures and thinks he can solve anything with Google.<p>Sure, many thinks are solvable using Google, but many require knowledge, experience and practice.<p>&gt;Unfortunately one company - who outsourced the first part of their interview process - had something similar to this, which I wasn&#x27;t impressed with. There were some arbitrary questions around several topics, and then in the coding exercises you were asked what the O(n) complexity of time&#x2F;space were.<p>The author is even outraged he was asked about time complexity, something even junior programmers shouldn&#x27;t have a with.