LinkedIn

“I went with an iterative postorder traversal using a stack where each frame tracked the node, a child iterator, and the max height seen so far among processed children.” 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 sprawled in a way I wasn't ready for.” 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.

“The length-difference trick clicked for me pretty fast: get both lengths, advance the pointer on the longer list by the difference, then walk both in sync until you hit the same node reference.” 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 got the basic version down pretty fast but the Unicode part threw me off more than I'd like to admit.” 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 to just do a DFS and track depth, which is fine, but I didn't immediately clock that you need the max depth before you can assign any weights.” 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 is the kind of question where you can go in ten directions and none of them feel wrong, which is its own problem.” 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 knew something was off with the naive approach but couldn't articulate it cleanly at first.” The rest of the author's notes on Machine Learning 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 to just count sequences naively and I almost missed that the same plate can have multiple trips.” 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.

“Pretty straightforward join and group-by.” 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 I actually felt okay about.” The rest of the author's notes on Software Engineer 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.