I applied through a recruiter. The process took 1 week. I interviewed at LinkedIn in Jul 2015
Interview
Contacted by their recruiter. Next day had a call with her, and within 24 hours they scheduled a phone interview for the next week. Smooth and clear, no hiccups.
Phone interview was with one of their junior SWE, he was very nice and polite. We briefly talked about each others' past and current projects and went straight to the coding. Was not that hard after all, I just did not have a practice of that sort of interactive coding. The guy, again, was polite, few times gave me some small hints. At the end he confirmed that I did it correct.
Recruiter contacted me next morning and asked for another phone call with more senior team members. Going to do it next week.
Interview questions [1]
Question 1
Task was for using different data structures in Java Collections framework.
I applied through a recruiter. I interviewed at LinkedIn
Interview
Contacted by recruiter, agreed to do phone screen, went on site. Had 5 interviews. Two coding/algorithmis, one design, one communication, one chatting about my history. Also had lunch in the cafeteria. They have an ipad with your schedule for the day. They let you know your interviewers ahead of time. The recruiting host shows you around the place before you start. It's a nice place.
Interview questions [1]
Question 1
Graph and tree problems, a geometry/math question, a well-known OOP design question, and explain a previous project as if explaining it to two new teammates.
I applied through a recruiter. The process took 4 weeks. I interviewed at LinkedIn in May 2015
Interview
Phone Screen: They followed the usual collabedit.com based shared document to write code for the given question.
The interviewer was nice and had good communication skills. I bombed the interview, possibly due to the prompts required to answer the question. Their expectations are higher.
No sour grapes here, the process is fair, better than other companies. With this out of the way, here is some feedback to LI itself:
One important point, I realized was the fact that, any line you type on the screen is considered final. My thought process is to exercise my own code and find issues with it. The interviewer was immediately jumping in pointing out things. Holes in the logic should be fine to point out, but, leave a minute or two to let the person think. It is a tough(only for some people, obviously) thing to pull off a balance between showing the interviewer what you are thinking Vs. solving the problem itself.
I feel that an experienced engineer can't simply survive a day not knowing some of the things the interviewer mentioned in my interview. I write decent C++ code day-in and day-out which is reviewed at a very high standard.
So, rejection from LI was a damning indictment of my "coding skills". So, be prepared to feel the worst engineer on the planet for a good month or so, if you do get rejected.
Interview questions [1]
Question 1
It is a famous problem from a famous book, that I happened to read 12+ years ago. Not entirely unexpected, but, writing the code on the screen was a different challenge by itself.