I was contacted by a recruiter and scheduled two rounds of technical phone interviews. The first round started on time, but the interviewer for the second round canceled at the last minute. No one informed me until I had waited over 30 minutes. After the second round, I received a thank-you email. The recruiter and one of the engineers had heavy accents, which made communication a little more difficult.
The interview process was standard. First, the engineer explained their role at LinkedIn and then asked about my most interesting recent project. They seemed to ask this question because they were instructed to, rather than out of genuine interest. After that, the interview involved typical coding algorithm problems, some harder than others. If you spent too much time on one question and didn't get to multiple problems, it probably meant you wouldn't proceed to the next round. Expect to solve two to three problems.
Given a target and a sorted array, find the element that is strictly larger than the target. i.e. {a,c,d,e}, target b -> output: c
Find the maximum sum of a continuous sequence in the array. {2, -1, 3, -5, 3} -> output: 4
Given a DNA sequence, find a pattern (hardest problem that you probably won't be expected to finish).
Given intervals, find the overlap and return the length. (It is surprising how easy it is to make mistakes in this one; I ended up spending too much time fixing my own bug.)
The following metrics were computed from 285 interview experiences for the LinkedIn Software Engineer role in United States.
LinkedIn's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for LinkedIn's Software Engineer interview process in United States.