I had a pleasant interviewer, but I'm disappointed with the interview process. My interviewer didn't ask any resume or behavioral questions. Instead, he just introduced himself and went straight to the coding question (which is fine). The question itself was taken straight from the top-tagged LC questions for LinkedIn, so I had seen it before and already practiced solving it.
I wrote out my solution in Python, explaining it as I went, and was satisfied that it worked (again, because I had already done this question correctly on LC). My interviewer used Java, so he had trouble understanding a technique I used on arrays that's only found in Python. I tried to explain what it would do, but he didn't believe that it would work correctly. I wasn't going to sit there and argue with him, so he asked me to take a different approach to the question. This is fine, I suppose, but I was already put off by the fact that he wouldn't listen to me explaining how this would work in Python.
I gave another solution to the problem using recursion, which he was satisfied with, and then I was rejected the next week. I saw the rejection coming, as I figured he wouldn't be impressed with my technical skills since he didn't believe my solution would work.
If an interview is language-agnostic, then to avoid situations like this, they should at least let candidates use the compiler in CoderPad so this doesn't happen. This could have been easily avoidable if the compiler was enabled and I could've run my script to show that it did indeed work. Instead, because my interviewer didn't know Python, I wasn't moved forward.
Nested list weight sum on LC.
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.