Roku Inc. Business Analyst interview typically runs 4 rounds: HR screen, hiring manager screen, Excel case study, and a final loop with three interviewers. The process often stretches over several weeks and is notably slow between rounds.
$177K
Avg. Base Comp
$230K
Avg. Total Comp
4
Typical Rounds
6-8 weeks
Process Length
Our candidates report that Roku cares less about polished storytelling and more about whether you can make sense of messy business data in a way that feels tied to the product. The standout signal is how often the questions get highly specific to the business context: one candidate was asked how to run A/B testing for payments, while another had to model regional sales growth under different assumptions. That tells us the team is looking for people who can move from generic analysis into the realities of streaming, monetization, and growth tradeoffs without needing a lot of hand-holding.
A recurring theme is the Excel-heavy case work, especially around gross profit, profitability, QoQ/YoY movement, and data cleaning under time pressure. We’ve seen that candidates who do well are the ones who can quickly structure an answer, spot what the numbers are really saying, and explain the business implication clearly. The non-obvious part here is that the interview seems to reward interpretation over computation; the mechanics matter, but only as a path to a sharper recommendation.
We also keep hearing that the process can feel slow and unresponsive, which changes the candidate experience more than the questions themselves. Multiple candidates mentioned long gaps and limited communication from HR, so persistence matters, but so does staying grounded when the process stretches out. In practice, Roku seems to value analysts who can stay crisp, business-aware, and comfortable with ambiguity — especially when the scenario is intentionally a little under-specified.
Synthetized from 1 candidates reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Roku Inc. process.
The process dragged on long enough that the interview itself almost felt secondary. I started with an HR screen, then a hiring manager screen about half an hour long, followed by an Excel case study, and finally a loop with three people. There was also a version of the process where the hiring manager was followed by a panel of four cross-functional team members and then a final round with the director, with each interview lasting about 30 minutes. In my case, the gaps between rounds were the biggest issue: there were about three weeks between the hiring manager screen and the case study, and then almost another month before the final loop. HR was not responsive at all, even when I mentioned I was in other processes, so I ended up moving on and taking another role rather than waiting around.
The actual interviews were a mix of behavioral and case work. The hiring manager asked background and situational questions, but one of the more memorable parts was how specific and off-script some of the questions felt. I was asked how I would do A/B testing for payments, and in the case study I had to work through Excel-based gross profit and profitability analysis, QoQ and YoY changes, data cleaning, and interpreting the scenario behind the numbers under a short time limit. The final round also included more technical case questions, including how I would model sales growth in a particular region given different assumptions. That part felt especially industry-specific and a bit confusing if you didn’t already know their context. Overall, the process was standard on paper but slow and frustrating in practice, and I ultimately did not get an offer.
Prep tip from this candidate
Be ready for an Excel-heavy case on gross profit, profitability, QoQ/YoY analysis, and data cleaning under time pressure. Also practice explaining how you’d structure an A/B test and how you’d model regional sales growth with assumptions, since those came up in the later rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Roku Inc.
Find the average yearly purchases for each product
| Question | |
|---|---|
| 2nd Highest Salary | |
| Button AB Test | |
| Top Three Salaries | |
| Paired Products | |
| Rolling Bank Transactions | |
| P-value to a Layman | |
| Find the Missing Number | |
| Upsell Transactions | |
| Hurdles In Data Projects | |
| Compute Deviation | |
| Liked Pages | |
| Google Maps Improvement | |
| Session Difference | |
| Size of Joins | |
| Cyclic Detection | |
| Random SQL Sample | |
| Groups of Anagrams | |
| Marketing Channel Metrics | |
| Popular Actions | |
| Identifying User Sessions | |
| Exam Scores | |
| Comparing Search Engines | |
| Categorize Sales | |
| Compute Variance | |
| Three Zebras | |
| Cumulative Sales Since Last Restocking | |
| Completed Shipments | |
| Digital Library Borrowing Metrics | |
| Reducing Error Margin |
Synthesized from candidate reports. Individual experiences may vary.
An initial recruiter conversation to cover your background, interest in the Business Analyst role, and basic fit. In this process, HR was the first touchpoint before any hiring manager or technical evaluation.
A conversation with the hiring manager focused on background, situational judgment, and role-specific thinking. Candidates reported questions like how they would approach A/B testing for payments, along with broader behavioral discussion.
A case exercise centered on Excel analysis under time pressure. The work included gross profit and profitability analysis, QoQ and YoY changes, data cleaning, and interpreting the business scenario behind the numbers.
A multi-interviewer round with either three interviewers or a panel of cross-functional team members followed by a director interview. This stage included more technical case questions, such as modeling sales growth in a region under different assumptions, and was described as highly company-specific.