← Back to Directory

LinkedIn

Large Enterprises

Most of these LinkedIn write-ups come from Software Engineers (78), then Machine Learning Engineers (21) and AI Engineers (16). The most reported rounds are the technical phone screen (81), the system design round (22), the behavioral / leadership round (11) and the hiring manager screen (3).

120 interview notes · updated Jun 2026

LinkedIn·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn SWE coding round, basically a DP problem on house painting with a twist. The naive solution gets you partway there but they clearly wanted the optimized version, so knowing your DP tricks matters here.
  • Given n houses in a row and k colors, where costs[i][j] is the cost of painting house i with color j and no two adjacent houses can share the same color, find the minimum total cost to paint all houses. Then optimize your DP solution from O(n*k^2) to O(n*k).

“The basic DP setup clicked pretty fast for me.”

View Post

LinkedIn·AI Engineer·Onsite - Multi Round

Jun 2026
LinkedIn AI Engineer loop with a combined round that split time between ML fundamentals and system design. Nothing too exotic but the breadth meant you couldn't really specialize your prep.
  • Walk through the core ML fundamentals: loss functions, regularization, and the bias-variance tradeoff.
  • What are the tradeoffs between classical ML approaches and deep learning, and when would you choose one over the other?
  • Explain how transformer architectures and attention mechanisms work.
  • How do embeddings work and how are they used in practice?
  • What evaluation metrics would you use for an ML model and how do you choose between them?
  • Design an end-to-end ML system relevant to the team's domain, covering data ingestion, feature engineering, model training, serving infrastructure, monitoring, and A/B testing.

“Felt fine on loss functions and regularization but the bias-variance piece always trips me up when they push past the textbook answer.”

View Post

LinkedIn·AI Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at LinkedIn for an AI Engineer role. One question, pretty meaty, focused on how you handle getting stuck when something outside your control is blocking the work.
  • Describe a situation where a dependency outside your control (another team, an external service, missing infrastructure) blocked you on something critical. How did you figure out what was wrong, what did you do to move things forward, and what happened?

“This one tripped me up a bit because my first instinct was to tell a story where I just escalated and it got fixed.”

View Post

LinkedIn·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Two behavioral questions for a software engineer role at LinkedIn. Nothing too wild but the second one required more concrete detail than I expected.
  • Describe a time you had to get your manager and other stakeholders on board with a project to secure resources. How did you frame the pitch, what pushback did you get, and how did you handle it?
  • How do you avoid becoming a single point of failure on your team? Walk through a specific example where you shared knowledge, documented something, or helped others grow to reduce that dependency.

“I had a decent story ready for this but fumbled the middle part where they asked specifically how I handled the concerns raised.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn coding screen for a software engineer role, one question the whole time centered on a data structure design problem. Pretty standard vibe but the follow-up about getRandom tripped me up more than I expected.
  • Design a data structure that supports insert, remove, and getRandom, all in average O(1) time. Each element in the set must have an equal probability of being returned by getRandom.

“I knew the array plus hashmap combo going in, which helped.”

View Post

LinkedIn·Software Engineer·Onsite - System Design / Architecture

Jun 2026
LinkedIn system design round, basically a follow-up to an earlier BFS coding question but scaled up to a production context. No coding, just a long discussion about how you'd actually run that algorithm on a graph with hundreds of millions of nodes. Way more open-ended than I expected.
  • You've built a BFS-based shortest-distance function between two users on a connection graph. Now imagine this runs in production on a graph with hundreds of millions of nodes. How do you design and optimize it?

“This one sprawled in every direction.”

View Post

LinkedIn·Machine Learning Engineer·Technical Phone Screen

Jun 2026
LinkedIn ML Engineer interview that focused pretty heavily on regularization and model diagnostics. Two main topics, nothing too wild, but the L1 vs L2 question had more depth to it than I expected going in.
  • What is overfitting and underfitting, and how do you tell which one you're dealing with from your training and validation curves?
  • Walk me through the main strategies you'd use to reduce overfitting in a model.
  • What's the difference between L1 and L2 regularization, and when would you actually choose one over the other?

“Pretty standard setup question but I fumbled the curve part a bit.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn software engineer interview, got a binary search problem that looks straightforward until you realize you need two separate searches. Pretty standard for this type of role but the O(log n) constraint is what makes it non-trivial.
  • Given a sorted array of integers, find the first and last position of a target value. Return [-1, -1] if the target doesn't exist. Must run in O(log n) time.

“My first instinct was to find any occurrence and then scan left and right, which is obviously O(n) and not what they want.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn SWE interview that went pretty deep on OS fundamentals. Virtual memory came up and I was not as prepared as I thought I was.
  • Explain virtual memory: how it works, why it exists, and what the trade-offs are.

“I started okay, got the basic idea out (each process thinks it owns a big contiguous address space, page tables map that to physical RAM via the MMU and TLB), but then I started fumbling when they pushed on demand paging.”

View Post

LinkedIn·AI Engineer·Onsite - System Design / Architecture

Jun 2026
LinkedIn AI Engineer system design round focused entirely on building an LLM-powered recruiter outreach tool, end to end. Pretty deep dive covering everything from retrieval pipelines to compliance to feedback loops. Felt like a real product they're thinking about internally.
  • Design a system that helps recruiters write personalized outreach messages to candidates using an LLM. Walk through the full system from recruiter login to message generation.
  • What are the functional and non-functional requirements you'd define for this system before designing anything?
  • How would you structure the retrieval pipeline to pull the right context for message generation?
  • How would you handle LLM serving given latency and cost constraints, and what's your fallback strategy?
  • How would you evaluate whether the generated messages are actually good, both offline and in production?
  • What safety and compliance concerns would you address, specifically around PII and potential bias in message generation?
  • How would you use recruiter edits to the generated messages as a feedback signal to improve the system over time?

“This was the whole interview basically.”

View Post

LinkedIn interview FAQ

What rounds are in the LinkedIn interview?

Candidates most often report a technical phone screen (81 write-ups), a system design round (22), a behavioral / leadership round (11) and a hiring manager screen (3).

What does the LinkedIn technical phone screen cover?

Across 81 technical phone screen write-ups, the most tagged question topics are Algorithms & Data Structures (93 questions), Technical Trade-offs (82) and System Design (26).

What is asked in the LinkedIn system design round?

Across 22 system design write-ups, the most tagged question topics are System Design (39 questions), Technical Trade-offs (30) and Data Modeling (11).

LinkedIn interview guides by role

78 notes

LinkedIn Software Engineer interview questions

21 notes

LinkedIn Machine Learning Engineer interview questions

16 notes

LinkedIn AI Engineer interview questions