> You also have to understand data structures like linked lists, queues, b-trees..., and to top it all of understand algorithm analysis to judge the efficiency of the code you write or look at.

While it's true that you need to know how to judge efficient code, the bit about data structures is HR bullshit. If the only indicator about an organization's coding styles during the interview is a bunch of cargo culted questions from HackerRank, then you should think about whether you really want to work there or not.

Remember that hiring is a two way street. As much as you're offering them something, they're offering you a paycheck (among other things). Don't accept a bad deal just because their "innovative".