In order to honor the NDA I signed, I'll try to be as vague as I can about the specific technical questions. Had a phone screen first. The phone screen consisted of two programming questions. The first one was very simple. It was a question just to make sure basically you can program and design unit tests for it. It was easy to get bugs in it, but as long as you know how to program, you should be fine. The second one tested your data structures. Make sure you know what lists and sets are good for. The recruiter was very responsive. I got a response within the next three days. He offered me good luck and transferred me to another recruiter to schedule the on-site. I had to change the on-site date once and the recruiter was very professional and accommodating. The on-site was extremely nice. To be honest, I wasn't particularly interested in LinkedIn at first, but the first phone interviews, recruiters, and campus really impressed me. Their campus is right next to Google's. Once you go in, they give you an ipad 2 for the day, where you can check your schedule and interviewers. It consisted of 5 interviews along with lunch: 2 technical, 1 design, 1 explain one of your projects in more detail than anyone would ever care, and 1 behavioral. The 2 technical interviews were fairly straight forward. First one was really straightforward in fact. It was just a very long programming question, but it was overall pretty straight forward and did not involve any special algorithms or data structures. The second one was a bit more tricky. All I can say is get very familiar with binary trees. I know for sure I got at least the first part very well. Second part, I spent a lot more time than I should have on it. The part I felt I really bombed was the design questions. The design question is actually posted on glassdoor by another candidate (hint hint), but I won't say it in order to honor the NDA, but definitely study the questions the other people have provided here. In any case, this interviewer impressed me most with his knowledge and he just seemed really smart in general. I'm sure this was the interview I got rejected on though. Definitely know your distributed systems. I was unfortunate in the fact that I never had any experience with distributed systems. I must also mention though, the last interview for the day was probably one of the worst interviews I have ever had. Not in terms of me not doing well, but the interviewers were pretty junior and seemed very nervous. It felt very awkward since one of them was studying something, and not paying attention at all, and the other was continually checking his time, obviously hoping it would be over soon. They drilled me in one of my projects into more details, which I kept giving, but it felt very uncomfortable since there were many instances when it felt like they did not know what to say so there were pockets of silence. Over all though, the experience was great. I did not get an offer, which I was a little disappointed with since I thought I did decently overall, but I did not do well on the design question and ultimately, it's their call on who they are looking for.