Getting an Interview
Getting an Interview
Interviews for Top Jobs at LinkedIn
- Software Engineer (133)
- Senior Software Engineer (40)
- Web Developer (24)
- Sales Development Specialist (23)
- Site Reliability Engineer (16)
- Data Scientist (14)
- Software Engineer Intern (13)
- Intern (12)
- Account Executive (11)
- Account Manager (9)
- Software Engineering Intern (9)
- Product Manager (9)
- Relationship Manager (8)
- Associate Web Developer (8)
- Software Engineering (7)
- Engineering (7)
- Manager (6)
- Marketing (6)
- Campaign Manager (5)
- Sales (5)
- Associate Product Manager (5)
- Principal Software Engineer (5)
- Enterprise Relationship Manager (5)
- Software Engineer - New College Grad (5)
- Software Engineer - Applications (4)
- Enterprise Support Specialist (4)
- Project Manager (4)
- Customer Service Representative (4)
- Marketing Manager (4)
- Analyst (4)
Contract Ruby On Rails Software Engineer Interview
I applied through other source. The process took 1 day – interviewed at LinkedIn (Mountain View, CA) in January 2012.
A senior engineering VP reached out to me using - of course - LinkedIn itself. He had taken the time to read my profile, venturing a friendly remark about a well-known company at which we'd both worked a couple of decades before. We engaged in a friendly and informative email exchange, and he arranged to call me early the next day. We spoke for about an hour, getting along very well. He asked if I'd be up for a follow-up technical screen the same day with a senior member of his staff; I answered in the affirmative, knowing I'd need to move around a couple of commitments.
So, his direct report contacts me at the appointed time, and almost immediately I experienced a "oh no it's going to be one of _those_ calls" sinking feeling. With no preamble, the guy - a former CS professor from Bulgaria - launched into a series of questions about my day-to-day influences, e.g. "What do you read to keep up with the Rails community?" I truthfully answered, "various Pragmatic Programmers publications, Stack Overflow, Y. Katz's blog," etc., which seemed to satisfy him. OK, fine. He immediately then challenged me how, programmatically, I would go about determining the set of integers between 1 and 100 evenly divisible ("remainder 0") by 3 but not by 9.
Fine: it's going to be one of those "how does this guy think?" questions, which I knocked out quickly. To my confusion, he immediately blurted out, "Wrong... wrong... that doesn't work," which I found a bit unsettling and bizarre. He'd asked me to do the exercise on paper (not how programmers actually work), which I did. Insisting it would work, I mentioned that I should have opened a console window and fired up the interactive irb interpreter, where Ruby programmers often test short exploratory blocks of code. I had done that, and found that my solution actually worked. The guy got hung up on a "thinking out loud" utterance I made at one point, involving the use of the 'yield' keyword, and chose to force us down a conversational cul-de-sac with no productive purpose in mind.
At a certain point, I knew with complete certainty that I would never work with or under this guy, and told him I'd like to terminate the interview. Oddly, he wanted to continue, but by that point I knew that every minute spent in unnecessary combat with my arrogant interlocutor was an additional point of blood pressure increase not worth experiencing.
The high irony of the incident is this: they're trying to staff a team to build out an applicant tracking system, some subsystem of which would, ideally, generate metrics for the effectiveness of interviewers. Sincerest best wishes to them in that endeavor.