J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez LinkedIn (Mountain View, CA)
Entretien
A recruiter initially reached out to me through LinkedIn.
After a few phone call interviews, I moved on to a few remote skills exercises. I didn't interview for a specific position, instead I was told that the position the company thinks you are best suited for is determined through your interview process (whether you're senior or staff level or whatever).
I had two screen-sharing interviews, which were coding exercises where two developers from LinkedIn would give you specific challenges or examples and ask you to solve them / work through them. Each one was about 45 minutes, with 30 minutes of coding and 15 minutes of just questions or introductions or whatnot. The first covered JavaScript, while the second covered HTML and CSS. Even though you're coding in a web interface, the code doesn't compile or actually show UI. I think it's so that you don't get distracted with minutia of making something actually work and instead talk about strategy and overall steps to achieving your goal.
After these first skill assessment interviews, I was flown out to Mountain View to interview at their campus. The on-campus interview was pretty much a full day process. I started off with a brief tour of the office and some discussion about the background of the company with one of the people I had exchanged emails with during the early phases of the process. Then I was taken to a meeting room where the rest of my interviews would take place.
There were six or seven groups of interviews. The first two were general information about the company and about the team. Then there were 4 technical interviews, each one with a pair of developers (one senior, one junior). Each one addressed different aspects of development - CSS, HTML, JS, etc. There was also a lunch interview, which is when you just grab lunch with another developer. Each of these interviews is about the same format as the phone interviews - about 45 minutes each with 30 minutes or so of coding and 15 minutes or so of general questions. Also, the technical challenges are all done on a whiteboard, without a computer.
Questions d'entretien [1]
Question 1
During my phone JS interview, I got a lot of general CS questions. The questions were a bit frustrating, because they're things you know you can just Google search and find the one-line answer you need without any actual effort. Things like writing a function to determine if a string is a palindrome or writing a function for the Fibonacci sequence - things that don't have any real use and just exist as stereotypical interview questions.
J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez LinkedIn en sept. 2015
Entretien
1. Call from the recruiter. Mainly just about my past jobs. (20 min)
2. Technical call by a senior web developer. Technical questions about HTML, CSS and JavaScript. (30 min)
Mainly I was asked about positioning html with css, accesibility and frameworks that I use.
3. Technical call with collabedit by two Sr. Web developers . Technical questions about HTML and CSS. (45 min)
They showed me an image and asked me to type the structure for the HTML, and then apply the CSS rules.
4. Technical call with collabedit by a Sr. Web developer and a Web developer (45 min)
They showed me some code and asked me to describe what was happening there and why.
Knowing how value vs reference type and how context works is needed to answer this correctly.
I was asked to code the isPalindrome() function and another problem that uses your previously coded isPalindrome function that the interviewer had difficulties trying to explain to me. At the end, I got the idea and explained what I would do because the time was almost over.
5. In site interview in Mountan View, CA (I didn't make it to this interview)
The third and fourth interviews where done the same day consecutively. I didn't make it to the 5th interview because my HTML and CSS were not good enough. Basically, I feel the reason why they didn't like it is because I didn't use the elements correctly. Semantic elements are very important to them. Learning experience for me and loss for them. I still think that I would have been perfect for the job.
My JavaScript interview went great.
The recruiter called me to tell me the bad news. He explicitly said I didn't make it because of the third interview. I appreciate the fact that he called me instead of sending me an email.
Overall, it was a great interview process.
Questions d'entretien [3]
Question 1
What are the differences between AngularJS and Backbone.js? Which one do you prefer and why?
J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez LinkedIn (Mountain View, CA) en août 2015
Entretien
There were four steps; the first was an informal phone interview with the recruiter. The second was a phone conversation with two of LinkedIn's developers. The third was an online collaboration effort where the interviewer asked me a few code-related questions and I had to solve it in real-time as they watched me code. The fourth interview they flew me out to their offices in California where I did a full-day interview. This consisted of code questions where I had to solve the problems on a white board. We took a break for lunch and then finished with an interview with one of their managers.
J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez LinkedIn (Mountain View, CA) en avr. 2015
Entretien
Contacted via recruiter.
Had a phone screen with HR, and then a phone screen with a Senior Developer.
Then had an online code interview via CollabEdit (IF you're interviewing, I strongly recommend becoming familiar with CollabEdit before this step. It's... an interesting tool).
Flew out there for an onsite. Everyone was very welcoming. Everyone new be my name and they greeted me with some welcoming swag.
Flew back home and received a call two business days later with an offer.
You need to be very comfortable with your HTML, CSS, and JavaScript during the on-site. If not, I'm sure this would be very difficult. Lots of whiteboarding.
Questions d'entretien [2]
Question 1
While writing the markup for a page on a whiteboard, I was asked why I didn't use <DL> tags instead of what I had written.