LinkedIn New Grad- Software Engineer Interview Questions & Reviews
Getting an Interview
- Popular Job Titles:
- Software Engineer (83)
- Senior Software Engineer (33)
- Sales Development Specialist (20)
- Web Developer (18)
- Software Engineer Intern (13)
- Intern (10)
- Data Scientist (10)
- Software Engineering Intern (9)
- Site Reliability Engineer (8)
- Associate Web Developer (8)
- Account Executive (7)
- Engineering (7)
- Product Manager (7)
- Marketing (6)
- Account Manager (5)
- Principal Software Engineer (5)
- Software Engineer - New College Grad (5)
- Relationship Manager (4)
- Project Manager (4)
- Enterprise Relationship Manager (4)
- Campaign Manager (4)
- Sales (4)
- Senior Manager (3)
- Analyst (3)
- Manager (3)
- Business Operations Manager (3)
- Software Engineer - Applications (3)
- Senior Data Scientist (3)
- Recruiting Associate (2)
- Enterprise Support Specialist (2)
Software Engineer New Grad Interview (Positive Experience; Difficult Interview)
I applied online and the process took 6 weeks - interviewed at LinkedIn in December 2013.
Interview Details – I submitted my application through jobvite (funny, isn't it, since LinkedIn also have their own job application platform). I think I came accross the job posting on Glassdoor.
Several days later, a recruiter contacted me about the phone screening. Due to the timezone difference (15 hours different), I had to wait a week for the first availability. The questions were standard just like other big tech companies' interviews. A week later, I was told that they moved forward with another phone screening. A week of waiting and I was informed that they would do an "online" on-site interview instead of flying me to the US. I was really grateful that they did that because otherwise, it would be a long wait to get the visa and arrange things to fly over (I also had other interviews going on during that time).
The onsite interview was split into two days as it consists of 7 rounds, each about 45 minutes. Each round covers different skills, with the first being a very generic round where I was asked various kinds of question about my background (I have a Master's in CS - research-based). Other rounds included questions revolving around the team I'm applying to, and of course, programming questions. In one round, I spent around 15 minutes asking questions back and forth since I misunderstood the engineer, but we sorted it out in the end. One interviewer didn't show up, but somehow I was waived that interview thanks to the first interviewer (some big manager) being impressed with my background.
The day after the interview, my recruiter emailed me and told me that they might have to do another round for the interviewer that didn't show up. I was really pissed at that point because I had to wake up really early here to match the time in the US, but I agreed anyway. However, an hour later my recruiter informed me that they decided to waive that round since I impressed the big manager who interviewed me first.
Overall, the process was smooth. My recruiter was very quick to answer my questions, but I felt 7 rounds for the onsite were too much compared to other companies I interviewed with (Google and Amazon). However, the engineers were really laid-back and I really enjoyed discussing with them. Some of them appeared a bit cold and distant, but they were no less helpful when it comes to clarifying the ideas and providing feedback. Note that I interviewed with also Amazon and Google, and I think the standards are similar across the three companies.
Interview Question – Nothing particularly difficult. If you practice with careercup, leetcode, and codility enough, you'll be fine. Answer Question
Negotiation Details – LinkedIn spent quite sometime to decide the team for me first before extending the final offer - this is the opposite of Amazon and Google (though I failed Google due to my lack of preparation back then). I had three other standing offers at that time, but they weren't very high so I wasn't expecting a very good offer. However, when the recruiter told me the number, I was in a bit of shock since I didn't think the offer would be that attractive (better than my friend's offer from Google), though I wish they gave me a sign-on bonus instead of a yearly bonus (not that I'm complaining anyway). I decided to go with LinkedIn as I'm really impressed with the offer, and I really like the open-source driven projects they have there.
New Grad- Software Engineer Interview (Neutral Experience; Average Interview)
The process took 2+ weeks - interviewed at LinkedIn in April 2012.
Interview Details – I was first communicated by the recruiter who called me and had a normal background chat for about 30 minutes. He also gave me details about the company, culture, teams, etc.
I was scheduled for a phone interview of an hour which also had coding involved. This round had one problem-solving question, which was related to Binary Search Algorithm application, went okay. I could reach a solution, and even though I took some time to reach the correct approach, the interviewer appreciated my thought process.
I got mail for another phone interview which again was for an hour and I had to code online. This time it was a tough question about writing a program where given a sorted array, repetitions allowed, and given an integer, I had to return the start index and end index of that integer in the array. I chose the Binary Search approach but some modifications had to be made to make it optimistic in run-time. I failed to reach the exact solution, and hence could not clear this round.
I think LinkedIn is a nice company to work with and I would surely consider applying again to it at some point of time in future.
Interview Question – This time it was a tough question about writing a program where given a sorted array, repetitions allowed, and given an integer, I had to return the start index and end index of that integer in the array. I chose the Binary Search approach but some modifications had to be made to make it optimistic in run-time. View Answer
Interviews for Top Jobs at LinkedIn