As many of the other reviews at Glassdoor have pointed out, there is a phone interview followed by onsite. Unfortunately, I can't disclose any coding questions due to NDA however they are all from Leetcode tagged under LinkedIn. Here was the structure of my interviews: Phone Interview (1 hour) I was asked some basic iOS questions and 2 questions (one medium and one easy) from Leetcode and we used Collabedit (or some other code editor I think dont remember) to code and verify that the algorithm works. The interviewer was happy and a couple of days later, I got an invitation to schedule for onsite interview. Onsite Interview Two weeks later, I was on onsite. The interviewers were all really pleasant and fun. I had a total of 5 rounds of interview (including the lunch with one of the employees). Here was my ordering of the different rounds but keep in mind that they can be in any order: 1st Round (iOS Specific coding) This round is fairly straightforward and you're asked to build a very simple app (which consists of a couple of screens at most). Just make sure you know the basics of parsing, and building UI (storyboards or programmatically anything is fine). 2nd Round (Chat with a Manager) This round is the behavioral round where the manager asks the standard questions, "Why do you want to work at LinkedIn...etc...etc" and also introduces himself and some of the projects he/she is working on. The manager also asked a brief design question of how you would design a particular feature on the LinkedIn app, but this was just conversational, not whiteboarding or anything like that. 3rd Round (Lunch with employee) This round is really fun as you get to taste some food of LinkedIn :D and also chat with the employee. So somewhat relaxing but keep in mind that even though this is lunch, the employee is still evaluating you, so keep it friendly and make sure the employee is engaged. 4th Round (System and Design Question) This was a mobile architecture question which deals with designing a suitable API for the client and the interactions with it. Not that difficult, just make sure to explain the API structure you choose and also make sure to explain the front-end structure (how you would structure your classes, models, views, controllers, etc)... 5th Round (Algorithms and Data Structures) This is the round where luck can play a huge role (in my opinion of course). However, I got hopelessly DESTROYED :( Dynamic programming was my weakest link and I got asked a difficult Dynamic Programming question (similar to longest palindromic substring). I couldn't figure out the solution in the given 45-50 mins so I got wrecked. Oh well.... :( Even though (I thought) I did really well on the other rounds, received a rejection a week later but was a positive experience nevertheless and would definitely want to interview again if given a chance in the future.

Got contacted by recruiter through LinkedIn and scheduled a technical phone screen. I was honest with the interviewer and told him I had seen the first problem in past interviews, He told me it didn't matter and I went ahead with the implementation. I was very familiar with it so I wrote it in 10 minutes. Then he asked me a second problem. This one was a bit harder and I took some time to think about it. I started to tell him my thought process but as I was writing it I started to stutter and I believe that made him loose focus on my code, so I noticed he was not actually following me anymore. After some time I was able to complete the problem and he just told me it was ok, I'm pretty sure he didn't understand my implementation and he was just playing along with me, even though it worked. My advise for interviewers is to actually engage with the candidate, otherwise they'll just make you feel ignored and think you're wasting both parties' time. Even though I solved the two problems, I got the rejection email after a few days and asked the recruiter for any feedback, but as usual, they don't reply.