LinkedIn interview notes, page 5 of 32

“I started with user outcomes, like did the mouse actually get caught, and then tried to layer in things like time-to-catch, safety, ease of disposal.” 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 jumped straight into screens and flows without anchoring on what kind of app or what success looks like for a new user.” The rest of the author's notes on Product Designer 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.

“My first instinct was to just map the formula and re-sort at the end, which works but they clearly wanted something smarter.” 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.

“Pretty standard aggregation stuff.” 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 question is way broader than it looks.” 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 iterate from 1 upward and check k*k == n, which works but is obviously O(sqrt n).” 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 overcomplicate it.” 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 started with get/put/delete and felt pretty good about it, then they pushed on contains and size and I realized I hadn't thought through atomicity at all.” 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 getRandom part is where I got tripped up.” 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 got the brute force pretty fast, keep a list, scan everything.” 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.