LinkedIn recently organized a recruitment process on our campus.
There was an online test lasting 90 minutes, featuring around 30 multiple-choice questions and 3 coding questions.
The multiple-choice questions covered Data Structures, DBMS, OS, and Computer Networks.
The 3 coding questions were of an easy level. I was able to solve only 2 of them, yet I still cleared the written round.
Next, the Skype interview commenced.
He asked about my field of interest and then began the interview with it. First, we discussed operating systems, covering topics such as paging, swapping, and virtual memory. Then, we moved to Computer Networks, exploring the differences between TCP/UDP, which is used in live streaming and paid subscriptions, and how connections are established between nodes. In Java, he inquired about the internal workings of the garbage collector, and finally, about how B-Trees function internally and the necessity of threading.
All the topics discussed were of my choice, and the interviewer frankly asked if I was uncomfortable with any of them. He delved deeply into each question, which at times confused me, and I had to change my answers. I was not prepared for what would be asked during the interview, so the whole session was awful for me.
This interview was to be followed by a final onsite interview in Bangalore. However, since I couldn't clear this round, I never received a call.
How the Garbage Collector in Java Works Internally?
The following metrics were computed from 8 interview experiences for the LinkedIn Site Reliability Engineer role in India.
LinkedIn's interview process for their Site Reliability Engineer roles in India is very selective, failing most engineers who go through it.
Candidates reported having mixed feelings for LinkedIn's Site Reliability Engineer interview process in India.