The hiring process began with a brief, non-technical phone interview with the hiring manager. I was then invited for an onsite interview that was initially scheduled for three hours.
A day before the interview, the recruiter informed me that it had been shortened to 45 minutes. A couple of engineers met me in the lobby; they seemed unprepared, as they were looking for empty conference rooms at the interview's start time.
The technical questions were generally easy. If you know basic data structures, algorithms, and Big O notation, you should be well-prepared (definitely not as hard as Google interviews). The interviewers were very nice and professional.
I received the following feedback after the interview:
"Interview went well. I synced up with the interviewers and, based on their feedback, the candidate has very limited technical skills geared towards C++ and a little bit of scripting. It's a reject from our end."
It's funny because the reason I applied for this requisition was that it stated, "Extensive programming experience in Objective C or C/C++."
Feedback to the hiring manager: You should get your requirements straightened out before putting out a requisition.
Basic data structures, algorithms, and Big O notation.
Should be able to apply algorithms such as binary search, hashing, etc., as and when needed.
The following metrics were computed from 1 interview experience for the LinkedIn Software Development Engineer In Test role in Mountain View, California.
LinkedIn's interview process for their Software Development Engineer In Test roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for LinkedIn's Software Development Engineer In Test interview process in Mountain View, California.