Roblox software engineer candidates report a game-style online assessment, then live coding interviews and a behavioral round. Here is what to practice for each stage and what the reported questions looked like.
$191K
Avg. Base Comp
$226K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
The Roblox software engineer interview is best known for its game-style online assessment. Many candidates describe an OA with Roblox-hosted games alongside coding, and several mention a factory optimization game and a car-building terrain game. Candidates also report a situational multiple-choice or behavioral section, and some describe explaining the logic behind their strategy. Reports differ on the coding portion. One candidate called it trivial, others say it ran to LeetCode medium or harder, and one reports an assessment that took a few hours overall.
Candidates who moved past the OA describe live technical rounds. One reports two coding interviews of about 45 minutes each and a roughly 30-minute behavioral interview, while another describes about three hours of back-to-back technical and behavioral interviews. Reported live problems include a backtracking or dynamic programming question and converting a Roman numeral to an integer. OA coding reportedly included a BFS graph problem, a set problem, and a confusingly worded matrix-style question with a CSV-reading step. One candidate also faced early system design: a leaderboard service on the phone screen.
Behavioral prompts include resolving a conflict with a teammate and why Roblox. Most reports end in no offer, and some candidates did not get past the OA, so treat it as a real gate. Get comfortable with unfamiliar game mechanics under time pressure, solve mediums quickly, and rehearse explaining your reasoning aloud.
Synthesized from 95 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.
I went through a recruiter screen first, and the recruiter was very responsive and kept me updated the whole way, which made the process easy to follow. The technical portion covered three areas: coding, data architecture, and system design. I'd recommend preparing for all three rather than treating the coding round as the whole test. Alongside the technical work, I also had behavioral interviews focused on collaboration, ownership, and problem-solving, so come ready with concrete examples of how you've worked with others and taken responsibility for outcomes.
The last stage was conversations with the hiring manager and director. After those, the process moved into team matching, which is worth knowing about going in since it comes after the formal interviews. I found the interviewers friendly and professional throughout, and the overall experience felt transparent and well organized. I accepted an offer at the end.
Prep tip from this candidate
Prepare across coding, data architecture, and system design rather than focusing only on coding, and come with specific examples for collaboration, ownership, and problem-solving. Also expect a team matching step after the hiring manager and director conversations.
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 | |
|---|---|
| Google Maps Improvement | |
| Youtube Recommendations | |
| P-value to a Layman | |
| Friend Requests Down | |
| Confidence Interval Explanation | |
| Nearest Common Ancestor | |
| International e-Commerce Warehouse | |
| Unified Inbox | |
| Ranking Metrics | |
| Justify a Neural Network | |
| Centralized Event Ingestion | |
| Hurdles In Data Projects | |
| Spam Classifier | |
| Customer Success vs. Free Trial | |
| Tower of Hanoi | |
| KNN From Scratch | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Worker Distribution Dilemma | |
| User Event Data Pipeline | |
| Client Solution Pushback | |
| Moving Window | |
| Drink Production Allocation | |
| Your Strengths and Weaknesses | |
| Sports App Cheater | |
| Stories Success | |
| Statistically Significant Test | |
| Game Feature Home | |
| 2nd Highest Salary | |
| Subscription Retention |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report applying through the careers site, and some received the OA right after applying. One candidate describes a recruiter call of about 15 minutes after the OA. Prepare a concise answer about why you want to work at Roblox.
Candidates commonly describe a multi-part OA with Roblox-hosted games, such as factory optimization and building a car to cross terrain. It also includes a coding section, often two LeetCode-style problems, and a situational or behavioral questionnaire. Some candidates were asked to explain their reasoning. Length reports range from about 90 minutes to a few hours.
One candidate describes two technical interviews of about 45 minutes each at roughly medium difficulty, including a backtracking or dynamic programming problem. Another describes back-to-back rounds leaning on DSA and scalability, including converting a Roman numeral to an integer, after a phone screen that asked for a leaderboard service design. Explain your approach before coding.
One candidate reports a behavioral round of about 30 minutes with someone on the team, covering a general introduction and a time they resolved a conflict with a teammate. Another was asked why they wanted to work at Roblox. Prepare specific collaboration stories and a clear reason for joining.
