The hiring process was long, lasting over a month. It included:
I referred to previous interview experiences on Glassdoor, which helped me prepare, as the questions were mostly similar. I initially received a rejection email after the first round but was then called for the second round. They never answered when I called back, which I felt very bad about.
The first round was based on networking. TCP/IP, ARP, DNS resolution, sharding, scaling, caching, and server management concepts were covered.
The second round was scheduled only for Linux memory management. Entire memory management questions were asked, including how it works, why it is required, virtual memory, swap memory, swappiness, and more.
In the code review round, I was given three codes and had to find bugs. One was for storing backups, the second for parsing logs, and I don't remember the third.
System design was okay. They presented situations and asked how to design a system in those scenarios. I was allowed to ask questions to check if I was on the right track.
The last round was troubleshooting. There was an Apache server, and I had to debug it. It had 500 and 400 errors. I wasn't able to solve any in this round.
The following metrics were computed from 1 interview experience for the LinkedIn Site Reliability Engineer role in New Delhi, India.
LinkedIn's interview process for their Site Reliability Engineer roles in New Delhi, India is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for LinkedIn's Site Reliability Engineer interview process in New Delhi, India.