The process started with an online coding challenge.
It had three coding questions around LeetCode medium level, one DBMS query, and around 20 MCQs involving Networks, DBMS, Linux, etc.
Following that, there were two technical interviews and one hiring manager round.
The first technical interview was a Service Architecture round, where I was asked to scale a ride-hailing application to handle about 10,000 requests/min. It was a 1.5-hour round.
In the second interview, I was tested a lot on Data Structures, Networking, Linux administration, and troubleshooting. Certain questions were very tough, like "in what port do you attach your hard drive?" but I guess they asked that to check our limits, and they weren't deciding questions.
The last round was a Hiring Manager round, close to a typical HR round, but I had certain technical questions about my projects.
Scale a ride-hailing application to handle approximately 10,000 requests per minute.
This was a 1.5-hour-long discussion with follow-ups, including Consistent Hashing.
They also challenged multiple of my design claims, which I had to think about on the spot.
Questions covered DNS, Linux Inodes, Message Queues, Processes, Fork and VFork, the Kernel, the Linux Boot Process, and more.
The following metrics were computed from 3 interview experiences for the LinkedIn Site Reliability Engineer role in Bengaluru, Karnataka.
LinkedIn's interview process for their Site Reliability Engineer roles in Bengaluru, Karnataka is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for LinkedIn's Site Reliability Engineer interview process in Bengaluru, Karnataka.