RepostedRoblox logo

Roblox · OA → Onsite

In process

Roblox New Grad Games and BQ: 25 Experiences (Part 3 of 7)

Software engineer · New GradOct 2024
Shared byjanebeingjane

Roblox new grad SWE reports, Nov 2023 to Oct 2024: CodeSignal plus game assessments, two 45-minute technicals, then behavioral on teamwork and conflict.

At a glance

  • Process: a four-part assessment (a 50-minute CodeSignal with two questions, two 25-minute Roblox games, about 20 minutes of decision-making scenarios), then two 45-minute technicals and two behavioral interviews (60, 61, 63, 64, 70).
  • Asked recently: coding in nearly every report; vehicle or robot builds in 5 and the factory game in 4. Named tasks: pairing socks by ID (60), a Trie prefix-string task (55) and random items in two UI components (51).
  • Difficulty: OA questions were mostly medium (59, 63, 64, 65); one candidate got two hard ones in 50 minutes (67). Live rounds were called medium to hard (55).
  • Practise first: Pair Left and Right Socks by ID, Implement Trie and the vehicle-build game adaptation.

Coverage: New grad and early-career SWE, assessment through offers. San Mateo, San Francisco and one "California, MD" location, plus unstated ones. Current reports: Nov 2023 – Oct 2024. Three Sep–Oct 2023 reports are in 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 (current): 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

Behavioral questions are the richest detail in this stretch: four candidates gave the exact prompt. On coding, most kept to difficulty labels.

Counts cover the 22 current reports (49–70).

Topic Reports Last seen
Coding (OA or live rounds) 19 of 22 Oct 2024
Workplace scenarios or behavioral 12 of 22 Oct 2024
Vehicle or robot terrain game 5 of 22 Oct 2024
Factory / production game 4 of 22 Oct 2024
Strings and Trie 1 of 22 Sep 2024
Linked list 1 of 22 Oct 2024
Arrays 1 of 22 Nov 2023
Random selection in UI 1 of 22 Oct 2024

A candidate can appear in more than one row.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Pair left and right socks by ID 1 Jun 2024 (report date)
Prefix-string problem using a Trie (practice) 1 Sep 2024

Frontend / UI

Question Reports Last seen
Render random items in two components 1 Oct 2024

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 Oct 2024
Factory-profit game 4 Oct 2024
Cat game 1 Oct 2024

Behavioral (BQ)

Question Reports Last seen
Tell me about a teammate who was not contributing 1 Aug 2024
Tell me about a conflict you worked through with a teammate 1 Mar 2024
Tell me about a time you showed listening skills 1 Nov 2023 (report date)

22 detailed candidate timelines, loops, and screens

49: Four Python questions and three game themes

Interview date: Oct 2024 · Report date: Jul 2, 2025 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer

  1. Four Python questions on CodeSignal.
  2. Games: a cat game, vehicle creation (one goal was getting through a set stretch of track) and factory optimization. Coding statements were not shared.

50: A linked-list topic and two video interviews

Interview date: Oct 2024 · Report date: Apr 9, 2025 · Role: New Grad Software Engineer · Location: San Mateo, CA · Result: No offer

  1. An online application quickly led to an assessment with coding and a game.
  2. Two video coding interviews, then behavioral. They mentioned a linked-list question without the operation. The process took about two weeks.

51: Random items in two components

Interview date: Oct 2024 · Report date: Nov 18, 2024 · Role: Software Engineer New Grad · Location: "California, MD" · Result: No offer

  1. Several coding screens and games over about three weeks.
  2. They were asked how to render items randomly in two components. Independence, duplicates, component state and framework were not specified; the practice version fills those in.

52: A custom CodeSignal and most/least-effective choices

Report date: Oct 24, 2024 · Role: New Grad Software Engineer · Result: No offer

  1. A custom CodeSignal, a car-building game, factory maximization and a scenario section.
  2. For each workplace situation they chose the response they were most and least likely to give. No scenario or coding text was shared.

