Roblox · OA → Onsite
In processRoblox New Grad CodeSignal Finals: 23 Experiences (Part 4 of 7)
Roblox new grad SWE reports from Dec 2021 to Sep 2023: CodeSignal plus game simulations, then two 45-minute technicals and two 30-minute behavioral rounds.
At a glance
- Process: CodeSignal (often four questions, easy to hard) plus two Roblox games or simulations, then a final round of two 45-minute technicals and two 30-minute behavioral interviews (74, 81, 84, 85, 88).
- Asked in this period: vehicle builds (5 reports), the factory game (4) and a virus-spread animal-survival game (2). Named coding tasks: shuffle a playlist (81) and combine inventory outfits (80).
- Difficulty: CodeSignal sets ran from easy to hard (83, 89, 91, 95); live coding was called easy to medium (88, 90, 94) with one hard DP question (78).
- Practise first: Shuffle a Playlist and Inventory Outfit Combinations.
Coverage: New grad and early-career SWE, assessment through offers. San Mateo, San Francisco and Chicago, plus unstated locations. December 2021 to September 2023, by interview month when given, otherwise report date. All 23 reports are more than three years old, so the whole part sits under History.
In this series
- Part 1: 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 (current): 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
These older reports show the loop taking its current shape: game simulations next to CodeSignal, then a four-interview final. Counts cover the 23 reports in this part.
| Topic | Reports | Last seen |
|---|---|---|
| Coding (OA or live rounds) | 21 of 23 | Sep 2023 (report date) |
| Behavioral or workplace items | 14 of 23 | Sep 2023 (report date) |
| Vehicle or robot builds | 5 of 23 | Sep 2023 (report date) |
| Factory / production game | 4 of 23 | Sep 2023 (report date) |
| Dynamic programming | 2 of 23 | Sep 2023 (report date) |
| Virus spread / animal survival | 2 of 23 | Oct 2022 |
| Matrix and sliding window | 2 of 23 | Sep 2023 (report date) |
A candidate can appear in more than one row.
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Combine outfits from an inventory | 1 | Jun 2023 |
| Shuffle a list of songs | 1 | Mar 2023 |
Assessment games
The rows group game families, not identical levels. Each link is a coding exercise adapted from the game.
| Question | Reports | Last seen |
|---|---|---|
| Vehicle-building / terrain game | 5 | Sep 2023 (report date) |
| Factory-profit game | 4 | Sep 2023 (report date) |
| Virus spread and animal survival | 2 | Oct 2022 |
Behavioral (BQ)
| Question | Reports | Last seen |
|---|---|---|
| Tell me about a challenge you faced | 1 | Jan 2023 |
| Why do you want to work at Roblox? | 1 | Oct 2022 |
| What did you learn from your previous internship? | 1 | Oct 2022 |
Open-ended product reasoning
| Question | Reports | Last seen |
|---|---|---|
| How would you make an elevator experience happier? | 1 | Dec 2021 |
History (before November 2023): 23 detailed candidate timelines
74: Two technicals, then two half-hour behaviorals
Report date: Sep 30, 2023 · Role: SWE New Grad · Result: Rejected
- A cars-and-coding OA, a recruiter chat, two 45-minute technicals and two 30-minute behavioral interviews. The last round was behavioral, not another technical.
- They thought behavioral was their weakest stage and got little explanation. Their recruiter changed midway. Others replying put about a week between stages.
75: Still waiting after a strong OA
Report date: Sep 25, 2023 · Role: SWE New Grad · Result: Waiting
- OA on August 15: 600/600 coding, a factory score above 100k (factory game) and three car designs per track (vehicle game).
- Still waiting after several recruiter emails when they posted; no rejection yet.
76: A perfect CodeSignal score without advancing
Report date: Sep 22, 2023 · Role: New Grad Software Engineer · Result: No offer
- Two games, CodeSignal and behavioral. They scored perfectly on coding but did not pass the first stage.
- They mentioned hashing and implementation questions without describing them.
77: Sliding window in a matrix
Report date: Sep 21, 2023 · Role: Software Engineer (New Grad) · Result: No offer
- Coding, two games and a decision-making survey. The games had many rules, but the tutorials helped.
- The only coding detail: a sliding window over a matrix, with no stated goal.
78: An August OA, then a hard DP question at the onsite
Report date: Sep 1, 2023 · Role: SWE New Grad
- OA: cold-applied, took it August 17, invited to interview August 29. Scores: 600/600 coding, 107k factory, and five car solutions on the first track and two on the second (vehicle game). They recalled oil on one vehicle and spiked wheels on another.
- Virtual onsite: a different interviewer per question and a hard 45-minute cutoff, including five to ten minutes of introductions. Working code and their own tests were expected. They struggled with a hard dynamic-programming first question and solved the second. Others said behavioral followed about a week later.
79: Twenty-five workplace items alongside games and code
Interview date: Aug 2023 · Report date: Aug 30, 2023 · Role: New Grad Software Engineer · Location: San Mateo, CA · Result: No offer
- Two games, two coding challenges and 25 work-situation items.
- One game had them assemble parts to clear obstacles; the other had them add parts to earn the most money. They felt the games measured how they explored, not just the final build. The process took about two weeks.
80: Combining outfits from an inventory
Interview date: Jun 2023 · Report date: Mar 4, 2024 · Role: SWE New Grad · Location: San Mateo, CA · Result: No offer
- Four online rounds: two assessments (one a Roblox game), then two one-on-one technicals with engineers.
- The coding was standard but set in Roblox scenarios. One task asked them to combine outfits from a user's inventory; categories and conflict rules come from the practice version. The process took about two months.
81: Shuffling songs, with two 45-minute technicals
Interview date: Mar 2023 · Report date: Feb 26, 2025 · Role: Software Engineer (New Grad) · Location: San Mateo, CA · Result: No offer
- OA: a factory min/max game, a two-question coding exam and a behavioral survey.
- Technicals: two 45-minute interviews with engineers, any language, with interviewers happy to clarify. One asked for a program to shuffle an input list of songs. They did not pass; a resume and skills behavioral interview would have been next.
82: An extra behavioral after four onsite rounds
Interview date: Jan 2023 · Report date: Mar 7, 2024 · Role: New Grad Software Engineer · Location: San Mateo, CA · Result: No offer
- After the OA, four onsite interviews (two coding, two behavioral), then one more behavioral. One question asked for a challenge they had faced.
- They had heard others got an extra technical instead; that was secondhand. The process took about four weeks.
83: Four coding questions and a motivation question
Interview date: Oct 2022 · Report date: Aug 19, 2023 · Role: Software Engineer New Grad · Result: Declined offer
- Two games (with glitches), a coding exam with one easy, two medium and one hard question, and a behavioral quiz.
- They were asked why they wanted to work at Roblox. The process took about three weeks; they declined the offer.
84: CodeSignal and simulations before four final interviews
Interview date: Oct 2022 · Report date: Nov 4, 2022 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer
- CodeSignal plus two game-like simulations, then a final round of two technical and two behavioral interviews.
- They called the final questions fairly standard and named none. The process took about two months.
85: Robot debugging, plague prediction and a rigid interviewer
Interview date: Oct 2022 · Report date: Nov 2, 2022 · Role: Software Engineer New Grad · Location: San Francisco, CA · Result: No offer
- OA: CodeSignal plus two simulations: building and debugging a robot, and predicting which foxes would die from plague. A year earlier they had a perfect CodeSignal but weak simulations and no final-round invite.
- Four-hour final: two technical and two behavioral interviews. The coding was not especially hard, but one interviewer got frustrated when they proposed approaches with the same runtime as the interviewer's preferred one.
86: Rejected after a final half-hour behavioral
Interview date: Oct 2022 · Report date: Oct 26, 2022 · Role: Software Engineer New Grad · Result: No offer
- They passed the earlier stages and were rejected after a 30-minute behavioral interview.
- One question asked what they learned from a previous internship. The process took about two months.
87: An onsite a month after the invite
Interview date: Oct 2022 · Report date: Oct 25, 2022 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer
- CodeSignal and a Roblox cognitive-game assessment. A few days later came an invite to a virtual onsite about a month out.
- The onsite had ordinary technical and behavioral questions, none named. The process took about two months.
88: Two technicals with very different interviewers
Interview date: Oct 2022 · Report date: Oct 12, 2022 · Role: New Grad Software Engineer · Result: No offer
- Two 30-minute behavioral sections and two 45-minute technicals.
- The first coding task was hard but familiar from a LeetCode medium; the second was new but simpler. One interviewer said little; the other engaged readily. Questions were withheld under an NDA, and the behavioral ones had no twists.
89: Four questions in two hours
Report date: Oct 31, 2022 · Role: Software Engineer (2023 new grad) · Result: No offer
- Two earlier assessment activities, then four easy-to-medium coding questions in 120 minutes. They did not advance; nothing was named.
90: An extra interview, then an accepted offer
Report date: Oct 16, 2022 · Role: SWE New Grad · Result: Accepted offer
- Two technical and two behavioral interviews, with easy-to-medium coding. A September post about an additional interview and an October update belong to this one application.
- They accepted the new grad offer. No questions were shared.
91: Four CodeSignal levels, then cognitive games
Interview date: Sep 2022 · Report date: Sep 22, 2022 · Role: New Grad Software Engineer · Location: Chicago, IL · Result: No offer
- CodeSignal with four questions: easy, medium, a medium-hard matrix problem and a medium dynamic-programming problem.
- Two Roblox cognitive-game stages. Engineer interviews were still ahead when they posted.
92: Four coding questions on Codility
Interview date: Aug 2022 · Report date: Sep 13, 2022 · Role: Software Engineer New Grad · Result: No offer
- Four coding questions and two games. This candidate named Codility as the coding platform, unlike the CodeSignal reports. No tasks were identified.
93: Virus spread and animal survival
Interview date: Apr 2022 · Report date: Jun 10, 2022 · Role: Software Engineer New Grad · Result: No offer
- One test had general coding questions, medium to hard with one easier question.
- The other asked about virus spread and where animals could survive; its mechanics were not described.
94: An offer despite a repeated question
Report date: Apr 19, 2022 · Role: Software Engineer New Grad · Result: Accepted offer
- Logic games through Roblox, then onsite technicals around easy to medium.
- The second interviewer first tried to give the same problem as the first, which felt disorganized. Recruiters were helpful. Problems were withheld.
95: A 70-minute general coding assessment
Report date: Apr 4, 2022 · Role: Software Engineer New Grad · Result: No offer
- CodeSignal general assessment: four problems in 70 minutes (one easy, two medium, one hard).
- A separate two-part Roblox assessment that was not standard coding. No details were given.
96: Making an elevator experience happier
Interview date: Dec 2021 · Report date: Jan 16, 2022 · Role: Software Engineer New Grad · Result: No offer
- Welcoming interviewers who worked through problems with the candidate. Some behavioral rounds felt like consulting discussions.
- One question asked how to make an elevator experience happier, with no API, algorithm or architecture deliverable stated. The process took about three weeks.
Patterns across the reports
- A four-interview final. Two technicals and two behavioral interviews in 74, 84, 85, 88 and 90; the timed ones were 45 and 30 minutes (74, 88).
- Four-question CodeSignal. Four coding questions from easy to hard in 83, 89, 91 and 95, with 70 or 120 minutes when timed (89, 95).
- Strong coding scores were not enough. Perfect coding did not secure a next round for 76 or, a year earlier, for 85.
Common questions
What did the older Roblox new grad final round look like?
Two 45-minute technicals and two 30-minute behavioral interviews (74, 88), sometimes as a four-hour block (85).
How many CodeSignal questions did Roblox give new grads?
Four in most older reports (83, 89, 91, 95); some had two (79, 81).
Were the Roblox technical questions hard?
Mostly easy to medium (88, 90, 94), with one hard dynamic-programming question (78).
Keep practicing
- Shuffle a Playlist (81) and Inventory Outfit Combinations (80).
- Roblox problem bank: every Roblox coding question on FastPrep (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.