Solicité el puesto a través de la recomendación de un empleado. El proceso duró 3 semanas. Acudí a una entrevista en Fitbit (Boston, MA) en ago 2019
Entrevista
Small sized office (almost 200 people) in Seaport, seems very cozy. Product they are working on is brand new so that interested me greatly. Management seems to understand priorities and work is focused on doing things right instead of just delivering features.
The interview process was brutally long (6.5 hours in total including lunch). Other than that, the interviewers were all very professional and this truly looks like a fun work place to be in. Very collaborative. Benefits look great and can definitely see myself staying here for a while if I joined. Unfortunately with all things, timing was key and I had a much better offer right before I received the final package, so had to decline this opportunity.
Preguntas de entrevista [5]
Pregunta 1
Create a binary search tree given an array of values. Follow up discussion question (more theoretical) on how this can be balanced properly.
Solicité el puesto a través de un captador. El proceso duró 8 semanas. Acudí a una entrevista en Fitbit (San Francisco, CA) en ene 2020
Entrevista
Applied online, had a telephonic interview for 45 mins and then on-site interview. Telephonic interview had a coding question. On-site interview was divided into 4 slots of 1hr each. 2 slots for coding question, 1 system design and 1 behavioral questions sessions
Preguntas de entrevista [1]
Pregunta 1
Behaviorial questions were related to conflict resolution, challenges faced and accomplishments.
Envié una solicitud electrónica. El proceso duró 4 semanas. Acudí a una entrevista en Fitbit (San Francisco, CA) en nov 2018
Entrevista
The interview process contained a chat with the recruiter, followed by a phone screen, and then an on-site. The phone screen consisted of a discussion of an algorithm implementation followed by a discussion of past work experience, where there was some room for error on the former. The on-site consisted of four interviews, including two coding interviews, one architecture interview, and one manager interview. Overall, I felt that the interviews were fairly good evaluators, rather than focusing on getting tricks or having less useful algorithm knowledge.
Preguntas de entrevista [1]
Pregunta 1
If you're creating an API that serves up images based on an ID and an image size, how would you architect the service?
