← Back to Directory

LinkedIn interview notes, page 3 of 32

Large Enterprises

Most of these LinkedIn write-ups come from Software Engineers (156), then Product Managers (66) and Data Scientists (37). The most reported rounds are the technical phone screen (169), the product sense round (62), the system design round (42) and the behavioral / leadership round (20).

316 interview notes · updated Oct 2026

LinkedIn·Machine Learning Engineer·Technical Phone Screen

Apr 2026
Phone screen for an MLE role at LinkedIn, basically just a project walkthrough. Nothing too intense, but there's a small tactical thing worth knowing going in.
  • Walk me through some of the projects on your resume.

“The interviewer defaulted to older stuff on my resume and I kind of just went along with it for a bit before realizing I had more relevant recent work I should be talking about.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
LinkedIn PM interview with a product design question that had nothing to do with LinkedIn. One question, pretty open-ended, left me second-guessing my structure the whole time.
  • You're a PM at Airbnb. How would you design a furniture product?

“The Airbnb framing threw me off more than it should have.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at LinkedIn with a product design prompt that had nothing to do with LinkedIn itself. One question, open-ended, and I spent the first few minutes wondering if I'd misheard the company name.
  • Design a travel app experience for Meta.

“Weird prompt to get at a LinkedIn interview but here we are.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Apr 2026
LinkedIn SWE coding round, one problem the whole time. It's a phone keypad / dictionary lookup thing, basically LeetCode 17 but with a word list constraint. Felt manageable once I figured out the pruning angle.
  • Given a string of digits (2-9), where each digit maps to letters like a phone keypad, and a dictionary of valid words, return all letter combinations of the digit string that appear in the dictionary.

“I started with the naive backtracking approach, generate every combination then filter against a set.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Apr 2026
Quick LinkedIn technical screen, just one SQL question and that was basically it.
  • How would you perform a lookup in SQL?

“Pretty standard.”

View Post

LinkedIn·Software Engineer·Onsite - System Design / Architecture

Apr 2026
LinkedIn system design round for a software engineer role, one big open-ended question about building a distributed key-value store from scratch. The scope was wide enough that I kept second-guessing how deep to go on each piece.
  • Design a distributed key-value storage service that supports put, get, and delete operations, handles tens of terabytes of data, and meets sub-10ms p95 latency with high availability.

“I started with the API and data model which felt safe, but then spent way too long debating consistency models out loud before I'd even sketched the architecture.”

View Post

LinkedIn·Machine Learning Engineer·Technical Phone Screen

Apr 2026
LinkedIn ML engineer screen that was basically one big pseudocode question about gradient descent variants. Pretty focused, no fluff, just write the algorithm and be ready to talk tradeoffs.
  • Write pseudocode for mini-batch gradient descent covering: sampling the training set into mini-batches of size B, the forward pass and loss computation, backprop and gradient calculation, the parameter update with learning rate η, and looping over epochs with a convergence check. Also contrast it with full-batch gradient descent and SGD.

“This is more involved than it looks on the surface.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Apr 2026
LinkedIn SWE coding round, pretty much what you'd expect. One algorithmic problem, classic grid traversal stuff.
  • Given a 2D binary grid where 1s represent land and 0s represent water, count the number of distinct islands. Islands are formed by horizontally or vertically connected land cells.

“Classic flood-fill problem.”

View Post

LinkedIn·Data Analyst·Technical Phone Screen

Apr 2026
SQL question at LinkedIn, pretty standard stuff, nothing that should've tripped me up but I still managed to second-guess myself halfway through.
  • What is the difference between a JOIN and a UNION in SQL?

“Knew this cold and still fumbled the explanation a bit.”

View Post

LinkedIn·Software Engineer·Onsite - System Design / Architecture

Apr 2026
LinkedIn system design round, one big question that sprawled into basically every subsystem you can think of. The scope was wider than I expected and I kept second-guessing whether to go deeper on caching or spend more time on the ingest pipeline.
  • Design an isMalicious(item) API service that, given a URL, IP address, file hash, or email, returns whether it is known to be malicious. Cover the API contract and latency/throughput targets, how you store and refresh threat intelligence data, a multi-tier read path with caching and a Bloom filter, propagation of new entries, regional replication, and monitoring.

“This one ate the whole session.”

View Post