I applied through an employee referral. I interviewed at Twitch (San Francisco, CA)
Interview
There was a recruiter call first, then two technical phone screens with two different engineers. I didn't make it to onsite. I thought the interviews went fine, but I got a standard rejection email from the recruiter.
Interview questions [1]
Question 1
- Data structures, algorithms
- Tell me about your experience
Thanks for the feedback. As a policy, we don't share granular feedback on interviews, which is why the rejection email read fairly generic. We've discussed quite extensively the merits between calling for rejections, or giving a candidate a response immediately with an email to be respectful of time. Either way, wish you luck in your job hunt and hope you decide to apply again down the road. - Arthur Yamamoto / Director of Recruiting
I applied through a recruiter. The process took 4 weeks. I interviewed at Twitch (Boston, MA) in Nov 2019
Interview
I was contacted though Linkedin, they invited me to apply so I did. I had a first screen phone call, then I was sent an online test about some algorithms. After that they invited me to 4 1:1 1 hour on-site interviews.
The recruiter and the rest of the team was super informative and really helpful during all the process.
This all happened really fast, 1 month passed since the first interview to the last one, I received a formal offer after 3 days.
Studying from Cracking the coding interview book was really helpful for me, I'd totally recommend doing that.
Interview questions [1]
Question 1
1 behavioral interview, 2 about algorithms and one about app architecture, requests and some border cases on a small app.
I applied online. The process took 5 weeks. I interviewed at Twitch (San Francisco, CA) in Jun 2019
Interview
Excellent experience interviewing with Twitch. Recruiters made sure I had everything I needed to succeed at every step. The process had a slow start, but once I alerted them to another pending offer they jumped through hoops to slot me in. Employees were welcoming and professional on-site and no questions felt unrelated or too difficult. Standard bay area technical interview process. Call with recruiter, 1 take home technical test, 1 phone screen with an engineer, followed by an onsite interview loop.
Interview questions [2]
Question 1
Classic algorithm questions such as those online, though most if not all involved recursion. E.g. generate permutations, check for sums, etc.
I applied online. I interviewed at Twitch in Jul 2017
Interview
Very straight forward. Much like you would expect. I spoke with a recruiter about my experience and then had a phone screen with an engineer. The engineer asked about my background and some of my experience and then had me work on a technical question over an online code pad.
Interview questions [1]
Question 1
I was asked to make an asynchronous API synchronous. It was a very fair and relevant question.