J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez LinkedIn (San Francisco, CA) en sept. 2012
Entretien
The interview process consisted of an initial call with recruiter and a phone call meeting with 4 web developers. The call was a half hour which involved discussing of my skills and how I would handle certain situations, just to get an idea of where my skills were at. After that, they had me speak to 2 more developers using http://collabedit.com for live coding sessions which enabled them to see me code what they asked me to. I first had to develop a small widget, just the basic html css and javascript for how I would do it, simple enough. The third guy had me create a function for adding a class in JavaScript, given an element or ID string, and the class string to add. He was looking to see if I understood the DOM and use of NodeType for checking for if an element or string was being passed and how to add the class to the className. The fourth guy was a senior web developer and he asked me questions that had to do with prototypal inheritance and the prototype chain. He also asked me to create a function that would flatten an associative array into a single array which was quite an involved question to ask. He had asked me to create the addClass function which I said I had done for the previous guy and could send him the code for what I had done.
I was told later when following up that they had decided to pass, and I got a message from the senior developer with feedback for the addClass function I sent him, which he had several concerns for what I coded for it. I was aware of all the issues he had stated and wasn't expecting such a harsh response. When I wrote the code I wasn't under the impression that I must create a fully working function on the spot, but it apparently was what the senior dev was expecting which is what his decision to not hire me was based on. Unfortunately he did not allow me to produce a revised version which I had done that addressed all his concerns and some he had not mentioned in full. He never responded to me about any issues with that version.
Questions d'entretien [1]
Question 1
It wasn't that the questions were hard so much as how involved the addClass and array flattening questions were given it was for an interview and the expectations were very high for creating a working function of each. JavaScript has a lot of quirky things that make answering these questions harder since there is more that needs to be considered when developing solutions for them.
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.