LinkedIn Software Engineer Onsite Coding Questions
139+ questions from real LinkedIn Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the LinkedIn Onsite Coding round test?
The LinkedIn onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
LinkedIn Software Engineer Onsite Coding Questions
Implement LRU Cache
Design and implement a data structure for LRU (Least Recently Used) cache. It should support the following operations: get and put. get(key) - Get the value (will always be positive) of the key if the
Reverse a String
## Problem Given a string `s`, reverse it and return the reversed string. ## Input - One line string `s`. ## Output - Print the reversed string. ## Constraints - `0 <= len(s) <= 10^5` - The string
LinkedIn SWE Infra Interview Experience for Software Engineer
Sharing my recent interview experience for a Software Engineer role at LinkedIn. Hope this helps others preparing for similar roles. ### Screening Round First 30 mins : Deep dive into past projects Se
Rejected from job and then got a request to chat over LinkedIn?
I was recently rejected from a position at a big tech company after the final round. One of the interviewers from the final round requested to connect on LinkedIn the same day that I got rejected whic
LinkedIn Software Engineer IC2 DSA Loop Interview Experience
This was 2nd round of DSA with LinkedIn. Duration - 60 mins Number of Questions - 2 1. Max consecutive 1's in circular format. https://leetcode.com/problems/max-consecutive-ones-ii/description/ replac
Onsite Fulltime SDE Interview Experience at LinkedIn with 6 Years Experience
Finding a job is tough, please give me some points! 🙏🙏🙏🙏 To be honest, the interview went so-so. My coding skills definitely need more practice, so failing is normal. Plus, with 6 years of experience,
LinkedIn Onsite Interview Experience for SDE Infrastructure Role
I recently finished my LinkedIn SDE Eng infra track interview and wanted to give back to the forum. Interview: Two original questions on nested listed weight sum. League of Legends Interviewers: 339,
LinkedIn Onsite Interview Experience and Question Breakdown
Two and a half weeks ago, I had an onsite interview with LinkedIn. Still no news, probably failed. Phone interview: 4 questions, nested integer sum, max subarray sum + max subarray prod, binary tree d
LinkedIn Staff Software Engineer Onsite Interview Experience (US)
**Role:** Staff Software Engineer at LinkedIn (US) **Session Structure** * **Introduction:** 5 minutes * **Behavioral Segment:** 20 minutes **Coding Problem Statement** Design and implement a Max Stac
LinkedIn Senior Software Engineer (System and Infra) USA Interview Experience
**Technical Screening** The round included the "Number of Islands" coding problem, a 30-minute discussion on past projects, and a review of OS fundamentals (processes, threads, semaphores, mutexes, PC
LinkedIn | Phone | Array/String Based Question
Introductions took 3-5 mins. Coding 3 coding questions 1 Easy 2 Medium Was able to solve all with optimal time and space complexity. After 3 days, I got invitation to do virtual onsite....
LinkedIn | SDE | California | April 2022
Current experience: 3.5yrs SDE Gave my video call live coding round today. 1 easy, 1 medium asked in 1hr interview. Maximum sum subarray, Search in Rotated Sorted Array. Solved both and was invited for...
Amdocs | Backend Dev | Virtual | Nov - 2021 | Rejected
Status: 2020 Grad , Normal Private College (Tier 3/4) Company at that time : Infosys (Digital Specialist Engineer) Position they offer: SDE1 Location: Pune, INDIA Date: Nov 2021 Applied Thorugh : Refferal on Linkedin. This is...
Linkedin | Onsite | Stream of temperatures
There is an infinite stream of daily temperatures, design a data structure which allows to perform operations such as: - addTemperature(Date date, int temperature) // adds new temperature value at...
LinkedIn | Phone | SQRTX/Maximum Subarray
Just wanted to help you guys out if you\'re interviewing for LinkedIn\'s mobile positions! Split into 2 parts: Conceptual and Typical Algorithms part We started out with introductions. He was an iOS...
Linkedin | Onsite SSE | Concurrency
Giving back to the community. For those wondering about concurrency round, this is what i received on my onsite. https://leetcode.com/discuss/interview-question/341504/uber-implement-scheduledexecutorservice The interview mentioned the code must be working code. If you code in...
Company: LinkedIn YOE: < 1 Role: iOS Software Engineer, Flagship Question: https://leetcode.com/problems/all-oone-data-structure/ Hope this helps! PS. If you\'re asking me if I think I got the offer, I got grilled hard on this question. The...
Linkedin | onsite | pizza cut
/ Description: Given a pizza, how many pieces can you get by making n straight cuts (The pieces need not be of equal size). More formally, what is the maximum number...
LinkedIn | Onsite | Find the kth maximum product
Given two unsorted arrays A1 and A2 containing negative and positive integers of different lengths, find the kth maximum product of A1[i] A2[j] ( a number from A1 number from...
LinkedIn | Onsite | Split an array into K equal sum subsets
Hello, I received the below question during onsite some days ago. Actually I could not resolve it within time and submitted uncompleted solution using backtracking approach. I solved it after the...
What to Expect in the LinkedIn Onsite Coding Round
The LinkedIn Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 139+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at LinkedIn show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at LinkedIn typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at LinkedIn Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 139 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access