Rokt Software Engineer Compute Infra Build & Release Interview Experience
Interview Experience
I applied to rokt in the month of early october for the role of Software engineer - Build and Release Infrastructure. After giving the OA, I recieved a mail from the recruiter informing about the next
Full Details
I applied to rokt in the month of early october for the role of Software engineer - Build and Release Infrastructure. After giving the OA, I recieved a mail from the recruiter informing about the next steps. I scheduled the next steps for my Technical Screen with the one of the team member. Screen 1 : This round is four part interview (Intro + concepts + coding + Q/A) Everything went fine answered most of it was hinted on moving to next rounds. After a week I had a super casual talk with recruiter, explained about what it is like working with Rokt in nyc all the fun stuff etc. Then told me team is interested to do loop rounds. Scheduled my loop within the next week. (Day 1)Loop 1 - The intereviewer probed me on System design it was a 2 part question on implementing the design and deep dives eventually on Scalability, consistency and latency reduction, optimizing query response times. Super friendly encouraged me to work on my design and evaluated me on my trade-offs and choices. Probed on my choices and deep dives on tech stack. (Day 1)Loop 2 -
Behavioral Manager round. She seemed super friendly and had a casual chat on what my experiences were and what rokt does about its products. Emphasized on what production issues I faced and how were the long term fixes and short term fixes. (Day 2)Loop 3 - Coding + project outline design The interviewer just joined for the sake of interviewing asked me to code a stack based Q. asked complexity, dry run of tc. Moved on the the project design asked me to discuss on my fav project and deep dived into kubernetes internals. Recruiter told me I
passed day 1 loop and smashed the sys design round. and told me will get back to me after day 2 loop After two days recruiter called me and told me team isn't moving forward. and wouldn't continue with the final bar raiser round! No right feedback was given on what went wrong. !!!Rokt if you are seeing this have to balls to tell what the feedbacks are.!!! Absolute BS!!
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.