LinkedIn Senior Software Engineer Interview Questions

1.Describe a time you had to build a working relationship with a difficult stakeholder—maybe a PM, designer, or engineer from another team—to ship something important. What made them difficult and how did you approach it?

2.Tell me about a time you took ownership of a problem that wasn't clearly your responsibility. What was the issue and why did you decide to own it?

3.Tell me about a time you pushed back on a product feature or engineering decision because you felt it wouldn't serve LinkedIn members well. What was the feature and how did you advocate for members?

4.Tell me about a time you raised the engineering bar for your team—maybe around code quality, testing, or development practices. What standard did you introduce and how did you get the team to adopt it?

5.Walk me through a time when you either gave tough feedback to a teammate or received feedback that was hard to hear. How did the conversation go and what changed afterward?

6.Describe a calculated technical or product risk you took that didn't work out as planned. What was the risk, why did you take it, and what did you learn?

7.You're on-call and get alerted that LinkedIn's Feed is serving stale content to millions of members. The ranking service is up but responses are cached from 6 hours ago. How do you debug this?

8.Write a function that determines if two LinkedIn members might know each other based on their connection graphs. You have access to each member's first and second-degree connections but need to respect privacy settings.

9.We want to add a 'skills gap analysis' feature to Learning that compares a member's current skills to job requirements. The naive approach queries across our Skills, Jobs, and Learning databases. How would you design this efficiently?

10.Our Recruiter product has a feature where users can save candidate searches. We're seeing 30-second timeouts when users load saved searches with complex filters. The database queries look optimized. What's your investigation approach?

11.LinkedIn's messaging system needs to support read receipts across mobile, web, and API clients. Each client has different connectivity patterns and we need to maintain exactly-once delivery guarantees. Design the backend architecture.

12.You're tasked with implementing a circuit breaker for Sales Navigator's lead generation service, which calls multiple external data providers. The service needs to maintain 99.9% uptime even when providers fail. Walk me through your implementation.

13.Design a system to recommend relevant courses to LinkedIn Learning members based on their profile and career goals. We have 40 million learners and need to serve personalized recommendations in under 200ms.

14.Design a content moderation system for LinkedIn's Feed that can review millions of posts per day for professional appropriateness, misinformation, and spam while preserving authentic professional discourse.

15.LinkedIn Jobs needs to detect and prevent fake job postings at scale. We see 10 million job posts per month and need to catch fraudulent listings before they reach members. How would you approach this?

16.Design the backend for LinkedIn's connection recommendation system - the 'People You May Know' feature. We need to suggest relevant connections for 800 million members while respecting privacy settings and avoiding awkward suggestions.

17.Sales Navigator needs a real-time lead scoring system that updates prospect scores as members change jobs, post content, or engage with company pages. The system serves 50,000 sales professionals and must handle 1 million member updates per hour.

18.LinkedIn Recruiter needs a candidate search system that can handle complex boolean queries across 800 million profiles with sub-second response times. How would you design the indexing and search architecture?

19.Tell me about a time you had to influence a team or engineer from another org to adopt a solution you proposed. How did you approach it when you had no direct authority over them?

20.Tell me about a time you had to develop and mentor a struggling engineer on your team. What was your approach and what was the outcome?

21.Describe a time when you had to make a technical decision that impacted multiple teams at LinkedIn. How did you communicate that decision across the organization?

22.Tell me about a time you had to convince your team to slow down and invest in technical debt or infrastructure when there was pressure to ship features quickly.

23.Walk me through a time when you had to lead an incident response or major production issue that affected LinkedIn members. How did you coordinate across teams during the crisis?

24.Describe a time when you disagreed with a product or engineering decision that was being made by leadership above you. How did you handle that disagreement?

25.LinkedIn's job recommendation algorithm serves 50 million members daily. If we increase our recommendation pool from 10 to 20 jobs per member, estimate the additional infrastructure cost and storage requirements.

26.Sales Navigator shows a 15% drop in lead exports but user sessions are flat. No new releases went out and infrastructure metrics look normal. Walk me through your diagnostic approach.

27.LinkedIn Learning wants to launch in India where internet connectivity is inconsistent and data costs are high. Estimate the technical and business challenges we'd need to solve for 100 million potential users.

28.LinkedIn's Feed ranking algorithm needs to balance member engagement with content quality. If we increase the weight of 'time spent reading' by 20%, estimate the impact on professional vs. viral content distribution.

29.LinkedIn Recruiter processes 2 billion candidate searches per month. If we add semantic search capabilities using LLMs, estimate the computational cost and infrastructure requirements needed.

30.LinkedIn's connection growth has slowed 5% quarter-over-quarter while new member registrations remain steady. Estimate how this impacts our network effects and long-term member engagement.