El proceso duró 1 día. Acudí a una entrevista en LinkedIn en nov 2011
Entrevista
Some of the interview questions were decent (e.g. intersection of two number arrays) but non-coding questions were about a decade old. Especially when interviewing someone for a Principal position, lame questions can be avoided e.g. Question is: Would you prefer Java over any other language? Ans. I don't know all programming languages. I can compare against the ones i know. You can guess the response. Overall, it was pretty bad (i didn't learn anything, except not to interview here again).
Cakewalk of an interview. Nobody knew anything about the role or its expectations. Same questions from a question bank. Questions are available on Google search in a couple of minutes. No wrong answers.
Envié una solicitud electrónica. Acudí a una entrevista en LinkedIn (Mountain View, CA)
Entrevista
The initial communication was good and the recruiter did a good job of arranging a coding test on collabedit.
The interviewer was very unprofessional. Came late and hurried up the interview and the other person didn't turn up at all. Also the interviewer didn't know what she was working on !!!
Solicité el puesto a través de un captador. El proceso duró 3 días. Acudí a una entrevista en LinkedIn en dic 2011
Entrevista
I was contacted by a Linkedin recruiter. After having a 1:1 sessions with development leads was called for an onsite. My technical interviews I thought went reasonably well but I was declined.
Preguntas de entrevista [1]
Pregunta 1
Given a large document and a short pattern consisting of a few words (eg. W1 W2 W3), find the shortest string that has all the words in any order (for eg. W2 foo bar dog W1 cat W3 -- is a valid pattern)
