This was one of the most organized interview processes I have participated in. Thumbs up to LinkedIn and the recruitment team! They were always providing feedback during the process.

1. It started with a phone screen by the recruiter, with a few basic technical questions just to filter the candidates.

2. After that, you were scheduled for two technical phone interviews with other Site Reliability Engineers. The first was generic and included everything you can imagine, from Linux to networking, fundamentals, databases, troubleshooting, etc. The second was a coding interview where you both shared a document and were given a few operational challenges to solve. You picked the language to use.

I really enjoyed that because I am not a software engineer, and I am used to coding things to solve operational problems. That's what they want for an SRE.

1. If you passed the phone interviews, then you were set to go onsite for a full-day interview with more SREs. The onsite was similar to the first generic phone interview, but now all those topics were interviewed by an expert in that area, going as deep as you could keep answering. This was the challenging part.

2. Once I was done with the onsite interview, it took about one week to get the offer. During that week, I received a lot of feedback from the recruiter, and she said I had passed the process and they were discussing the offer and the SRE team where I would fit.

I really enjoyed the process. It was more difficult than I had expected, and the communication with the recruiters was great.

All the steps above were communicated to you once you passed each of them, including the interview topics you were expected to cover.

I can't talk about the questions, but one of the topics the recruiter will tell you about is Linux Internals, and that is definitely the most difficult.