J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Roku (Los Gatos, CA) en oct. 2018
Entretien
I recently interviewed with Roku for a Senior Engineering position with their Mobile Backend team. Here's my review of their interview process.
To get the interview, I mailed a Roku Recruiter from my LinkedIn contacts list and he responded promptly with an initial discussion of the company, my experience and match for the open roles.
This was soon followed by a technical phone screen with the hiring manager. The phone screen was an algorithm question followed by some design questions, discussion of my experience and more specifics about the team and the role.
I got the results of the phone screen very soon and I was invited for an onsite at the beautiful Roku campus in Los Gatos.
The onsite had 5 technical rounds and 1 non technical round with HR. The technical rounds were a mix of programming, debugging and system design questions. All the questions were very reasonable, clearly explained and nothing out of the order of what you will be expected to do as a Software Engineer. The focus was on sound coding, design principles and appropriate use of data structures rather than some tricky gotchas. The interviewers themselves were very courteous, knowledgeable and very patient about answering any questions I had of the team and the role.
I heard about the results of the interview on the same evening as well - as the recruiter was very mindful about other deadlines I had. The recruiter also clearly outlined their offer details and gave me a lot of insight into the company culture, team expectations and so on.
Overall from the initial contact to the final results, the process with Roku was outstanding. In terms of prompt communication, professionalism in treating their candidates and fairness in terms of compensation, Roku is a model that other companies in the valley should strive to emulate.
J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Roku en avr. 2026
Entretien
Talk with Recruiter, tech talk and Hackerrank with Engineer. Engineer interviewer offered little feedback during an implementation discussion. I justified my selection as being best for a time-constrained interview and he agreed. The interviewer was playing around in my code editor while I was typing, causing distractions and additional errors in my work. Finally, the interviewer was extremely dissatisfied that I did not use the other option that I had discussed, and that I did not select Python when I was told to solve in any language.
J'ai postulé en ligne. J'ai passé un entretien chez Roku
Entretien
Recruiter called me and asked some general questions related to work experience, tech stacks etc. Later they asked about renumeration drawn from the current org: to which I responded saying 'need to check with HR regarding any NDA if they have pertaining to salary disclosure'. I also felt current renumeration being irrelavent question for next role and asked what's the comp. band that this role is entitled to. To which recruiter told without current comp. info, they won't be able to proceed further and rejected on spot.
Questions d'entretien [1]
Question 1
Familarity with tech stack, work experience and salary.
I had recruiters from Roku reach out the whole year. I finally agreed to do a call. I had an initial call with a recruiter where we just talked about my past experience and what I’m looking for. Then I was scheduled for the next round with the hiring manager and was given zero context on what to expect despite asking. You should know that there be will coding with OOP on your first call with the HM despite no one saying anything about it. The whole thing was silly and pointless.
Questions d'entretien [1]
Question 1
The hiring manager asked me to do an OOP solution for a warehouse inventory system, where you need to track the type and amount of a product and find the nearest warehouse with products the customer is looking for. Despite this being an OOP and you being able to implement it in TypeScript or any language, and despite the HM not mentioning, your solution needs to handle concurrency and have locking. Then you’ll be asked what you’d do differently in a production environment. You’ll need to state the obvious like writing tests, using a DB, distributed locking etc. The way they asked the question was very silly and assessed nothing.