Linkedin | SSE | Oct 2025 | Rejected
- Result
- Rejected
- Posted
- 1 Dec 2025
Summary
I interviewed for a Senior Software Engineer (SSE) role at Linkedin in October 2025. The process involved multiple rounds, and despite strong performance in some areas, I was ultimately rejected due to my answers lacking the expected depth for an SSE level.
How it went
I interviewed for a Senior Software Engineer (SSE) role at Linkedin in October 2025. The process involved multiple rounds, and despite strong performance in some areas, I was ultimately rejected.
Round 1 - Technical Problem Solving (TPS)
This round involved a mix of technical discussions and a DSA question. I was asked to:
- Discuss any issues I've found in systems during my work, such as performance bottlenecks or poor code quality.
- Share my mentoring experience.
- Explain software design patterns and their importance.
- Describe the CAP theorem.
- Differentiate between concurrency and parallelism.
- Determine the output of a given multithreading code snippet.
- Solve the "Diameter of a Binary Tree" problem.
- Design an API capable of handling 10,000 queries per second (QPS) for write traffic.
I received a "Hire" verdict for this round.
Onsite Rounds
Round 2 - Data Structures & Algorithms (DSA)
In this DSA round, I faced three problems:
- An adaptation of Insert Delete GetRandom O(1), specifically focusing on implementing a
removeRandommethod. - A follow-up based on Insert Delete GetRandom O(1) - Duplicates Allowed.
- A problem conceptually similar to Number of Islands, but presented within a real-world story context.
I received a "Strong Hire" verdict for this round.
Round 3 - Data Structures & Algorithms (DSA)
This DSA round had two problems:
- Closest Binary Search Tree Value II: I could only develop an O(N) solution, while the interviewer was looking for an O(logN) approach using predecessors and successors.
- Intersection of Two Linked Lists.
The verdict for this round was "No/Lean Hire".
Round 4 - High-Level Design (HLD)
I was asked to design a notification system. This involved considering aspects like rate limiting for different notification categories (e.g., 5 marketing notifications per day per user) and handling user preferences. Additionally, there was a discussion on how I measure project success, including performance testing and metrics like p90.
The verdict for this round was "No/Lean Hire".
Round 5 - Hiring Manager (HM) & Behavioral
This round covered a mix of behavioral questions and another system design challenge. Behavioral questions included:
- My reasons for switching from my previous role.
- Differences I observed between my current and previous companies.
- My experience with ops work and on-call duties.
- A conflict I faced with management and how I resolved it.
- How I keep up with the tech industry, particularly during a career break.
- An interesting tech article I've read, where I cited Discord's blog on indexing trillions of messages.
- My technical growth over the past year.
The system design problem was to design a system to route leads to sales representatives. Key requirements included routing individual leads based on timezone and region, allowing the product team to configure rules, sales reps checking leads via UI or email, and lead scoring, all while handling 15,000 leads per day.
The verdict for this round was "Lean Hire".
Overall, the recruiter provided detailed feedback, indicating that my answers, particularly in the system design and depth expected for an SSE, were lacking. Despite the rejection, the process was smooth, and the feedback was appreciated.
Questions asked (23)
- 01
Discuss System Issues
Other
Discuss any issues encountered in a previous system, focusing on performance, poor code, or similar aspects.
- 02
Mentoring Experience
Behavioral
Discuss your experience with mentoring others.
- 03
Software Design Patterns
Other
Explain what software design patterns are and why they are important.
- 04
CAP Theorem
Other
Explain the CAP theorem.
- 05
Concurrency vs. Parallelism
Other
Explain the difference between concurrency and parallelism.
- 06
Multithreading Code Output
Other
Determine the output of a given multithreading code snippet.
- 07
Diameter of a Binary Tree
Data Structures & Algorithms · Easy
Open the problemFind the diameter of a binary tree.
- 08
API Design for High Write Traffic
System Design
Design an API capable of handling 10,000 queries per second (QPS) for write traffic.
- 09
Insert Delete GetRandom O(1) (Customized)
Data Structures & Algorithms · Medium
Open the problemImplement the
Insert Delete GetRandom O(1)data structure, but with aremoveRandommethod instead ofgetRandom. - 10
Insert Delete GetRandom O(1) - Duplicates Allowed
Data Structures & Algorithms · Hard
Open the problemImplement the
Insert Delete GetRandom O(1)data structure, allowing for duplicate elements. - 11
Number of Islands (Story-wrapped)
Data Structures & Algorithms · Medium
Open the problemSolve a problem with logic similar to 'Number of Islands', presented within a story context.
- 12
Closest Binary Search Tree Value II
Data Structures & Algorithms · Hard
Open the problemGiven the root of a binary search tree and a target value, return k values in the BST that are closest to the target. I initially developed an O(N) solution, but the interviewer was looking for an O(logN) approach involving predecessors and successors.
- 13
Intersection of Two Linked Lists
Data Structures & Algorithms · Easy
Open the problemGiven the heads of two singly linked lists
headAandheadB, return the node at which the two lists intersect. If the two linked lists have no intersection at all, returnnull. - 14
Design a Notification System
System Design
Design a scalable notification system. Key requirements include implementing rate limiting for various notification categories (e.g., maximum 5 marketing notifications per user per day) and managing user preferences for different types of notifications.
- 15
Measuring Project Performance and Success
Other
Discuss how project performance and success were measured. This includes details on performance testing methodologies and specific metrics observed, such as p90 latency.
- 16
Reason for Previous Job Change
Behavioral
Discuss the reasons for your previous job change.
- 17
Differences Between Companies
Behavioral
Describe the observed differences upon joining your current company compared to your previous one.
- 18
Experience with Operations/On-Call Work
Behavioral
Discuss any experience you have with operations work, on-call duties, or similar responsibilities.
- 19
Design a Lead Routing System
System Design
Design a system to route leads to sales representatives efficiently. The system should handle approximately 15,000 leads per day, routing each lead individually to sales people based on criteria such as timezone and region. The product team must be able to configure routing rules, and sales representatives should be able to view leads via a UI or receive email notifications. Incorporate lead scoring into the design.
- 20
Conflict with Management
Behavioral
Describe a conflict you faced with management and how you handled the situation.
- 21
Staying Current with Tech During Career Break
Behavioral
Explain how you have kept up with advancements in the tech industry during a career break.
- 22
Interesting Tech Article/Topic
Behavioral
Open the problemShare one interesting thing you have recently read about in the tech industry. I specifically mentioned Discord's approach to indexing trillions of messages.
- 23
Technical Growth Over Past Year
Behavioral
Describe your technical growth and development over the past year.
How they prepared
After the interview and receiving feedback, I decided to continue grinding on LeetCode problems and focus specifically on diving deeper into system design research to strengthen those areas.