← Back to Directory

LinkedIn interview notes, page 16 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

May 2026
LinkedIn DS interview with a meaty causal inference question about a redesign rollout where you can't just run a clean A/B test. The kind of problem that sounds manageable until you're actually in the hot seat trying to remember what a propensity score even does under pressure.
  • A new mobile app redesign is released as an opt-in upgrade, so users self-select into the new version. How would you measure the causal impact of the redesign? Walk through your causal inference approach, how you'd build comparable treatment and control groups, what features you'd match or weight on beyond past engagement, and how you'd validate your assumptions.

“This one wrecked me a little.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn SWE coding round, one algorithmic problem the whole time. Pretty standard sliding window territory but the details matter more than you'd think.
  • Given two strings s and t, find the shortest substring of s that contains every character from t, including duplicates. Return an empty string if none exists.

“The O(n) constraint is what makes this non-trivial.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

May 2026
LinkedIn product interview, one question about expanding LinkedIn Learning into a new market. Pretty sparse on details but the question itself is a solid GTM case.
  • How would you go about launching LinkedIn Learning in a new country?

“This is a classic market expansion case but LinkedIn Learning adds some wrinkles.”

View Post

LinkedIn·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Behavioral round at LinkedIn for a software engineer role. Three questions, all pretty standard conflict/failure territory, but they pushed for specifics more than I expected.
  • Tell me about a time you had a conflict with a peer, manager, or stakeholder and how you resolved it.
  • What's the most challenging project or problem you've worked on, and how did you approach it?
  • Describe a time you handled a difficult situation poorly. What happened, what did you learn, and what would you do differently?

“I had a story ready but I fumbled the resolution part.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

May 2026
LinkedIn PM interview, one question about experimentation on a past product. Pretty short on details but enough to know what they're looking for.
  • Walk me through an experiment you ran on a product you worked on previously.

“I had a decent example ready but I fumbled the structure a bit.”

View Post

LinkedIn·Machine Learning Engineer·Technical Phone Screen

May 2026
LinkedIn MLE interview with a probability/randomness question that sounds like a classic puzzle but has a lot of depth once you get into the weeds of efficiency.
  • You have a biased coin function that returns 0 with unknown probability p and 1 with probability (1-p). Implement a function that returns a uniformly random integer from 0 to 6 inclusive. Walk through your approach, analyze the expected number of calls to the biased function, and discuss how you'd minimize it.

“The von Neumann trick clicked for me pretty fast: call the biased function twice, if you get (0,1) output 0, if (1,0) output 1, otherwise discard and retry.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn software engineer interview, coding round. Pretty standard bracket matching problem but they layered on a follow-up that tripped me up more than I expected.
  • Given a string of bracket characters, write a function to determine if the brackets are valid (every opening bracket has a matching closing bracket in the correct order). Start with only parentheses, then extend to all three bracket types.

“Part A felt easy and I went straight to a counter, just incrementing on '(' and decrementing on ')'.”

View Post

LinkedIn·Data Scientist·Technical Phone Screen

May 2026
LinkedIn data science interview focused entirely on newsfeed health, four questions deep into metrics, experimentation, and the tricky balance between engagement and actual user satisfaction. Pretty analytical throughout, no fluff.
  • What engagement and revenue metrics would you track for the LinkedIn newsfeed, and how would those differ at a daily versus monthly granularity?
  • If you saw a spike in engagement metrics, how would you figure out whether it reflects a real quality improvement or just a short-term bump?
  • Walk me through how you'd design an analysis to causally attribute changes in feed metrics to specific product changes that were made.
  • How do you think about the tension between maximizing time spent on the feed versus keeping users satisfied and retained over the long run?

“I went through the obvious stuff first: DAU, feed scroll depth, click-through on posts, time spent.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn software engineering interview that went deep on memory management fundamentals. One question, but it had a lot of moving parts and I felt like I was juggling too many comparisons at once.
  • Explain the heap and the stack in process memory. Compare them across allocation management, cost of allocation and deallocation, lifetime and scope, growth direction, fragmentation, thread safety, and typical contents. Also walk through when objects land on each, and what causes a stack overflow versus an out-of-memory error.

“This question looks like one thing but it's actually like eight questions stapled together.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn software engineer interview with a classic grid traversal problem. Nothing too surprising but it's the kind of question where you either see it immediately or you spend five minutes staring at the grid like it owes you money.
  • Given a 2D grid of '1's (land) and '0's (water), count the number of islands, where an island is a group of land cells connected horizontally or vertically.

“Classic BFS/DFS flood fill.”

View Post