LinkedIn Front End Software Engineer Interview Questions

Applied online over Linkedln, and same got a response to schedule a phone interview. The phone interview went well and schedule a phone screening interview for next week. The recruiter was a helpful easy and smooth process.

2 round. Coding challenge and coding interview. Coding challenge in Java, interview in react. Challenge took 90mins, interview took 45mins. Interviewer was nice. Code did not have to run. Had access to the web to look up syntax. Interviewer was very helpful and interactive

It was a smooth process. Used coderpad for code. Interviewer was kind enough. Explained how the interview process is. And introduced himself. Ask me about myself. How things work at LinkedIn.

First you get a call they will ask you few basic questions and then I you're good enough by answering those questions then you will going to get an appointment for the interview and after that you will be given a task to complete on that base they will decide to hire you or not.

Recruiter, then Phone Interview They were generally nice, asked html questions then js palindrome coding then html coding. Only thing I would say is the interviewers were not on the same page at all, they just randomly paired together two engineers. One would tell me to do one thing and the other would tell me to disregard that and do something different the way he wanted.

overall is good, every one is nice and friendly. But you can not tell if they agree with you or not. Be prepared for core front-end questions and js problems.

Was by phone but they sent you and email with a link you need to open the link and write code. LinkedIn Introduction My Introduction 2 step -> Questions (theory) 3 -> step -> code (What does this code return?)

Applied online and got a call from recruiter to setup some time for phone screen. Phone screen was more of a rapid fire round of questions all related to HTML/CSS/JS. Then final 20-25 mins for coding. I felt I did answer all questions correctly but never got a proper response from recruiter.

My interview experience with LinkedIn was pretty great overall, you can feel the amazing company culture in every step of the interview process, interviewers (both over the phone and in-person), my recruiter, coordinators, etc. I reached out to a LinkedIn recruiter that had previously contacted me months ago, we had an initial phone conversation and discussed the role, my experience and interests. After that the first phone screen was scheduled. I did good on that one but had to take a second phone screen a week later since I was not able (due to timing) to demonstrate my javascript knowledge enough. I did great on the second one and was invited onsite shortly after. I was interviewing with a few different companies and had pending offers by the time I went onsite, so they were able to expedite the onsite date and travel logistics to accommodate my needs. The onsite consisted of 6 rounds of interviews (all but one were 1:1) plus lunch with another engineer (this might be considered as the 7th interview) at one of their amazing onsite cafeterias. The interviews were all technical and 5 out of 6 involved coding problems in javascript. They test very heavily on vanilla javascript knowledge and coding abilities. All the problems were challenging but totally solvable with good preparation on algos and data structures. On the system design interview, expect to be able to design a system that scales as a whole, but the heavy focus is on front end architecture. Showing passion for well design products, front end development and LinkedIn and its mission should suffice to pass the non-technical interviews.

I was contacted by a recruiter on Linkedin. Overall the process was great and everybody I spoke to were nice. Apart from the position , I was mainly concerned about culture and work-life balance and everybody I spoke to were really happy about working there. 1) Technical phone screen - This was a standard collabedit phone screen. Part-1 I was given some code and was asked the output and how to fix it. It was based on scope and JS inheritance. Part-2 HTML/CSS Had to code it from an image they had. I was also asked to explain floats| promises| accessibility.This was pretty straightforward, make sure you brush up on core JS. 2) Heard back roughly a week later and was invited Onsite. The onsite had 6 interviews with lunch. The HR will give you the different modules each interview focuses on. All interviews we mainly focused on UI(html/css/js) except 1 which was an Algo string manipulation question. Some modules were just JS, some I had to build out the whole component as a plugin(html/css/js). The design question was also more UI layer focused than system architecture which was unusual. 3) I left thinking I did well in all my interviews. But unfortunately I didn't get the job, the reason I was given was Design and 1 Js round feedback wasn't good. In both interviews I kept an open dialog discussed solution , improved with hints and reach a agreeable outcome. It was disappointing to not get specific feedback , so I'm not sure what really went wrong.