LinkedIn interview notes, page 21 of 32

“I picked something I genuinely use every day, which helped, but I spent too long gushing about why I liked it and not enough time on the actual launch plan.” The rest of the author's notes on Product Manager interview at LinkedIn, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I rambled a bit.” The rest of the author's notes on Product Manager interview at LinkedIn, Hiring Manager Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight for a min-heap of size K and felt pretty good about it until they pushed on the streaming angle.” The rest of the author's notes on Software Engineer interview at LinkedIn, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The add/remove/lookup by name part is basically just a hash map and I got through that fine.” The rest of the author's notes on Software Engineer interview at LinkedIn, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew the answer here (hashmap plus doubly linked list) but I fumbled explaining WHY the doubly linked list specifically.” The rest of the author's notes on Software Engineer interview at LinkedIn, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Spent the first minute just trying to nail down what 'engagement' even means for LinkedIn specifically, because likes and shares feel like the wrong metric for a professional network.” The rest of the author's notes on Product Manager interview at LinkedIn, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is a Simpson's paradox setup and I knew that pretty quickly, which helped.” The rest of the author's notes on Data Scientist interview at LinkedIn, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is basically a 'design DynamoDB but explain every decision' question and I was not ready for the full scope of it.” The rest of the author's notes on Machine Learning Engineer interview at LinkedIn, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was DFS, trying each possible letter at each digit position and checking against the word list.” The rest of the author's notes on Software Engineer interview at LinkedIn, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The naive approach is obvious and wrong, O(n^2) calls if you just check every pair.” The rest of the author's notes on Software Engineer interview at LinkedIn, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.