LinkedIn - Interview Experience - Software Engineer
Replies (5)
typeahead SD is pretty standard at linkedin from what i've heard. component naming is actually a real thing they care about, they have their own terminology for the pieces
minimum window substring as a hard is rough. did they give you test cases or did you have to generate your own?
no hidden tests, you had to trace manually. wrote out a few test cases before coding
LFU cache is brutal under time pressure. how long did you have for the coding rounds?
45 min each i think. LFU i felt okay on actually, SD is what killed me
that naming confusion thing happens more than people realize. interviewers have their own mental models and if you're not syncing on terminology early you just spiral
tough feedback to get. SD clarity is hard to improve without doing mock sessions with someone who knows how linkedin frames these problems