I was contacted by a campus recruiter on LinkedIn. They set up a phone interview to tell me more about the role.
The phone interview was good. The recruiter explained the role, what they expected from interns, and what our responsibilities would be.
They then said, "I'll be asking you some basic questions. If you give the right answers, then you'll have the next technical round."
The questions covered Bash, TCP, and processors. Finally, they gave me a list of IP addresses and asked which ones were public and which ones were private (it wasn't as easy as 127.0.0.1 or 192.168.0.1).
The recruiter was satisfied with my answers and told me to send my availability date for the interview.
I had a phone-screen interview. Most of the questions were similar to those posted here. I focused more on Linux Fundamentals, such as learning about fork, runlevels, init, Docker, application deployment, and port numbers.
The email mentioned that the interview would include scripting questions on application deployment, filesystem traversal, and log parsing.
I couldn't get the role. I was expecting to get it because I focused more on Linux than scripting. However, the recruiter who contacted me called and gave me the news. They were kind and told me to apply next year or send an email when I graduate. They also advised me to practice scripting if I wanted this position, as it essentially revolves around scripting and automation.
FizzBuzz Question
Modifications: 4 and 6 instead of 3 and 5. Linked, In, and LinkedIn instead of Fizz, Buzz, and FizzBuzz.
Log Parsing
Recursive call of the LinkedIn API using REST.
The following metrics were computed from 46 interview experiences for the LinkedIn Site Reliability Engineer role in United States.
LinkedIn's interview process for their Site Reliability Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for LinkedIn's Site Reliability Engineer interview process in United States.