LinkedIn interview notes, page 22 of 32

“I jumped straight to funnel analysis which felt right but I spent too long there and almost forgot to check the obvious stuff like whether a recent release broke something.” 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.

“I'd practiced this but still rambled past the time.” 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.

“My first instinct was to just sort and index from the end, which works but they pushed back on efficiency pretty fast.” 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'd done the simpler version before so I felt okay starting out.” 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 the n-squared brute force and I actually started explaining it before catching myself.” 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 took me a second to parse because I kept thinking about distributed KV stores like Redis and had to mentally downshift to something more like RocksDB or even just a hash map with extra steps.” 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.

“My first instinct was to just iterate from 1 upward and check each square, which obviously fails the time constraint.” The rest of the author's notes on Mobile 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 the obvious stuff, check recent deploys, look at error rates, see if it's regional or global.” 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 was the most interesting question of the screen.” 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.

“I went straight to network effects and data quality, which felt right, but I think I undersold the supply side of it.” 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.