Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en LinkedIn (Mountain View, CA) en abr 2015
Entrevista
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.
Preguntas de entrevista [2]
Pregunta 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.
Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en LinkedIn en sep 2015
Entrevista
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.
Preguntas de entrevista [3]
Pregunta 1
What are the differences between AngularJS and Backbone.js? Which one do you prefer and why?
Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en LinkedIn (Mountain View, CA) en ago 2015
Entrevista
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.
