Don't read research papers. Get a TopCoder, CodeForce, Spoj, etc account. Practice with easy Spoj and Div2 TC CF first. Learn basic DS and algo and keep reimplementing until you can do it with your eyes closed.
As an example, I read a few papers on how graph coloring is used in compilers for register allocation and garbage collection,and could see some scope of an interesting discussion in an interview regarding intractable graph problems ...
Well, what are chances anybody is going to discuss it with you? Companies have process, the care if you fit in their process or not, meaning 2-3 coding rounds, design, architecture, behavioral. Unless those papers are super relevant for the role, like research role or machine learning or distributed computing etc and you applying for one, then I would say they are not super important.
Yup. You're right. A not so smart friend just bagged a killer offer in a company that had an insanely high bar,and attributed it to 3 months of Leetcoder. Just got the news.
comments
Companies have process, the care if you fit in their process or not, meaning 2-3 coding rounds, design, architecture, behavioral.
Unless those papers are super relevant for the role, like research role or machine learning or distributed computing etc and you applying for one, then I would say they are not super important.