First, there is an online coding assessment. It's not hard at all. The only difference from other interviews is that it asked a frontend question (coding in JS), but I was applying for a full-stack position, so it's not completely out of the norm.
Then came the onsite interview. There were five interviews total.
The first interview was meeting with the hiring manager. It was the hardest to prepare for because the recruiter said he could ask anything he wants: behavioral, technical, coding, anything. At the end, the hiring manager only asked behavioral questions, but this is where I suspect I didn't get an offer, because I feel I did pretty well for the rest of the day.
Then there were two coding interviews (lunch in between). One was about algorithms, which wasn't hard; anyone knows how to iterate an array and using a hashmap should be able to do it. The second was about using the Twitch API to get some data and process the results. The coding interviews were not hard at all. They ran out of questions to ask before the interviews ended.
The next interview was with a senior UX designer. It was mostly talking about my past experience.
The last interview was system design. It was a question about how to design a particular feature of Twitch. The question itself was a pretty typical system design question. It would help if you know or use Twitch (the product) beforehand.
Tell me about a time you lost another person's trust.
Tell me about a time another person lost trust in you.
The following metrics were computed from 3 interview experiences for the Twitch Senior Software Engineer role in Seattle, Washington.
Twitch's interview process for their Senior Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Twitch's Senior Software Engineer interview process in Seattle, Washington.