Solicité el puesto a través de la recomendación de un empleado. El proceso duró más de 1 semana. Acudí a una entrevista en Snap (Venice, CA) en ene 2017
Entrevista
Applied by referral and was contacted almost immediately by a recruiter. Set up a google hangouts phone screen and then set up an on-site at their Venice HQ.
Phone screen was 1hr, and on-site is the usual all-day multiple interview process. The recruiters were friendly and extremely prompt. The girls who interviewed me were absolutely fantastic engineers that made the interviews interactive, open to different/new ideas, and were generally welcoming. The men who interviewed me were agressive, rude (on phone texting, checking emails right next to me, and NOT willing to change or explore new ideas), and most importantly not willing to work together.
Throughout my interview I had recruiters, and engineers consistently talk down upon the android client (huge red flag). Overall, it reeked of an engineering culture that is youthful and trying to find its way. I would be careful to work here simply because a toxic culture can not be fixed from the ground up, and most importantly it impeads on the time for learning.
Overall, I was able to implement each answer correctly with unit tests in the allotted time but was denied. I ended up taking another offer at a larger company in the bay-area, and would not have accepted the offer if it was given due to (what I perceived to be) a very hostile workplace.
Easy interview though, just use the MVC architecture in your answers (engineers didn't know MVP/RxJava patterns).
Preguntas de entrevista [1]
Pregunta 1
1. Implement a stack.
- after asking about constraints I was given: Implement a stack of fixed length.
- Must execute, and write unit tests.
1B. Now, use the stack you created to create a stack of variable length.
- Extend the stack, and implement a next pointer. Essentially a linked list extension.
2. Write an App that accepts deeplinks and displays the last path on the screen. (A word bank app).
3. Design Battleships and write functional unit tests.
4. Write an App that mimics a network based search functionality. You can append "-whatever" to the word, and mock the network layer.
- Wrote this as MVP, with an interface between my presenter and data layer.
- Imolementsd the interface to just do thread.sleep, then hit callback.
- Write unit tests.
- Used RxJavas denounce for the TextView (interviewer didn't know RxJava so I had to implement a debounce function extending a handler instead so he could understand).
Envié una solicitud electrónica. Acudí a una entrevista en Snap (Seattle, WA) en ago 2024
Entrevista
First a Recruiter Call -> Talking about experience working on Android and what are the values of the Company & How my values align to
Technical Phone Interview -> It was a phone interview with a Engineer part of the team that is hiring
Preguntas de entrevista [1]
Pregunta 1
Given a string that represents a color in the combination RGB and a string target that represents a color in the combination RGB generate all color combination between this range.
El proceso duró más de 1 semana. Acudí a una entrevista en Snap
Entrevista
Phone screen was fine and standard interview with codepad problem. But on site was awkward as you had to solve non-standard coding problems in less than 30 min and make all unit tests pass. The interviewers were not helpful.
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 4 semanas. Acudí a una entrevista en Snap (Venice, CA) en nov 2017
Entrevista
I was referred by a friend who was in the interview process. Had a quick chat with the hiring manager and then scheduled the phone screen. The phone screen was an hour long and focused on fundamental data structure and algorithm understanding. Two hours after the phone screen, I was invited to come on site. The on site interview was pretty standard - 4, one-hour long interviews that covered overall system design, Android specific topics, and general data structures/algorithms. I hadn't been feeling well that day and by the end of the day was dragging pretty bad; my final interview was pretty rough but that was nobody's fault.
The only complaint I have is that finding the lobby could certainly be easier. It's tucked back in a group of unmarked bungalows; maybe if they could have someone standing out on the street or on the boardwalk to meet you it'd make that a bit easier.
Preguntas de entrevista [1]
Pregunta 1
General understanding of data structures - be familiar with linked lists, trees, sorting, etc.
