First Telephonic Round:
Was cool. The interviewer asked two coding questions directly after the introduction and requested the use of CollabEdit. The coding questions were quite common and can be found on platforms like CareerCup, Glassdoor, or LeetCode. It's important to finish the first question quickly and as correctly as possible, as this makes a strong first impression and allows for more time on the second question. In my case, I couldn't solve the second problem completely, but my approach was correct.
Onsite Round:
A good experience. It started with a small campus tour and ended in a reserved, personalized huddle room. I was greeted by the recruiting manager, who gave a brief overview of all the upcoming rounds and discussed their expectations for each, which was very useful.
There were two coding rounds, one system design, one Project Manager, one Current Project, and one lunch round.
1st Coding Round:
A basic tree question with many variations added during the interview. The focus was on coding skills, so it's important to write code that can handle as many edge cases as possible. Since the problem was pretty basic, the interviewer kept changing or adding variations to it.
2nd Coding Round:
A very tough question. However, as told by the recruiter and interviewer, the focus in this round was more on problem-solving skills rather than writing complete code. I received sufficient hints, but I couldn’t fully solve the NP-hard problem.
Project Manager Round:
Resume scan, a close review of your career growth, and what you have achieved. Be ready to project your achievements as a coder and handle questions like "Why LinkedIn?". This was the only round where I was not standing and doing whiteboarding.
System Design Round:
As expected, this focused on design questions. The interviewer expected me to consider all aspects while designing a system, such as storage, concurrency, scaling, and performance. I received a very common system design question.
Current Project Round:
Nothing special, except for some additional questions like the ideal ways to ensure code quality.
Lunch Round:
Nothing special. Good food choices. This is the round where you can clear your doubts regarding LinkedIn.
Overall, a good experience. However, after one week, I am still waiting for feedback/results from the recruiters. Anyway, I am considering this as no offer. Good luck!
Problems that require the Binary Search technique.
Basic Binary Tree problems.
NP-Hard problems, Dynamic Programming.
The following metrics were computed from 22 interview experiences for the LinkedIn Senior Software Engineer role in Sunnyvale, California.
LinkedIn's interview process for their Senior Software Engineer roles in Sunnyvale, California is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for LinkedIn's Senior Software Engineer interview process in Sunnyvale, California.