As many of the other reviews on Glassdoor have pointed out, there is a phone interview followed by an onsite interview. Unfortunately, I can't disclose any coding questions due to an 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 two questions (one medium and one easy) from LeetCode. We used Collabedit (or some other code editor, I think; I don't remember) to code and verify that the algorithm worked. The interviewer was happy, and a couple of days later, I received an invitation to schedule my onsite interview.

Onsite Interview Two weeks later, I was onsite. The interviewers were all really pleasant and fun. I had a total of five rounds of interviews (including 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:

1. 1st Round (iOS Specific Coding) This round was fairly straightforward, and I was asked to build a very simple app (which consisted 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).

2. 2nd Round (Chat with a Manager) This was the behavioral round where the manager asked standard questions, "Why do you want to work at LinkedIn?" etc., and also introduced himself and some of the projects he/she was working on. The manager also asked a brief design question about how I would design a particular feature on the LinkedIn app, but this was just conversational, not whiteboarding or anything like that.

3. 3rd Round (Lunch with Employee) This round was really fun as I got to taste some food at LinkedIn! and also chat with the employee. It was somewhat relaxing, but keep in mind that even though this was lunch, the employee was still evaluating me, so I kept it friendly and made sure the employee was engaged.

4. 4th Round (System Design Question) This was a mobile architecture question that dealt with designing a suitable API for the client and the interactions with it. It wasn't too difficult; I just had to explain the API structure I chose and also the front-end structure (how I would structure my classes, models, views, controllers, etc.).

5. 5th Round (Algorithms and Data Structures) This was 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 was asked a difficult dynamic programming question (similar to the longest palindromic substring). I couldn't figure out the solution in the given 45-50 minutes, so I got wrecked. Oh well... :(

Even though I thought I did really well on the other rounds, I received a rejection a week later. It was a positive experience nevertheless, and I would definitely want to interview again if given a chance in the future.

Why do you want to work at LinkedIn?

Standard coding questions that are on LeetCode.