I applied through a recruiter. The process took 2 days. I interviewed at LinkedIn in Dec 2013
Interview
I got a call from Linkedin's internal recruiter. He has asked me about my work experience, am I willing to relocate. He has describe a bit about the job work load. As SRE isn't really what I have been doing, the job description he provided didn't really click with me. He has also asked some basic DNS lookup question, linux questions about what system calls related to listing files and what tool you can use to check I/O load. I passed this part. As I am a sys admin so this was easy for me.
The second interview was conducted by a junior technical staff in the team. The recruiter has sent me exactly what would be asked. HTTP browser request, how to monitor a website, to distribute loads of files fast and accurrately.
The interviewer did ask all these questions and a bit more. unfortunately I don't have experience with websites. I am more a sys admin. so i was just really guessing what i would have done. like detect via load balancer, error logs in apache etc.
I didn't get to the next stage.
Interview questions [1]
Question 1
How to monitor a website as this is not really my line of expertise.
I applied through a recruiter. The process took 3 weeks. I interviewed at LinkedIn (Mountain View, CA) in Oct 2013
Interview
Had an initial call with a recruiter followed by two phone screens and 4 onsite interviews as part of LinkedIn Invitational. Recruiting did a great job showing us around, and a few of the engineers made a really strong impression on me. However for the most part I found the interviewers to be cold, deliberately vague, and frustrating. In one case, the interviewer would frantically grab his notepad and start scribbling furiously every time I made a mistake. It was that obvious. Compared to my interviews at Google (received an offer), although the process at both places was largely robotic technical interviewing, I felt LinkedIn interviewers were much more difficult to connect with.