Process
The onsite interview involved a coding section that I found to be not difficult. The design part, however, was more challenging. I felt the interviewer may not have been very professional. The other parts of the interview felt good. I'm unsure why the coding feedback was not positive, as the interviewer did not point out any specific issues.
Questions
Design the blacklist and implement a hashmap.
Was this helpful?
Interview Statistics
The following metrics were computed from 285 interview experiences for the LinkedIn Software Engineer role in United States.
Success Rate
LinkedIn's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having good feelings for LinkedIn's Software Engineer interview process in United States.
LinkedIn Work Experiences
- 5.0Love the cultureSoftware Engineer • Current EmployeeSan Francisco, California, United StatesFebruary 8, 2024Pros: Working with people makes working at LinkedIn very enjoyable.Cons: Down-leveling and promotion cycles are difficult.
- 5.0Love The People, Great StartSoftware Engineer • Current EmployeeMountain View, California, United StatesAugust 11, 2017Pros: It's going really well, and I like the people a lot.Cons: Not much, honestly, as of now. But I just joined.
- 1.0Technology arrogance without the abilitySoftware Engineer • Current EmployeeMay 5, 2011Pros: It's a 'hot' company, that's about all.Cons: Blind technology leadership, and a "not invented here" attitude towards standard open source technologies. For example, the 'open sourced' Zoie project implements a cheap hack for real-time search using Lucene, which was presented to and rejected by Twitter. Voldemort is yet another copy of Amazon's Dynamo; however, it falls far short of Cassandra. LinkedIn has numerous open source and internal projects that show technology comes last, and egos come first.
LinkedIn Interview Questions
