Candidates describe a Roblox Software Engineer process that opens with a game-style online assessment, then moves to a recruiter call, LeetCode-style technical interviews and a short behavioral round.
$180K
Avg. Base Comp
$362K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
The Roblox Software Engineer interview is unusual mainly because of its first step. Nearly every candidate describes an online assessment hosted on Roblox's own platform. It typically mixes coding problems with game-based problem-solving tasks, such as a factory-profit optimization game and a car-building game where you pick parts to cross different terrain. Several candidates also report a decision-making or behavioral multiple-choice section. A few say they were asked to explain their strategy in writing afterward, so practice articulating your reasoning as well as finishing the task. One candidate warns to check whether multi-part sections share one timer. Another reports the Roblox app freezing during the games.
The coding in the assessment and live rounds is mostly described as LeetCode easy to medium, with occasional harder problems. Reported topics include heaps, sets and hashmaps, matrices and islands, task scheduling with cooldowns, Roman numeral conversion, backtracking or dynamic programming, and minimum window substring. Candidates who got live interviews generally describe two 45-minute technical sessions and a 30-minute behavioral conversation about motivation, teams of interest and a past challenge or conflict. Interviewers reportedly ask follow-ups on optimization and expect you to propose your own test cases. System design shows up less often. One candidate got a leaderboard design question on a phone screen, and another met a system design question in the first technical round.
Most reports in this set end without an offer, and several candidates never got past the assessment. One candidate reports an accepted offer. Practice the assessment format on Roblox beforehand, and rehearse explaining your approach out loud.
Synthesized from 89 candidate 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 Roblox process.
Three interviews back to back in a single day was the part that wore me down most. After the online assessment, a recruiter emailed to schedule the next step, and that turned into two technical rounds and one behavioral, all in one sitting. Both technical rounds used the same format: a LeetCode medium-to-hard problem split into two parts, where the second part changed the problem and asked me to implement something to handle the change.
The topics I remember were sliding window and DFS/BFS, and both rounds pushed me to optimize whatever I had first written. I'd suggest preparing for the moment when the interviewer says something like "okay, now what if..." and you have to figure out which part of your existing code breaks. Get a working first version, state its complexity out loud, and look for the bottleneck yourself. Talk through your trade-offs as you go.
The online assessment was a different kind of test. It had one coding question, a couple of short games meant to test problem solving, and then a written paragraph explaining my thought process on the games. I'd treat the games seriously and keep track of your reasoning as you play, because you have to put that reasoning into words afterward.
The behavioral round caught me off guard. It felt less like a list of standard questions and more like a conversation where the interviewer kept following up on my answers. They asked what I did specifically, why I chose that approach, and how it turned out. If you bring a story, know every detail of it, because you will be asked about it. Anything you embellish is likely to come back up.
I accepted an offer at the end of the process.
Prep tip from this candidate
Expect the two-part format: once you solve the base problem, the interviewer will change a requirement and ask you to adapt it. Practice sliding window and DFS/BFS problems where you extend your solution and then optimize it.
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 Roblox
Convert a list of integers into their Roman numeral representations
| Question | |
|---|---|
| P-value to a Layman | |
| Google Maps Improvement | |
| Nearest Common Ancestor | |
| Hurdles In Data Projects | |
| Centralized Event Ingestion | |
| Spam Classifier | |
| Customer Success vs. Free Trial | |
| Tower of Hanoi | |
| KNN From Scratch | |
| Worker Distribution Dilemma | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| User Event Data Pipeline | |
| Moving Window | |
| Confidence Interval Explanation | |
| Drink Production Allocation | |
| International e-Commerce Warehouse | |
| Youtube Recommendations | |
| Client Solution Pushback | |
| Unified Inbox | |
| Ranking Metrics | |
| Friend Requests Down | |
| Sports App Cheater | |
| Justify a Neural Network | |
| Your Strengths and Weaknesses | |
| Stories Success | |
| Statistically Significant Test | |
| Game Feature Home | |
| 2nd Highest Salary | |
| Groups of Anagrams |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment that combines coding problems with Roblox-hosted games, such as optimizing a factory for profit or building a car to cross terrain. Many also describe a multiple-choice decision-making or behavioral section. Reported length varies, from roughly 90 minutes to several hours. Some candidates were asked to explain their game strategy afterward, and one flagged confusing timers across sections.
Several candidates describe a brief recruiter or HR conversation, in one case about 15 minutes, covering interest in Roblox, background and logistics. One candidate received written questions an hour beforehand. They covered start date, other interviews, office schedule and sponsorship. Another report describes a phone screen that went straight into a leaderboard system design question, so the depth of this step may vary.
Candidates who reached live interviews typically report two back-to-back technical sessions of about 45 minutes, each built around one or two problems. Difficulty is usually described as medium, with some harder problems reported. Topics candidates mention include heaps, hashmaps and sets, matrices, backtracking or dynamic programming, and string windows. Interviewers may ask optimization follow-ups and expect you to write your own test cases.
Candidates describe a roughly 30-minute behavioral conversation, often on the same day as the technical rounds. Reported questions include why Roblox, which teams interest you, a challenge you faced, resolving a conflict with a teammate, and questions about your resume and projects. One candidate was also asked about their experience with games. Timing after the final round varies, and one candidate reports waiting weeks for an update.
