The first interview was a phone screen with the technical recruiter. It was mostly an opportunity to hear about the state of LinkedIn and see if it's a good fit for you. The recruiter asked me about my current skills and roles. The second phone call was with a two session, 45 minutes each, phone code challenge using collabedit. The questions were both frontend questions about markup, css and javascript. If you know these three intimately, you'll be okay. The developers I talked with were really great and were really interested in talking through the process with you, so don't get carried away just typing, talk through your process. The last interview was an onsite. The recruiter met me at the lobby and walked with me to the interview room and explained to me how the interview process was going to go. They give you an itinerary with everyone's name on it, which is really nice to offload one more thing you have to stress about through the day. We had a great conversation about what the recruiter liked about LinkedIn, about where I currently work and just life in general until my first technical interview. Each technical interview (of which there were 7 questions), was about an hour, and a mix of culture/skills questions and whiteboard questions. These questions ranged from moderate to difficult, and they all require you to think through the process of solving the problem. You really need to know html and css with 100% certainty, and you need to know your javascript well. There were two CSS challenges and 5 javascript challenges, almost all of them involved also writing the markup to correlate with them. Overall, this has been the best interview experience I've ever had, and I've had some really great interview experiences. LinkedIn seems like the kind of place anyone with a passion for development/engineering would love to be.

1. Call from the recruiter. Mainly just about my past jobs. (20 min) 2. Technical call by a senior web developer. Technical questions about HTML, CSS and JavaScript. (30 min) Mainly I was asked about positioning html with css, accesibility and frameworks that I use. 3. Technical call with collabedit by two Sr. Web developers . Technical questions about HTML and CSS. (45 min) They showed me an image and asked me to type the structure for the HTML, and then apply the CSS rules. 4. Technical call with collabedit by a Sr. Web developer and a Web developer (45 min) They showed me some code and asked me to describe what was happening there and why. Knowing how value vs reference type and how context works is needed to answer this correctly. I was asked to code the isPalindrome() function and another problem that uses your previously coded isPalindrome function that the interviewer had difficulties trying to explain to me. At the end, I got the idea and explained what I would do because the time was almost over. 5. In site interview in Mountan View, CA (I didn't make it to this interview) The third and fourth interviews where done the same day consecutively. I didn't make it to the 5th interview because my HTML and CSS were not good enough. Basically, I feel the reason why they didn't like it is because I didn't use the elements correctly. Semantic elements are very important to them. Learning experience for me and loss for them. I still think that I would have been perfect for the job. My JavaScript interview went great. The recruiter called me to tell me the bad news. He explicitly said I didn't make it because of the third interview. I appreciate the fact that he called me instead of sending me an email. Overall, it was a great interview process.