LinkedIn Software Engineer interview questions

78 Software Engineers have shared notes from their LinkedIn interviews, with the questions they were asked in each round. That is 65% of the 120 LinkedIn interview notes on Screna AI.

78 Software Engineer interview notes

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·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·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·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn coding screen for a software engineer role, just one algorithm question the whole time. Pretty standard vibe, nothing unexpected.
  • Given a non-negative integer n, determine whether it is a perfect square without using any built-in square root function. Your solution should run in O(log n) time.

“My first instinct was to just iterate from 1 upward and multiply each number by itself until I hit n or exceeded it.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn system design round for a software engineer role, centered on a pretty gnarly extension of a classic LC problem. The interviewer pushed hard on tradeoffs and I don't think I gave clean enough answers on the eviction side.
  • Design a data structure supporting insert(value, ttl), remove(value), and getRandom(), where each inserted item has a time-to-live after which it should be invisible to getRandom. Keep all operations as close to O(1) amortized as possible, and handle duplicate values with different TTLs.
  • Compare lazy expiration versus active eviction strategies (such as a priority queue or timer wheel) for this TTL-based structure. What are the tradeoffs?

“This is basically LC 381 with a TTL layer bolted on, which sounds manageable until you realize getRandom is the part that breaks.”

View Post

LinkedIn·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
LinkedIn behavioral round for a software engineer role, three questions back to back covering conflict, hard projects, and a time you dropped the ball. Pretty standard format but the failure question was the one that actually made me think.
  • Tell me about a conflict you had with a peer, manager, or stakeholder and how you resolved it.
  • What is the most challenging project or technical problem you have worked on, and how did you handle 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 for this but halfway through I realized I was making myself sound too right and the other person too wrong.”

View Post

LinkedIn·Software Engineer·Technical Phone Screen

Jun 2026
LinkedIn coding interview, one question about bracket validation. Pretty standard stuff but worth knowing cold if you're interviewing there.
  • Given a string made up of only parentheses, curly braces, and square brackets, write a function to determine whether the string is valid. Valid means every opening bracket is closed by the matching type, and in the right order.

“Classic stack problem.”

View Post