LinkedIn·Product Manager·Onsite - Product Sense / Strategy
- How would you grow LinkedIn's student user base?
“I went straight to acquisition and kind of forgot that retention for students is a completely different beast.”
Large Enterprises
Most of these LinkedIn write-ups come from Software Engineers (156), then Product Managers (66) and Data Scientists (37). The most reported rounds are the technical phone screen (169), the product sense round (62), the system design round (42) and the behavioral / leadership round (20).
316 interview notes · updated Oct 2026
“I went straight to acquisition and kind of forgot that retention for students is a completely different beast.”
“The core Kadane's logic came back to me pretty fast: track the max sum ending at the current position and decide whether to extend the running total or restart from the current element.”
“I had a story ready but I spent too long on the backstory and barely got to what made it actually excellent.”
“I went with the usual suspects: oversampling the minority class, undersampling the majority, or adjusting class weights in the model.”
“This is way more than the usual 'state the Big-O and move on.' They wanted me to actually derive it and justify each case separately, not just say O(n log n) and shrug.”
“This is one of those questions that looks manageable until they start asking why at every single step.”
“I knew the LC 380 version cold, array plus hashmap, swap-with-last on remove, done.”
“The O(log n) requirement is basically telling you binary search, but the rotation breaks the usual assumption that one side is always smaller.”
“This is the kind of question where the wrong move is pretending the conflict doesn't exist.”
“This is where I started rambling.”