LinkedIn Principal Software Engineer Interview Questions & Reviews
Overview |
| |
Salaries |
| |
Reviews |
| |
Interviews |
| |
Photos |
| |
Jobs |
| |
|
Updated Dec 14, 2011 – Interview questions and reviews posted anonymously by interview candidates.
|
Difficulty Rating [?] Based on 4 ratings 
“Difficult” Interview
|
Interview Experience [?] Based on 4 ratings
|
LinkedIn has 3,902 connections on Glassdoor
See Who You Know
| 1–4 of 4 LinkedIn Interviews | Sort by |
Principal Software Engineer at LinkedIn
Posted Dec 14, 2011
|
4.0
Difficult Interview
|
Overall Negative Experience
|
Interviewed and No Offer
|
Interviewed Dec 2011 (took 3 days)
I was contacted by a Linkedin recruiter. After having a 1:1 sessions with development leads was called for an onsite. My technical interviews I thought went reasonably well but I was declined.
Interview Questions
Other Details
I got the interview through a Recruiter and the interview consisted of a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Principal Software Engineer at LinkedIn
Posted Nov 21, 2011
|
3.0
Average Interview
|
Overall Negative Experience
|
Interviewed and No Offer
|
Interviewed Nov 2011 (took a day)
Some of the interview questions were decent (e.g. intersection of two number arrays) but non-coding questions were about a decade old. Especially when interviewing someone for a Principal position, lame questions can be avoided e.g. Question is: Would you prefer Java over any other language? Ans. I don't know all programming languages. I can compare against the ones i know. You can guess the response. Overall, it was pretty bad (i didn't learn anything, except not to interview here again).
Interview Questions
Other Details
The interview consisted of a Phone Interview and a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Principal Software Engineer at LinkedIn
Posted Aug 31, 2011
|
4.0
Difficult Interview
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed May 2011 in Mountain View, CA (took 2 weeks)
The process began with a technical 1:1 phone screen. This part is not very difficult, they test basic algorithms and data structures knowledge. You have to code online and in real time with the interviewer using collabedit.
The onsite interview was exhausting and unnecessary long, I got there around 10 am and left at 5 pm. I was interviewed by 10 people in 5-6 sessions. The interviewers were nice in general and they tested: technical communication, algorithms, data structures, architecture/design and culture. I only failed to complete 1 of the questions but that was enough to get rejected.
Overall it seems like a good place to work at.
Interview Questions
Other Details
I got the interview through a Recruiter and the interview consisted of a Phone Interview, a 1:1 Interview and a Group/Panel Interview.
Helpful Interview?
Yes |
No
Inappropriate?
Principal Software Engineer at LinkedIn
Posted Jul 10, 2010 — 3 of 3 people found this helpful
|
3.0
Average Interview
|
Overall Negative Experience
|
Received and Declined Offer
|
Interviewed Jun 2010 in Mountain View, CA (took 6+ weeks)
Totally unprofessional from the beginning. Their HR is a disaster. Took almost a month just to schedule an interview. Many reschedules in between.
The workplace stinks inside out. I swear. Just visit once and you will know. Engineers are packed like slaves inside. No space to even walk around without the hurdles.
They think they are Google just because they are next door. They try copy Google in every aspect. But they don't realize they are not even close. Engineers and the Managers I spoke with are absolutely clueless on the technology and e-commerce side. They think they are smart. Most these guys seemed like C programmers and still think that way to program in Java!
They don't seem to understand Java Concurrency at all. They don't even know Merge Sort!! Seriously. But they think they are the smartest. Many of them were really rude. But I demonstrated right to their face how immature they were in terms of technical know how.
All in all, this company is a disaster. I think it is just foolish to hire people on LinkedIn. It is not hard to build fake community of referrals on it. The 2B evaluation is just one more bubble waiting to be burst. With the kind of Engineers they have, I doubt their success.
Reason for Declining
Lack of real engineering talent. It's dangerous to work with such folks who think they know everything.
Their HR is a total disaster. Workplace stinks. Salary is below par. Benefits are poor.
Other Details
I Applied Online and the interview consisted of a Phone Interview and a 1:1 Interview.
Helpful Interview?
Yes |
No
Inappropriate?
RSS Feed for LinkedIn
Interviews
Embed
