HR interview questions
Common LinkedIn HR/culture questions, sample answer frames, and STAR tips.
LinkedIn Interview Experiences
Overview
Section titled “Overview”How LinkedIn’s loop actually runs for engineering candidates, based on aggregated candidate reports (Blind, Glassdoor, GeeksforGeeks) and LinkedIn’s own careers pages. Panel-to-panel variation is real here, so treat this as a prep map, not a script.
Reported India-based, entry-level Software Engineer total compensation sits roughly in the ₹20-45 LPA range per public aggregators (levels.fyi, Glassdoor), skewed heavily by level, location, and stock refreshers - treat this as an approximate reported band, not a guaranteed offer, since LinkedIn hires selectively at this level.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What it tests |
|---|---|---|
| Recruiter screen | 20-30 min | Background, motivation for LinkedIn, comp expectations, logistics |
| Technical phone screen | 45-60 min | 1-2 coding problems (LeetCode-medium), CS fundamentals |
| Onsite - Coding (1-2 rounds) | 45-60 min each | DSA medium-to-hard, code quality, dry-running test cases out loud |
| Onsite - System design | 45-60 min | LinkedIn-scale systems: typeahead search, feed ranking, notifications |
| Onsite - Hiring manager / behavioral | 45-60 min | Culture add, STAR stories, motivation, collaboration |
| Team matching (post-offer) | 1-2+ weeks | Matches you to a team with open headcount - after the loop, not during |
Real interview experiences
Section titled “Real interview experiences”Experience 1: Software Engineer (2025, off-campus)
Section titled “Experience 1: Software Engineer (2025, off-campus)”Profile: B.Tech CSE, ~7.8 CGPA, tier-2 college, one internship, steady LeetCode practice, applied off-campus after not seeing LinkedIn at any campus drive
Recruiter screen
- 25-minute call: current role, why LinkedIn, notice period, and comp expectations. No coding.
Technical phone screen
- Two interviewers on the call. First problem: find the lowest common ancestor of a binary search tree, with a follow-up asking what changes if the tree isn’t a BST.
- Second problem: longest substring without repeating characters (sliding window + hashmap) - interviewer wanted the solution dry-run against an edge case (empty string) before moving on.
Onsite - coding rounds
- Binary tree level-order traversal, then a follow-up on handling a tree that isn’t balanced.
- A design-a-data-structure question: support adding words and searching with wildcard pattern matching (trie-based).
Onsite - system design
- Asked to design a typeahead search box for people and companies - discussion covered prefix indexing, ranking suggestions, and how to keep results fresh as connections change.
Onsite - behavioral round
- “What are the three things most important to you in a job?”
- “Tell me about a time in the last week you felt satisfied, energized, and productive at work.”
- Conversational tone, but the interviewer pushed for specifics rather than accepting the first answer.
Result: Selected What helped: Talking through the approach before coding, dry-running edge cases without being asked twice, and giving a specific, recent example in the behavioral round instead of a rehearsed story.
Experience 2: Software Engineer (2024-2025, referral)
Section titled “Experience 2: Software Engineer (2024-2025, referral)”Profile: B.Tech IT, ~7.3 CGPA, strong personal projects, applied via an employee referral after LinkedIn wasn’t part of the college’s placement cycle
What differed
- The technical phone screen included a CS-fundamentals detour: OOPs concepts (polymorphism, with a real project example) before the coding problem.
- The onsite system design round leaned into a notification system: how connection-accepted and profile-view events reach a user in near real time, and what happens if the user is offline.
- A coding round asked for the inclusive and exclusive time of functions given a call-stack log - a stack-based simulation problem rather than a textbook pattern.
Mistakes that hurt other candidates in the same hiring cycle
- Jumping into code before clarifying constraints on the coding rounds
- Treating the behavioral round as a formality instead of a real evaluation
- Giving system-design answers that named buzzwords (sharding, caching) without a concrete bottleneck or trade-off
Result: Selected after the behavioral round; matched to a team about two weeks after the offer Takeaway: A clear, calm walk-through of the approach - plus one honest, specific behavioral story - carried more weight than reciting textbook system-design vocabulary.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Find the lowest common ancestor of a binary tree / binary search tree
- Longest substring without repeating characters - sliding window + hashmap
- Binary tree level-order traversal - BFS, with an unbalanced-tree follow-up
- Inclusive/exclusive time of functions given a call-stack log
- Design a data structure that supports adding words and pattern-matching search (trie)
- Merge intervals / overlapping intervals
- Top-K frequent elements (heap-based)
System design
Section titled “System design”- Design a typeahead/autocomplete search box for people and companies
- Design LinkedIn’s News Feed and how it ranks content
- Design a notification system (connection accepted, profile view, new comment)
- Design a key-value store or rate limiter, with failure-mode follow-ups
Behavioral
Section titled “Behavioral”- What are the three things most important to you in a job?
- Tell me about a time in the last week you felt satisfied, energized, and productive at work
- Tell me about a time you dealt with a difficult teammate or stakeholder
- Why LinkedIn, and what do you know about the team you’re interviewing for?
Practical tips for LinkedIn
Section titled “Practical tips for LinkedIn”- Clear the technical phone screen first - narrating your approach and dry-running test cases matters as much as reaching a working answer.
- For system design, ground your answer in LinkedIn’s actual product surface (search, feed, notifications) instead of a generic distributed-systems template.
- OOPs fundamentals still open some LinkedIn panels. Do not skip the basics assuming they only ask hard DSA.
- Behavioral answers should be specific and recent. LinkedIn’s “culture add” framing rewards a genuine, particular story over a polished, generic one.
- Since LinkedIn hires centrally, be ready to talk about broad interests (what kind of problems you want to work on) rather than only the one team you saw in the job posting - you may be matched elsewhere after the offer.
HR interview
Section titled “HR interview”After technical rounds, LinkedIn’s hiring-manager/behavioral round doubles as its HR conversation: motivation, collaboration style, and a couple of closing logistics questions. Prepare those answers on the dedicated page rather than cramming them into this hub.