So long as those algorithmic challenges are actually in-use. Warranted. If it's just to flex that last little bit of grey matter, not warranted. The issue is software complexity is such a spectrum that so too must the interview process. No standard "developer 101" interview exists because each company has different software needs. An entry-level exam at Google will look different than an entry-level exam at Dunder-Mifflin. I think better expectations and better communication are the way to have successful (and meaningful) interviews. Yes, code test and all that but you should formulate the interview so that it gives you a good understanding of what they would be like to work along-side. I agree though with what you said.