LinkedIn interview notes, page 10 of 32

“The social network framing is cute but once you see it's just shortest path on an unweighted graph, it's BFS and nothing else.” 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 array plus hashmap idea comes to you pretty fast, but the devil is in the swap.” 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 basic push/pop/top part was fine, I've done stack problems before.” 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 this one.” 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.

“My first instinct was a simple hash map with a min-heap and I said so out loud, which I think was a mistake because it anchored the conversation on the naive solution for too long.” 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.

“This one tripped me up for a second because the table uses both author_id and viewer_id and you have to compare them.” 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 one tripped me up a little because my first instinct was to pick something that made me look proactive, but I realized mid-answer that the more interesting part is the 'how did you decide it was worth it' piece.” The rest of the author's notes on Product Manager interview at LinkedIn, Onsite - Behavioral / Leadership round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went straight for in-order traversal for the smallest, which is the obvious move.” 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.

“This one ate up probably 30 minutes.” 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.

“I spent the first few minutes confused about why weight mattered at all.” 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.