The process took 1+ week. I interviewed at LinkedIn
Interview
One email from a recruiter, who didn't respond to any of my further mails. Left wondering if he was actually going to all me at the agreed time. He did and then Told me he'd back in 2 days. 1.5 weeks later I got a response. Very poor.
I applied through other source. The process took 2+ months. I interviewed at LinkedIn (Omaha, NE)
Interview
Not sure if it was the company itself or the recruiter. My process was not impressive. The recruiter never followed up even though I was a final candidate. I had to reach out to the recruiter every single time for some sort of an update. Seems unprofessional, especially since this is for talent solutions.
LinkedIn also seems to oversell the "greatness" of their culture. And after my interview the overselling became a red flag. My first interview was with a team member. He was cold and inexperienced. I got a strong sense of arrogance from the team member and also the recruiter. I did not formally speak or see a hiring manager until the final round. And between the time I began the process until the end it was way too long. Months.
I like the things I read and studied about the company. The process just proved it was not for me. If you do feel the company is a great fit here are some things I would suggest you prepare for:
1. Product knowledge - do your research, sign up for a demo
2. Company direction (10 yr plan - "economic graph")
3. Sales approach
4. Uniqueness. They want someone who can bring something new to their team. So stand out!
Interview questions [4]
Question 1
Company XYZ recently had a new HR Manager hired on this year and they don't have experience with LinkedIn for recruiting. They are "coming in hot" and do not want to renew this year. How would you handle this?
I applied through a recruiter. The process took 1 day. I interviewed at LinkedIn (Mountain View, CA) in Feb 2016
Interview
Phone screener consisted of jr. level Linux questions. Outline of general interview topics were provided (data structure, API, and file system I/O). Interview was scheduled, but scheduler failed to provide timezone, leading to confusion and delay (could not have been the first time).
Interviewers were focused on ability to code, less than ability to grasp concepts. Interview was strictly test-based, so be a good tester.
Interview questions [1]
Question 1
Parse a log except, providing a csv of the count of each proc per DTTM.