Rokt Senior Full-Stack Machine Learning Engineer Onsite Interview Experience
Interview Experience
This post was last edited by Anonymous on 2025-10-08 at 09:27. The job requirements are a full-stack senior MLE (Model-View-Language) role, roughly 60% ML and 40% infrastructure. The interviewer said
Full Details
This post was last edited by Anonymous on 2025-10-08 at 09:27. The job requirements are a full-stack senior MLE (Model-View-Language) role, roughly 60% ML and 40% infrastructure. The interviewer said it was ML fundamentals, but directly asked me to design video recommendation systems for platforms like Instagram and TikTok, emphasizing model and data labeling. I was very familiar with these tasks. The American female interviewer said, "genuinely happy to meet you," and the recruiter said they had never seen such good feedback. A bit flattered. VO: 1. Business Qualifications (BQ) Director Interview, generally speaking, the feedback was good. 2.
Coding question: Determining if abbreviations match the original words. Slightly harder than coding challenges, but not too difficult overall. I overcomplicated one part and got stuck. The follow-up wasn't fully tested in time, but I basically finished. 3. The most comprehensive system design ever, e-commerce recommendation. The first 25 minutes focused on machine learning (ML), the last 25 minutes on ML infrastructure (how to design the entire pipeline, how to store features, and how to optimize). Basically, a comprehensive understanding of ML is required. The interesting part is that the feedback was "very strong candidate," and the skills were very aligned, but I still didn't pass. Quite ridiculous. I guess it's because the coding wasn't perfect, or because I haven't done much ML in the past two or three years due to focusing on ML infrastructure...
About This Question
This is a candidate experience report from a rokt interview for a mle role (senior level) during the onsite round reported in 2025.
It covers the following topics: System Design, System Design, Stack, Stack .
Difficulty rating: Hard
Topics
About Rokt Interview Reports
This question was reported by a candidate who interviewed at Rokt. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Rokt are the higher-signal extractions to take from this report.
For broader preparation context, the Rokt interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Rokt reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Rokt Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Rokt reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.