53: Fourteen days for four tasks

Report date: Oct 14, 2024 · Role: New Grad Software Engineer · Result: No offer

  1. An emailed invite: coding, two problem-solving sections and decision making, with 14 days to finish.
  2. A rejection email came within about a week.

54: A factory task and a next-day rejection

Report date: Oct 8, 2024 · Role: New Grad Software Engineer · Result: No offer

  1. The named activity was factory assembly to maximize profit.
  2. They felt the OA went very well but were rejected the next day without explanation.

55: A prefix-string problem with a Trie

Interview date: Sep 2024 · Report date: Oct 15, 2024 · Role: SWE New Grad · Location: San Mateo, CA · Result: No offer

  1. A multi-part assessment, then two medium-to-hard technicals back to back.
  2. They felt the first went very well and solved the second, but did not advance. The process took about three weeks.
  3. The task they could name was a prefix-string problem using a Trie; its operations were not given. Implement Trie is the standard baseline.

56: A recruiter check-in, then good news

Report date: Sep 27, 2024 · Role: SWE New Grad

  1. A recruiter reached out two days after final interviews. At about a week they were still waiting.
  2. A September 30 update reported good news. No questions were shared.

57: Compiler trouble in one round, an edge-case fix in the other

Report date: Sep 26, 2024 · Role: SWE New Grad

  1. First technical: nearly the whole round went on fixing compilation problems. The code eventually ran; tests were only discussed.
  2. Second technical: done in about 20 minutes with tests and follow-ups. They missed an edge case at first, then fixed it.
  3. Rejected without feedback. Neither task was named.

58: An offer after about a week

Report date: Sep 25, 2024 · Role: SWE New Grad (2025 cohort) · Result: Offer

  1. A recruiter emailed that processing was underway and asked how the interviews went.
  2. The offer came about a week after the final interviews. No questions were shared.

59: A written response of at least 500 characters

Interview date: Aug 2024 · Report date: Oct 31, 2024 · Role: Software Engineer New Grad · Location: San Francisco, CA · Result: No offer

  1. Two roughly medium coding questions, two problem-solving games and a written response of at least 500 characters.
  2. A behavioral question asked about a teammate who was not contributing and how they handled it. The process took about two weeks.

60: Matching left and right socks by ID

Report date: Jun 26, 2024 · Role: Software Engineer New Grad · Result: No offer

  1. Two Zoom sessions: technical questions with different interviewers (about 45 minutes each) and behavioral interviews with two interviewers (about 45 minutes each).
  2. Coding: given socks with an ID, color and left/right side, return pairs of IDs, each one left and one right sock of the same color (Pair Left and Right Socks by ID). No tie-break was given.

61: A technical screen before a superday

Interview date: Mar 2024 · Report date: Aug 13, 2026 · Role: Software Engineer (new grad) · Location: San Francisco, CA · Result: Accepted offer

  1. Two problem-solving games, a technical screen, then a superday with technical and behavioral interviews; they were unsure of the exact counts.
  2. A behavioral question asked about a conflict they worked through with a coworker or teammate. The process took about two months.

62: A terrain-crossing robot

Interview date: Mar 2024 · Report date: Jul 18, 2025 · Role: SWE, early career · Result: No offer

  1. A questionnaire, a coding test and two Roblox games. One asked for as many robot cars as possible that could cross the terrain.
  2. They mentioned Kaiju Cats as practice, not as part of the assessment.

63: A 50-minute coding test and two 25-minute tasks

Report date: Mar 26, 2024 · Role: Software Engineer New Grad · Result: No offer

  1. A 50-minute CodeSignal with two medium algorithm questions.
  2. Two 25-minute problem-solving assessments and a decision-making section of about 20 minutes. They did it all in one day.

64: Two mediums, two games and a behavioral task

Report date: Mar 25, 2024 · Role: Software Engineer New Grad · Result: No offer

  1. CodeSignal with two medium questions, two Roblox games of about 25 minutes each, and a 25-minute behavioral task. Nothing was named.

