LinkedIn

LinkedIn Software Engineer Phone Screen Questions

133+ questions from real LinkedIn Software Engineer Phone Screen rounds, reported by candidates who interviewed there.

133
Questions
8
Topic Areas
10+
Sources

What does the LinkedIn Phone Screen round test?

The LinkedIn phone screen typically lasts 45-60 minutes and evaluates core Software Engineer fundamentals. Candidates should expect 1-2 algorithmic problems, basic system design discussion at senior levels, and questions about relevant experience. The goal is to confirm technical competence before bringing candidates onsite.

Top Topics in This Round

LinkedIn Software Engineer Phone Screen Questions

Given a standard binary tree, print the maximum value in each possible path from the root of the tree to the leaf as a list Any approach or similar question?

Interview started with introduction and background and explain about the most interesting project and challenges faced. Location : Sunnyvale. Then 2 coding questions https://leetcode.com/problems/valid-parentheses/ (With some integers and special characters also as part...

Telephone screen round Started with a brief Introduction Asked to draw an HLD of the current services you\u2019re working upon - TPS in each service - Queuing write semantics - DB consistency levels - Authorization...

LinkedIn SWE IC2 Infra Phone Screening Experience

Graph,Bfs,Dfs,Nested List,Os 2026

Hey guys, I just went through the initial screening round. 1. Project deep dive (wanted to understand under how much scale I have worked) 2. Few CS fundamentals - Java basics - Process vs Threads 3. O

I recently interviewed for a Senior Software Engineer position at LinkedIn. Unfortunately, I didn't make it to the next round, but I wanted to share the questions and my experience to help others prep

LinkedIn Software Engineer Phone Screen: Weighted GetRandom Variation

Arrays,Hash Table,Probability Stats,Design 2026

Hi, got an interesting question in Phone screen interview. Hopefully it will help someone. Trying to share the idea of the question. the actual language might be different in the question. Linked has

1. **If it's a string with numbers, return true otherwise false** - [Valid Number](https://leetcode.com/problems/valid-number/description/) You're expected to figure out that it's valid number and com

Cleared coding round but rejected in interview , Here’s what I realized

Linked List,Sliding Window,Interview Anxiety,Communication 2026

I recently went through the placement process for a product-based company. The first round was a coding test with questions on Linked List and Sliding Window, and I was able to clear it confidently. N

LinkedIn Senior Software Engineer SSE Infrastructure Team Interview

Binary Tree,System Design,Graph,Stack,Behavioral,Os,Bfs 2026

Month of Interview : Feb 2026 YOE : 4 years I recently got the opportunity to interview for a SSE role at LinkedIn and felt like sharing the interview experience. # Phone Screen Round - Past projects

This post was last edited by Anonymous on 2025-10-02 14:19 I wasn't well-prepared for the store with Miss ABC. I couldn't solve one of the frequently tested hard coding problems. System & Infrastructu

LinkedIn Software Engineer Systems Infrastructure Interview Experience (2.5 YOE)

Os,Binary Search,Binary Tree,Heap,Sliding Window,Stack,System Design,Behavioral,Sql 2025

**Candidate Profile:** Software Engineer with 2.5 Years of Experience (YOE). **Phone Screen Round** * **Topics:** Operating System concepts, deep dive into past projects, and specific engineering chal

Pretty standard problem asked https://leetcode.com/problems/closest-leaf-in-a-binary-tree/description/. Instead of the closest leaf we needed to return the value. I discussed approach: > construct path from root to node > reverse iterate path & for each...

I had my LinkedIn onsite interview last week. Here\u2019s a summary of my experience: ### Phone Screen: - Solved 2 DSA questions, wrote optimal code for both. ### Onsite Rounds:...

I recently had the opportunity to interview for the SDE-1 Backend role at PhonePe, and I wanted to share my experience. The interview was conducted by Sahil Malik (LinkedIn). Round 1...

Round 1 : https://leetcode.com/problems/max-stack/description/ Eventhough I gave optimal solution, they still rejected. The interviewers were pretty much not interested to take interview.

Finally got a job

Oop,Behavioral,Career 2025

May 2025 CS Grad here. After almost 200 applications, finally got an entry level SWE job. Here’s how my interview process went. -90k base -10% yearly bonus -3000 shares -MCOL After a great first round

Recently had my screening round at Linkedin. There were two interviewers. Initial 10 minutes were basic resume discussion. 2 DSA questions were asked then:- 1. https://leetcode.com/problems/bulb-switcher/description/ - was presented in a...

Phone Screen -> Final vs finally, thread vs process, Os concepts like pagination and segmentation, about previous projects and what extra could I have changed in that. -> DSA - https://leetcode.com/problems/paint-house/description/?envType=company&envId=linkedin&favoriteSlug=linkedin-six-months **DSA ROUND...

First 3 - 5 mins -> Introduction Next 10 mins -> project discussion (with some technical follow ups) Next 40 mins -> 2 coding questions (1 Easy, 1 Medium) \t...

Talk about a project in depth. Java basic questions - inner class, mutex vs semaphore. Variant of https://leetcode.com/problems/letter-combinations-of-a-phone-number/description/ Given the standard mapping from English letters to digits on a phone keypad (1 \u2192...

What to Expect in the LinkedIn Phone Screen Round

The LinkedIn Software Engineer Phone Screen round has a specific calibration purpose distinct from other rounds in the loop. Across 133+ 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 Phone Screen round at LinkedIn show recurring patterns in difficulty and topic distribution. The Phone Screen 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.

Phone Screen Round Timing and Format

The Phone Screen 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 Phone Screen 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 133 Questions from This Round

Full question text, answer context, and frequency data for subscribers.

Get Access