Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Localytics (Boston, MA) en may 2015
Entrevista
A couple of emails back and forth. 2-3 screen calls. Then a pair programming code test in JS. Pair programming was probably the hardest part of it all. Definitely brush up on your JS in advance, no time to look stuff up while pair programming. Definitely read about functional JS that can scale. Great interview process overall!!!
Preguntas de entrevista [1]
Pregunta 1
Functional Programming and stuff related to javascript. Control flow.
Me postulé a través de un reclutador. Acudí a una entrevista en Localytics (Boston, MA) en sep 2017
Entrevista
Telephone with recruiter - > 1 hour coding challenge -> 1 day interview
The recruiter asked me what time I want to give the coding challenge and he sent me the email with question and 2 tsv files at that time. I had to email the answers and my code in 1 hour. So you code the solution and get the answers.
In the 1st call, the recruiter will ask you if you know scala and if you dont know scala, they will still send you the coding quiz but you dont stand a chance. I used a parser to parse the tsv files and also got the answers using hashmap in java, but the recruiter told me they didnt like my solution. Well, I wished them all the best in their search and got a better company and better job.
Preguntas de entrevista [1]
Pregunta 1
2 tsv files. Read them and answer questions based on data in them.
Me postulé en línea. El proceso tomó 5 días. Acudí a una entrevista en Localytics (Boston, MA) en jul 2015
Entrevista
Screening call. I thought it went well, but never received a follow up. Person I talked to was friendly, seemed knowledgeable. Admitted the company was only starting out on their commitment to Agile, but at least they have a coach now (I've seen that really help). I was surprised not to at least get a polite rejection notice, but figure it got lost in the shuffle as they're not a huge company.