← Back to Directory

LinkedIn interview notes, page 1 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·Data Scientist·Technical Phone Screen

Sep 2023
LinkedIn Data Scientist interview with a SQL question focused on aggregating user activity. Pretty standard stuff, nothing that should trip you up if you've done any analytics work before.
  • Given a posts table with columns for post id, user id, and creation timestamp, write a SQL query that returns each user and their post count over the past 30 days, sorted by post count descending.

“Straightforward aggregation question.”

View Post

LinkedIn·Software Engineer·Onsite - Multi Round

Aug 2024
Went through four rounds for a Senior SWE role at LinkedIn and felt pretty decent about most of it, except the AI coding round which was rough. Now the job got reposted and I'm spiraling a little waiting to hear back.
  • Design a system (the round covered architecture and scalability topics for a senior engineering role).
  • Implement an LRU cache variant with modifications, and explain why you chose a doubly linked list as your underlying data structure.

“This was the round I felt best about.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Apr 2026
LinkedIn software engineer interview, one round focused entirely on a project deep-dive. Pretty standard format but they push hard on the specifics so vague answers won't fly.
  • Walk me through a project you worked on: what was the goal, what was your specific role, what technical challenges came up, what trade-offs did you make, and what was the outcome?

“This is the kind of question that sounds easy until you're actually in it and realize you've been rambling for three minutes without getting to the interesting part.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Apr 2026
LinkedIn coding interview with a phone keypad grouping problem. Pretty classic hash map territory but the twist of mapping letters to digits instead of grouping anagrams tripped me up for a minute.
  • Given a list of words, group together any words that map to the same digit sequence on a classic phone keypad (where 'abc' maps to 2, 'def' to 3, and so on). Return all groups.

“My first instinct was anagram grouping and I almost went down that path before catching myself.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
PM interview at LinkedIn, single question about launching LinkedIn Live Video and defining what success looks like for it. Pretty open-ended, which I both liked and fumbled.
  • You're a PM at LinkedIn in 2018 responsible for launching LinkedIn Live Video. How would you define and measure success for it?

“I jumped straight to engagement metrics and kind of forgot to anchor on what LinkedIn Live Video was even supposed to do for the platform.”

View Post

LinkedIn·Software Engineer·Onsite - Product Sense / Strategy

Apr 2026
LinkedIn data analyst interview, one question about designing an AI data product. Pretty open-ended and I wasn't totally sure how deep to go on the technical side versus the product side.
  • Design an AI-powered data product from scratch.

“I spent the first couple minutes just trying to figure out what angle they wanted.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
LinkedIn product interview, one question about expanding into a restricted market. Not much context given so I'm filling in the blanks from memory.
  • How would you launch LinkedIn in Belarus?

“This one threw me because Belarus isn't exactly a standard market entry case.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Apr 2026
LinkedIn SWE interview with a string pattern matching problem. Pretty standard algorithmic question but worth noting for anyone prepping.
  • Given a string and a pattern, count how many times the pattern appears in the string.

“Seemed simple at first and I jumped straight to using a built-in count method, which worked but they pushed me to implement it manually.”

View Post

LinkedIn·Machine Learning Engineer·Technical Phone Screen

Apr 2026
LinkedIn ML Engineer screen, one meaty theory question on logistic regression loss functions. Pretty standard for this type of role but it went deeper than I expected.
  • What loss function does logistic regression typically use, and what's the reasoning behind that choice?

“Knew binary cross-entropy was the answer but fumbled explaining the 'why' at first.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

Apr 2026
Interviewed at LinkedIn, got hit with a competitive strategy question that felt more like a business school case than a PM interview.
  • How would you respond if competitors started rapidly shipping a lot of new features?

“My first instinct was to say 'copy the best ones and move fast' which, looking back, was pretty shallow.”

View Post