Rokt Software Engineer interview questions

4 Software Engineers have shared notes from their Rokt interviews, with the questions they were asked in each round. That is 80% of the 5 Rokt interview notes on Screna AI.

4 Software Engineer interview notes

Rokt·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Rokt for a software engineer role. Just one question but they really wanted you to dig into the specifics, not give a surface-level answer.
  • Tell me about a significant setback you faced in a project or role. What happened, what did you do about it, and what changed in how you work afterward?

“I had a decent story ready but fumbled the 'what changed' part.”

View Post

Rokt·Software Engineer·Technical Phone Screen

Jun 2026
Rokt software engineer interview that centered entirely on how I actually use AI day to day, not a coding round or system design session. Felt more like a conversation than a grilling, but it still caught me a bit flat-footed because I hadn't prepared to talk about my own workflow in that much detail.
  • How do you use AI in your day-to-day work? Walk through the specific tools you rely on, concrete tasks where AI changed how you work, and what you've learned about where it helps versus where it falls short.

“I rambled a bit here.”

View Post

Rokt·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineering role at Rokt and got a classic expression evaluator problem. Not the hardest thing in the world but there are enough edge cases to trip you up if you're not careful about operator precedence.
  • Implement a function that evaluates a basic arithmetic expression string containing non-negative integers and the operators +, -, *, /. Spaces should be ignored, division truncates toward zero, and there are no parentheses.

“The precedence handling is where people mess up.”

View Post

Rokt·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Rokt for a software engineer role. The whole thing was one big question about designing a CI/CD platform at Google-scale, so if you've never thought deeply about build infrastructure before, buckle up.
  • Design a CI/CD platform that can support a large engineering organization at the scale of tens of thousands of developers, hundreds of thousands of commits per day, and up to a million pipeline jobs per day.

“This is a beast of a question.”

View Post