Me postulé en línea. El proceso tomó más de 1 semana. Acudí a una entrevista en Roku
Entrevista
I applied online and received a call from their recruiter within a few days. She scheduled a phone screen, which happened a day or 2 afterwards. The phone screen started with him asking me to do a narration of my recent experience while he got his stuff together. He then asked me some questions about C++ keywords and how to determine integer bit size on any given machine. I was then asked in for an onsite interview. They are in a temporary space right now, so it's just a bunch of folks all sitting at tables in the same room. They appear to have one conference room in which the interview took place. At first the interview was going ok - he wrote a code snippet from a bug he had to fix earlier in the week and asked me to find the bug - a race condition - pretty easy. After that he asked me to do some coding on the white-board. The coding question was really easy - write a sort algorithm for a singly linked list; however at this point I seemed to go full retard and completely fell apart. Some stuff went on afterwards, but I could read it in the interviewers eyes that the interview was over. There was one other interviewer who was a QA guy. He asked some questions about coding with testing in mind and asked how to detect if a linked list had a loop in it.
So, sort of a bad experience, but it was completely my fault. If you interview with these folks I would suggest a review of your old data structures book before you show up.
Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Roku en abr 2026
Entrevista
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.
Me postulé en línea. Acudí a una entrevista en Roku
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 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.
Preguntas de entrevista [1]
Pregunta 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.
