Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Twitch (San Francisco, CA) en nov 2015
Entrevista
The interview process was pretty smooth. After a quick call with the recruiter, they set up a phone screen and then moved on to the on-site, which was a good mix of technical questions and chats about both myself and Twitch. I really felt like they spent a good amount of time making sure that I could learn about the company rather than just constantly grilling me.
Preguntas de entrevista [1]
Pregunta 1
If you were a product manager at Twitch, how would improve the product to make subscriptions more beneficial to our users?
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 4 semanas. Acudí a una entrevista en Twitch (New York, NY)
Entrevista
Had a phone screen with a recruiter before the technical phone screen. Technical phone screen was straight forward, basically asked how to parse information out of a stream and return sorted results with the smallest time complexity.
Then got asked for an onsite, which was pretty long. Had 6 different interviewers, including a video chat with a coderpad. From what I hear Twitch does two types of interviews, either build focused or algorithm focus. I had a build focused interview. Two of the interviews were behavioral ("tell me about a time when...") and product focused (mostly role playing, somewhat anecdotal). The other four started from the resume and migrated to coding based questions, three of which I was required to write code solutions.
I heard results two days after the interview.
Preguntas de entrevista [2]
Pregunta 1
Design an API that would get user data and play a video based on a specific stream url.
