I applied online. The process took 2 weeks. I interviewed at LinkedIn in Sep 2014
Interview
Applied online, got the phone screen with HR. They asked basic questions about your career and what you have done so far. Then got the 1st phone interview which was very simple and easy coding question. The 2nd phone interview was much harder and requires a thorough amount of studying. Be prepared!
HR was very nice and responsive.
The recruiter contacted me through email and arranged me a technical phone interview. I'm a little disappointed though, the interview was scheduled at 6:00PM Eastern Time.
During the phone interview(using collabedit.com), the interviewer asked two coding questions:
(1) the deepest common ancestor of two nodes of a tree
(2) all permutations of a string.
The questions were reasonable, but I failed to solve the second one. Also the interviewer thought I'm not engaging enough(didn't talk much).
I applied through a recruiter. The process took 4 weeks. I interviewed at LinkedIn (Mountain View, CA)
Interview
A recruiter initially reached out to me through LinkedIn.
After a few phone call interviews, I moved on to a few remote skills exercises. I didn't interview for a specific position, instead I was told that the position the company thinks you are best suited for is determined through your interview process (whether you're senior or staff level or whatever).
I had two screen-sharing interviews, which were coding exercises where two developers from LinkedIn would give you specific challenges or examples and ask you to solve them / work through them. Each one was about 45 minutes, with 30 minutes of coding and 15 minutes of just questions or introductions or whatnot. The first covered JavaScript, while the second covered HTML and CSS. Even though you're coding in a web interface, the code doesn't compile or actually show UI. I think it's so that you don't get distracted with minutia of making something actually work and instead talk about strategy and overall steps to achieving your goal.
After these first skill assessment interviews, I was flown out to Mountain View to interview at their campus. The on-campus interview was pretty much a full day process. I started off with a brief tour of the office and some discussion about the background of the company with one of the people I had exchanged emails with during the early phases of the process. Then I was taken to a meeting room where the rest of my interviews would take place.
There were six or seven groups of interviews. The first two were general information about the company and about the team. Then there were 4 technical interviews, each one with a pair of developers (one senior, one junior). Each one addressed different aspects of development - CSS, HTML, JS, etc. There was also a lunch interview, which is when you just grab lunch with another developer. Each of these interviews is about the same format as the phone interviews - about 45 minutes each with 30 minutes or so of coding and 15 minutes or so of general questions. Also, the technical challenges are all done on a whiteboard, without a computer.
Interview questions [1]
Question 1
During my phone JS interview, I got a lot of general CS questions. The questions were a bit frustrating, because they're things you know you can just Google search and find the one-line answer you need without any actual effort. Things like writing a function to determine if a string is a palindrome or writing a function for the Fibonacci sequence - things that don't have any real use and just exist as stereotypical interview questions.