← Back to Directory

LinkedIn interview notes, page 14 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·Software Engineer·Technical Phone Screen

May 2026
LinkedIn technical screen, one question about MapReduce, pretty bare bones. Not much else to report.
  • Explain how MapReduce works.

“Covered the basics, map phase splits and transforms data, reduce phase aggregates it.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

May 2026
Got a product improvement question about Headspace in what seemed like a product sense round at LinkedIn. Not a ton of context to go on but the question itself is a classic.
  • How would you improve Headspace?

“Classic product improvement format.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

May 2026
Stumbled across this question in what seemed like a product strategy round at LinkedIn. Not much context to go on, but it's a classic acquisition rationale question.
  • Why did Facebook acquire Instagram?

“I've seen this one before so I wasn't totally lost, but I still fumbled the structure a bit.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn Software Engineer interview with a binary search coding problem. Pretty focused session, just the one algorithmic question but it had a few gotchas worth knowing about.
  • Given a positive integer n, determine if it is a perfect square without using any built-in square root functions. Your solution should run in O(log n) time.

“The binary search angle is pretty clear once you think about it for a second, but the part that actually tripped me up was the overflow.”

View Post

LinkedIn·Software Engineer·Onsite - System Design / Architecture

May 2026
LinkedIn system design round for a software engineer role. The whole session was basically one big question about job scheduling, with a follow-up that caught me more off guard than the main part did.
  • Design a scalable, fault-tolerant job scheduling system that supports one-time and recurring background jobs, with guarantees around execution reliability and no job loss.
  • How would you design the data model for jobs, including what fields to store and how to index them to support both scheduling and efficient time-range queries?
  • Design an API and storage query strategy to efficiently fetch all jobs scheduled within the next N hours for a near real-time dashboard, given high QPS and variable N per request.

“I started with requirements which felt right, but I spent too long on the functional side and the interviewer had to nudge me toward non-functionals.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed at LinkedIn for a product role, and the main question was about whether LinkedIn should localize the developer experience. Not a ton of detail to share but it was a product strategy type discussion.
  • Should LinkedIn localize the developer experience for different regions or markets?

“This one pulled me in two directions pretty fast.”

View Post

LinkedIn·Product Manager·Onsite - Product Sense / Strategy

May 2026
Product strategy question for what seems like a PM role at LinkedIn, just the one question about whether Airbnb should move into furniture. Short but the kind of thing that can spiral if you're not careful about scoping.
  • Should Airbnb enter the furniture market?

“My first instinct was to just say yes and start listing reasons, which would've been a mess.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn SWE interview where they had me write a custom map function from scratch in vanilla JS and wire it up to the DOM. No frameworks, no libraries, just a script tag and whatever you can remember about how the browser works.
  • Using only vanilla JavaScript in a script tag, implement a function similar to Array.prototype.map that works on both arrays and key-value objects, then use it to render one div per transformed item into the DOM with proper classes and attributes, and handle empty input and error states.

“This is deceptively wide for a single question.”

View Post

LinkedIn·Product Manager·Hiring Manager Screen

May 2026
LinkedIn PM interview, just the one question from what I can tell. Not much context to go on but it's a solid behavioral question worth thinking through.
  • What are some of the best practices you've seen from PMs you've worked with?

“This one tripped me up a bit because it sounds easy but you can ramble forever if you're not careful.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

May 2026
LinkedIn technical interview, one question about domain-specific challenges that came up during program execution. Pretty sparse on details but the question itself had some meat to it.
  • What domain-specific technical challenges have you run into during program execution, and how did you go about solving them?

“Broad question but it's actually kind of a trap if you try to answer it generically.”

View Post