There were lots of programming questions. I had a couple of Zoom/CodePair technical interviews, along with a few hours of in-person whiteboard sessions.
One interviewer I felt I was on a completely different page from. I'm not saying they weren't sharp or friendly, just that we had a major disconnect when trying to communicate about the questions they were asking. This one was in-person, which was odd. I did my best to explain my thought process about what I thought was being asked, and asked several questions to try and get on the same page as them, but it just... didn't work.
Apart from that one, all the other interviews went smoothly. The questions weren't easy, and for the most part, they weren't things I had seen before. They were mostly foundational computer science concepts:
Along with some more domain-specific questions, such as:
I walked out of the interview confident, not necessarily that I nailed every answer, but at least that the interviewers considered me as a peer.
When a Linux process attempts to allocate heap memory, what really happens behind the scenes? This includes what happens in user-space, what happens in kernel-space, and what system calls are involved.
The following metrics were computed from 5 interview experiences for the Roku Sr. Software Engineer role in United States.
Roku's interview process for their Sr. Software Engineer roles in the United States is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Roku's Sr. Software Engineer interview process in United States.