Roblox Onsite Interview Experience for Software Engineer
Interview Experience
See here for the previous interview: https://www.1point3acres.com/bbs/thread-1146238-1-1.html This round consisted of one coding question and one Subject Design question. The coding question was about
Full Details
See here for the previous interview: https://www.1point3acres.com/bbs/thread-1146238-1-1.html This round consisted of one coding question and one Subject Design question. The coding question was about a course scheduler. An additional requirement was to always choose the course with the smallest ID from the available courses. The solution used topological sorting and a priority queue. The Subject Design question was about designing a Matchmaking Service for Multiplayer Games. I recommend searching for this question and interview points on hellointerview. Before the interview, I prepared three frequently asked questions: Design a Delayed Payment Scheduler Service, Design a Like/Unlike Feature, and Design a To-Do List App With Multi-User Collaboration. I ran out of time and didn't prepare for this one. Unexpectedly, it was asked. I completely improvised. I thought I would fail, but I
passed. Next, I'll be interviewing with the Hiring Manager and the Director. If anyone has experience with this, please share.
About This Question
This is a candidate experience report from a roblox interview for a swe role during the onsite round reported in 2025.
It covers the following topics: Heap, Graph, Sorting, Queue, Queue .
More Roblox Interview Questions
About Roblox Interview Reports
This question was reported by a candidate who interviewed at Roblox. 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 Roblox are the higher-signal extractions to take from this report.
For broader preparation context, the Roblox 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 Roblox reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Roblox 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 Roblox 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.