65: Twenty workplace scenarios

Report date: Feb 27, 2024 · Role: New Grad Software Engineer · Result: No offer

  1. Two LeetCode-style questions of at least medium difficulty, then two Roblox games.
  2. A decision-making part with 20 scenarios, each needing a most and least effective response.

66: A sandpit, branches and a robot car

Report date: Feb 25, 2024 · Role: Software Engineer New Grad · Result: No offer

  1. A coding screen, then a factory simulator and a robot-car activity: get across a sandpit and through branches.
  2. They disliked the car game and questioned its relevance.

67: Two hard questions in 50 minutes

Report date: Feb 12, 2024 · Role: SWE New Grad · Result: No offer

  1. Two hard coding questions in 50 minutes, then a game-style problem-solving assessment in Roblox. They did not advance.

68: Attaching parts to cross different terrains

Report date: Dec 18, 2023 · Role: Software Engineer New Grad · Result: No offer

  1. Four online tests over a few hours: two games, coding and decision making.
  2. One game had them attach parts to a robot to cross several terrain types. They could not tell how they did or what was being measured.

69: A two-week window and candidate resources

Interview date: Nov 2023 · Report date: Nov 26, 2023 · Role: SWE, early career · Result: No offer

  1. Games, coding and decision making, with two weeks to finish and extensions available. A candidate platform offered resources and a community of applicants.
  2. They named array navigation and manipulation plus hypothetical behavioral questions, without specifics.

70: Advancing despite a rough coding test

Report date: Nov 2, 2023 · Role: New Grad Software Engineer · Location: San Mateo, CA · Result: No offer

  1. The OA led to two 45-minute technicals and two 30-minute behavioral interviews. Their coding went badly but the puzzles went well, and they advanced.
  2. One behavioral question asked for a time they showed listening skills.

History (before November 2023)

These three reports are just over three years old, so they stay out of the counts and tables above.

71: Lag during an online puzzle

Interview date: Oct 2023 · Report date: Nov 15, 2023 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer

  1. Standard coding plus a Roblox puzzle activity, which lagged and hurt their score. They did not advance. The process took about two weeks.

72: Runtime follow-ups and two behavioral questions

Interview date: Oct 2023 · Report date: Oct 26, 2023 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer

  1. OA: two coding questions with factory-profit and vehicle-terrain games.
  2. Technical: two 45-minute coding rounds with questions on runtime and how to improve it.
  3. Behavioral: two 30-minute interviews: a time they navigated differences or diversity on a team, and a time they had to learn a new skill immediately. A decision came about a week later.

73: Priority queues and strings

Interview date: Sep 2023 · Report date: Nov 22, 2023 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer

  1. CodeSignal and a Roblox game assessment, then two technical problems using priority queues and string manipulation, then behavioral. They believed the games carried more weight, which is their guess, not a stated policy.

Patterns across the reports

  1. A four-part OA with set timings. A 50-minute CodeSignal with two questions (63, 67), two games of about 25 minutes each (63, 64), and a decision-making section of about 20 minutes or 20 scenarios (63, 65).
  2. Two technicals, then two behavioral interviews. 60 and 70 both described two technicals and two behavioral interviews; 50 and 55 also had two technical rounds.
  3. Quick decisions. Rejections came the next day (54) or within a week (53), and an offer about a week after finals (58).

Common questions

How long is the Roblox new grad CodeSignal?

50 minutes for two questions in both reports that timed it (63, 67).

What are the Roblox assessment games?

Vehicle or robot builds that cross terrain, a factory profit game and, once, a cat game (49, 52, 62, 66, 68).

What behavioral questions does Roblox ask new grads?

Named prompts: a teammate who was not contributing (59), a conflict with a teammate (61) and a time you showed listening skills (70).

How fast does Roblox reply after new grad interviews?

About a week in two reports (56, 58). After the OA, one rejection came the next day (54).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.