Roblox · OA → Onsite
In processRoblox New Grad OA and Interviews: 137 Experiences (Part 1 of 7)
Roblox new grad SWE reports, Sep 2025 to Oct 2026: a game-based assessment with CodeSignal coding, then two 45-minute coding rounds and a behavioral round.
At a glance
- Process: an assessment in the Roblox client (vehicle and factory games, Outpost:Mars, workplace scenarios, a written explanation and CodeSignal coding, often 3–4 hours in total), then two technical interviews and a behavioral round (09, 12, 14, 18).
- Asked recently: coding in 22 of 25 reports, the factory game in 9, vehicle or robot builds in 8, Outpost:Mars in 4. Only one coding task was named: zeros in a 2×2 grid (23).
- Difficulty: most called the coding medium; several got one clearly harder question (06, 12, 20). A perfect 600/600 coding score did not guarantee a next round (05, 07).
- Practise first: the factory-profit game adaptation, the vehicle-build game adaptation and the Outpost:Mars block-program adaptation.
Coverage: New grad and explicitly early-career SWE reports, from the assessment through live rounds. San Mateo, Redmond, Santa Clara, Livingston (NJ), Toronto, Vancouver and California City, plus reports with no location. September 2025 to October 2026, by interview month when given, otherwise report date.
In this series
- Part 1 (current): Sep 2025 – Oct 2026, 25 reports: today's game assessment and live rounds.
- Part 2: Dec 2024 – Sep 2025, 23 reports: one-digit pairs, pagination and a feature-design round.
- Part 3: Sep 2023 – Oct 2024, 25 reports: matching socks, a Trie prefix task and many behavioral questions.
- Part 4: Dec 2021 – Sep 2023, 23 reports: song shuffling, inventory outfits and an animal-survival game.
- Part 5: Nov 2020 – Oct 2021, 18 reports: Unexpected Demand, Ancestral Names, ceiling painting and DP-heavy OAs.
- Part 6: Sep – Nov 2020, 13 reports: browser history, weighted random and matchmaking design.
- Part 7: Oct 2019 – Sep 2020, 10 reports: Largest Subgrid and Ancestral Names.
What came up
The games get the most detail in these 25 reports. Candidates remember the car tracks and factory scores; most kept the coding prompts to themselves.
| Topic | Reports | Last seen |
|---|---|---|
| Coding (CodeSignal or live rounds) | 22 of 25 | Oct 2026 (report date) |
| Behavioral or workplace scenarios | 11 of 25 | Sep 2026 (report date) |
| Factory / production game | 9 of 25 | Sep 2026 (report date) |
| Vehicle or robot terrain game | 8 of 25 | Sep 2026 (report date) |
| Other or unnamed games | 7 of 25 | Sep 2026 (report date) |
| Outpost:Mars | 4 of 25 | Sep 2026 (report date) |
| Written reasoning | 2 of 25 | Nov 2025 (report date) |
| Dynamic programming | 1 of 25 | Nov 2025 (report date) |
| Trie and depth-first search | 1 of 25 | Oct 2025 |
| Grid task | 1 of 25 | Oct 2025 (report date) |
A candidate can appear in more than one row.
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Find the zeros in a 2×2 grid | 1 | Oct 2025 (report date) |
Assessment games
The rows group game families, not identical levels. Each link is a coding exercise adapted from the game.
| Question | Reports | Last seen |
|---|---|---|
| Factory-profit game | 9 | Sep 2026 (report date) |
| Vehicle-building / terrain game | 8 | Sep 2026 (report date) |
| Outpost:Mars | 4 | Sep 2026 (report date) |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| How do you handle multitasking? | 1 | Nov 2025 |
Written reasoning
| Question | Reports | Last seen |
|---|---|---|
| Explain the reasoning behind your factory decisions | 1 | Nov 2025 (report date) |
25 detailed candidate timelines, loops, and screens
01: Two medium questions and helpful interviewers
Report date: Oct 8, 2026 · Role: SWE New Grad · Result: Declined offer
- Two LeetCode-style technical questions, both around medium. The interviewers were helpful and the rounds felt like conversations.
- Neither task was named. The candidate later declined the offer.
02: Optimal solutions, a timestamp catch, then rejection
Report date: Sep 18, 2026 · Role: SWE, early career
- Assessment: five working designs on the first track of the vehicle-build game and three on the second; a factory score of 136k; Outpost:Mars "like 3 and 4".
- Two technical interviews: the candidate felt both solutions were optimal, needed no hints, wrote tests and finished early. They asked about a missing constraint on negative timestamps, and the interviewer called it a good catch. The problems were not named.
- Technical and behavioral were separate stages. A rejection came three days later. They mentioned Kahn's algorithm as prep advice, not as a question they got.
03: Five assessment parts in Redmond
Report date: Sep 18, 2026 · Role: SWE New Grad · Location: Redmond, WA · Result: No offer
- Five activities, including coding and a behavioral section. The candidate found those two easy but rated the whole experience difficult. No question wording was given.
04: Three games, coding and decision making
Report date: Sep 7, 2026 · Role: SWE, early career · Location: San Mateo, CA · Result: No offer
- Five parts: three games, one coding assessment and one decision-making assessment.
- The coding felt like LeetCode medium. The time limits were harder than the questions.
05: 600/600 on coding, but a misread factory task
Report date: Sep 1, 2026 · Role: SWE, early career
- Scores: 600/600 coding, 2/2 on cars, 80k on the factory game and 6/6 on Outpost:Mars.
- They said they misunderstood the factory question, and were rejected. Coding prompts and Mars levels were not shared.
06: An easy question, then a hard one
Interview date: Aug 2026 · Report date: Sep 29, 2026 · Role: Software Engineer New Grad · Location: Livingston, NJ · Result: No offer
- Passed the Roblox games and CodeSignal.
- Two virtual coding interviews: they solved the easy question but could not get the hard one working.
- The rejection came with interviewer feedback. The process took about three weeks.
07: A perfect coding score that went nowhere
Report date: Aug 22, 2026 · Role: SWE, early career
- Scores: 600/600 coding, 3/3 on cars, 120k on the factory game, and Mars written as "2/?".
- They felt Outpost:Mars went badly and were rejected.
08: Rejected two days after the OA
Report date: Aug 21, 2026 · Role: SWE, early career
- The rejection came two days after the assessment.
- They named Outpost:Mars as the hard part; the other sections seemed fine.
09: Games, two 45-minute technicals, then behavioral
Report date: Jun 30, 2026 · Role: SWE New Grad · Result: Declined offer
- Assessment: games including factory optimization and car building.
- Technical: two LeetCode-style interviews, 45 minutes each.
- Behavioral: a final interview. No questions were named; they declined the offer.
10: A retry two months later felt much harder
Report date: Apr 18, 2026 · Role: Software Engineer New Grad · Result: No offer
- First attempt: four OA tests, then an online technical with two easy-to-medium problems, each in two parts. They did not finish the second part of the second question.
- Retry: two months later they interviewed for the same position again. The problems felt medium to hard and they could not finish them.
11: An offer after one familiar problem and one curveball
Report date: Jan 12, 2026 · Role: SWE New Grad
- The commenter said they got a new grad offer in fall 2025.
- One technical problem resembled a Roblox-tagged LeetCode question; the other was unexpected. Neither was named.
12: Car assemblies, a production line, then CodeSignal
Report date: Jan 6, 2026 · Role: Software Engineer, New Grad · Result: No offer
- Tried car assemblies on obstacle courses (vehicle game), then optimized a factory production line.
- A workplace-scenario section asked for the most and least effective response from given options.
- CodeSignal last: two coding questions, one medium and one hard. No statements were shared.
13: A long assessment before back-to-back technicals
Report date: Dec 20, 2025 · Role: SWE, early career · Location: San Mateo, CA · Result: No offer
- A lengthy multi-part assessment, then two consecutive technical interviews.
- The live questions felt like ordinary LeetCode problems. None were named.
14: Three hours of assessments before live rounds
Report date: Dec 13, 2025 · Role: SWE New Grad · Location: San Mateo, CA · Result: No offer
- An OA of about three hours, then two technical interviews and, for those who advance, a behavioral round they believed was last.
- They kept question details private under an NDA.
15: An automated invite and a four-hour assessment
Report date: Dec 1, 2025 · Role: SWE New Grad · Location: California City, CA · Result: No offer
- An automated email led to a four-stage assessment in a downloadable client.
- About four hours of questions and skill games, plus a LeetCode-style coding section. No tasks were described.
16: Robot variants and a multitasking question
Interview date: Nov 2025 · Report date: Jan 24, 2026 · Role: Software Engineer · Location: Santa Clara, CA · Result: No offer
- A campus applicant built several robots to cross terrain (vehicle game), then took a coding assessment.
- They were asked how they handle multitasking. The process took about a week.
17: An imperfect coding score still led to a technical
Report date: Nov 22, 2025 · Role: SWE New Grad
- Recalled a robot game, a factory game with an essay explaining their choices, a situational test and coding.
- The coding felt medium; they guessed a score near 510/600 but were unsure of it and of the platform.
- They reached a technical interview and did not pass. Their memory of proctoring was mixed up with another company's test.
18: Manager behavioral plus an asynchronous interview
Report date: Nov 14, 2025 · Role: SWE New Grad · Location: San Mateo, CA · Result: No offer
- A four-hour OA, then two technical interviews with medium-to-hard questions. Dynamic programming came up; no prompt was given.
- Behavioral: one interview with an engineering manager and one asynchronous interview through the portal.
19: Two CodeSignal questions and three Roblox activities
Report date: Nov 4, 2025 · Role: SWE, early career · Result: No offer
- The assessment arrived automatically. CodeSignal had two medium questions.
- In Roblox: behavioral, factory and car puzzles. No prompts were described.
20: Toronto technicals with a Trie-and-DFS problem
Interview date: Oct 2025 · Report date: Oct 22, 2025 · Role: SWE, early career · Location: Toronto, ON · Result: No offer
- After the OA, two coding rounds: an easier medium and a hard problem, about 35 minutes per question.
- The hard one used a Trie and depth-first search; the actual operation was not shared.
- They did not reach behavioral, which they understood to be a 30-minute virtual interview plus an AI behavioral step. The process took about three weeks.
21: A next-steps call after a month of silence
Report date: Oct 14, 2025 · Role: SWE New Grad
- About a month after final interviews, a recruiter set up a 30-minute next-steps call. No offer had been confirmed when they posted.
22: Withdrawn after another offer
Report date: Oct 4, 2025 · Role: Software Engineer, New Grad · Result: Withdrew
- Roblox games and coding, including a factory game about maximizing output while limiting cost.
- Medium-to-hard live coding followed. The candidate then left the process for an offer elsewhere, so this is not a rejection.
23: A 2×2 zero-finding task
Report date: Oct 4, 2025 · Role: SWE, early career · Result: No offer
- The assessment had a Roblox game, a writing task, behavioral multiple choice and CodeSignal. They enjoyed the game but found it hard to iterate quickly without knowing the setup.
- The one coding prompt they gave: find the zeros in a 2×2 grid. The writing prompt and behavioral options were not shared.
24: Buying machines to make a factory profitable
Interview date: Sep 2025 · Report date: Jan 16, 2026 · Role: Software Developer New Grad · Location: Vancouver, BC · Result: No offer
- A campus applicant had four games in a 40-minute first round.
- In the factory game they bought machines and materials, set up production and chased the largest profit. They did not advance.
25: Four timed sections and a rejection days later
Interview date: Sep 2025 · Report date: Oct 23, 2025 · Role: Software Engineer (new grad) · Location: Vancouver, BC · Result: No offer
- Two coding questions in 50 minutes, 30 behavioral items in 25 minutes, a 25-minute problem-solving section and a 45-minute strategy section about improving a simulated game outcome.
- The rejection came several business days later. No questions were transcribed.
Patterns across the reports
- Two live coding rounds. Seven reports described two technical interviews (01, 02, 06, 09, 13, 18, 20). Some had one clearly harder question: easy then hard (06), an easier medium then a hard Trie task (20). Others called both medium (01) or medium to hard (18).
- Scores do not settle the outcome. Two candidates with 600/600 coding were rejected (05, 07), while one with an estimated 510/600 reached a technical (17). Candidates pointed at the factory game (05) or Outpost:Mars (07, 08) instead.
- A long assessment. Reports that gave a length put the full assessment at three to four hours (14, 15, 18).
Common questions
What is in the Roblox new grad OA?
A Roblox-client assessment with games (vehicle builds, a factory, Outpost:Mars), workplace scenarios, sometimes a written explanation, and CodeSignal coding (02, 05, 12, 17, 19, 23, 25).
How long is the Roblox new grad assessment?
Three to four hours in three reports (14, 15, 18). One candidate's timed sections added up to about two and a half hours (25).
How many technical interviews does Roblox new grad have?
Two coding rounds, often 45 minutes each, then behavioral (06, 09, 18, 20). One candidate had about 35 minutes per question (20).
Does a 600/600 coding score guarantee a Roblox interview?
No. Two candidates with perfect coding scores were rejected after the assessment (05, 07).
Keep practicing
- Find the zeros in a 2×2 grid: the one named coding task here (23).
- Factory-profit game adaptation, vehicle-build game adaptation and Outpost:Mars adaptation: coding versions of the assessment games.
- Roblox problem bank: every Roblox coding question on FastPrep (sign-in needed).
- Roblox behavioral bank: Roblox behavioral questions (sign-in needed).
- Roblox interview page and Roblox hiring insights: rounds, recent questions and hiring trends.
- Experience feed: the latest interview write-ups.
In this series
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.