I applied through a recruiter. The process took 3 weeks. I interviewed at LinkedIn (Mountain View, CA) in Mar 2016
Interview
Was contacted by a recruiter through LinkedIn Inmail. Had a call with the recruiter which included some simple prescreen questions. The next business day I was contacted to schedule a first round interview. First round consisted of 3 simple coding problems related to sysadmin tasks like log parsing and interacting with a REST api.
I passed this round and the second round was scheduled, this was 2 hour long technical interviews. First interview was mostly design questions about systems at scale, and the second interview grilled me on all sorts of sysadmin concepts like detailing the steps of an ssh connection and explaining host name resolution in detail.
I thought those interviews went well, but I did not receive an offer, maybe it was because I struggled a bit on the design questions. Overall, was a positive experience and a quick process, the only reason it took 3 weeks was because I have a busy schedule.
I applied through a recruiter. I interviewed at LinkedIn in June 2022
Interview
There were two rounds
1.operation round
2.coding round
both rounds were easy answered all questions which interviewer agreed are correct .still din't get feedback why i was rejected. They have standard questions which will be asked in every interview . I don't know how they are evaluating candidates.
Interview questions [1]
Question 1
Operations asked three questions
1.ssh how will it work
2.send one file from one server to 10,000
3.how to monitor three tier architecture
coding
1.FizzBuzz
2.recursion
3.log parsing
you can see answers here https://yumminhuang.github.io/note/sreinterview/
I applied through a recruiter. The process took 4 weeks. I interviewed at LinkedIn (New Delhi) in Feb 2021
Interview
The Hiring process was long, lasted over a month. I had an initial Hacker Rank coding round, followed by first round of interview, then second round and then final round which consisted of 4 rounds of interview.
I had referred previous interview experiences on Glassdoor and that helped to prepare. The questions were mostly similar. I got a rejection mail after the first round but then again I got a call for second round. They never answer when we call back. That's what I felt very bad about it.
Interview questions [5]
Question 1
First round was based on Networking. TCP/IP, ARP, DNS resolution, Sharding, Scaling, caching, server management concepts were covered.
Second round was scheduled only for Linux Memory management. Entire Memory management questions were asked. How it works, why is it required, Virtual memory, swap memory, swappiness and all.
System design was okay. They gave situations and asked how to design system in that scenario. We were allowed to ask questions to check if we were in tbe right track.
The last one was Troubleshooting
There was an Apache server and we had tk debug jt. It had 500 and 400 errors. I wasn't able to solve any in this round.
I applied online. The process took 4 weeks. I interviewed at LinkedIn (Bengaluru) in Jan 2021
Interview
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 host manager round. The first technical interview was a Service Architecture round where I was asked to scale a ride-hailing application to handle about 10000 requests/min. It was a 1.5 hour round. In the second interview, I was tested a lot on Data Structures, Networking, Linux administration, 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.
Interview questions [2]
Question 1
Scale a ride-hailing application so that it handles ~10,000 requests/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.