I found this quite amusing having read about many tech job interview questions here and around the web.<p>Back in my junior days programming interviews were more about finding subtle syntax errors in some snippet of code you would never imagine writing. At the time many argued this is what compilers/IDEs are for.<p>It seems these days it's all about regurgitating computer science algorithms or something similar. Again many argue this is where you'd leverage an existing library. If one didn't exist you'd perhaps spend some time researching + testing your implementation. Quite a different environment to a time constrained interview with someone waiting to see you trip up.<p>I feel there's also a bit of a catfishing element going on here. If you pass the interview having nailed the inverse binary tree problem; you might expect the role to be just as intellectually challenging; what you find might be very different..