RepostedRoblox logo

Roblox · OA → Onsite

In process

Roblox New Grad Coding Rounds: 23 Experiences (Part 2 of 7)

Software engineer · New GradSep 2025
Shared byjanebeingjane

Roblox new grad SWE reports from Dec 2024 to Sep 2025: games plus CodeSignal or HackerRank, then two 45-minute coding rounds, with five coding tasks named.

At a glance

  • Process: a multi-part assessment (vehicle and factory games, workplace scenarios, a written explanation, two coding questions), sometimes a 20-minute recruiter screen, then two 45-minute technicals with one question each and two 30-minute behavioral interviews (42, 43, 48).
  • Asked recently: coding in 21 of 23 reports, vehicle or robot builds in 9, the factory game in 6. Named tasks: one-digit pairs (26), largest square (27), pagination (28), island counting (34), array partitioning (42).
  • Difficulty: live rounds usually paired a medium with a harder, wordy multipart question (28, 29, 33, 35).
  • Practise first: Count Pairs Differing in One Digit, Cursor-Based Pagination Over Sorted Logs and Largest Square Under Building Heights.

Coverage: New grad and early-career SWE, assessment through behavioral. San Mateo, Palo Alto, San Francisco, Jacksonville (FL) and unstated locations. Dec 2024 – Sep 2025, by interview month, else report date.

In this series

  • Part 1: Sep 2025 – Oct 2026, 25 reports: today's game assessment and live rounds.
  • Part 2 (current): 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

Five candidates here named a real coding prompt, and one got a broad product-design question.

Topic Reports Last seen
Coding (OA or live rounds) 21 of 23 Sep 2025
Vehicle or robot terrain game 9 of 23 Sep 2025
Behavioral or workplace scenarios 8 of 23 Sep 2025
Other or unnamed games 7 of 23 Aug 2025
Factory / production game 6 of 23 Sep 2025
Written reasoning 5 of 23 Sep 2025 (report date)
Arrays and pair counting 3 of 23 Sep 2025
Sliding window 2 of 23 Sep 2025
Grids 2 of 23 Sep 2025
Trie 1 of 23 Sep 2025
System design 1 of 23 Aug 2025 (report date)
Object-oriented design 1 of 23 Feb 2025

A candidate can appear in more than one row.

Questions we found

Algorithms / Data Structures

Question Reports Last seen
Count Pairs Differing in One Digit 1 Sep 2025
Largest Square Under Building Heights 1 Sep 2025
Pagination over array data 1 Sep 2025
Island-style graph traversal 1 Aug 2025 (report date)
Array partitioning with two pointers 1 Feb 2025

System Design

Question Reports Last seen
Design a new Roblox feature that improves users' lives (practice) 1 Aug 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
Vehicle-building / terrain game 9 Sep 2025
Factory-profit game 6 Sep 2025
Cat game 1 Aug 2025

Behavioral (BQ)

Question Reports Last seen
Tell me about convincing someone to adopt a different approach 1 Feb 2025
Tell me about a time you showed leadership 1 Dec 2024 (report date)

Written reasoning

Question Reports Last seen
Explain the reasoning behind your solution 1 Sep 2025 (report date)
Explain the reasoning behind your factory decisions 1 Aug 2025 (report date)

23 detailed candidate timelines, loops, and screens

26: Integer pairs that differ in one digit

Interview date: Sep 2025 · Report date: Oct 9, 2025 · Role: SWE, early career · Result: No offer

  1. The assessment had terrain robots, factory-output optimization, coding, and office scenarios with best and worst responses.
  2. Two coding questions, using dictionaries and a 2D traversal. One asked to count pairs of integers that differ in exactly one decimal digit. The traversal task's goal was not given, nor were rules for unequal digit lengths or repeats.

27: A square-fitting question after car and factory games

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

  1. Car and factory activities in Roblox (vehicle, factory), then behavioral questions, then two coding questions.
  2. One coding task asked for the largest square that fits under building heights, set on a grid; the full input format was not given. The other task was unnamed. The process took about a week.

28: A much harder second technical, with pagination

Interview date: Sep 2025 · Report date: Sep 23, 2025 · Role: SWE, early career · Location: San Mateo, CA · Result: No offer

  1. OA: Roblox problem-solving games, multiple choice, writing and coding.
  2. Two technicals: one ordinary LeetCode-style question and one difficult multipart problem. One task involved pagination over array data; cursor format, log schema and tie rules were not given and come from the practice version. The process took about two weeks.

29: A two-part medium before a hard Trie question

Interview date: Sep 2025 · Report date: Sep 13, 2025 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer

  1. One medium and one hard problem, with friendly interviewers.
  2. The medium had two parts, about 30 minutes each, so a first solution had to come fast enough to leave time for the follow-up.
  3. The topics were sliding window and Trie. Neither task's goal was shared.

30: Coding, game scores and a written explanation

Report date: Sep 23, 2025

  1. A four-part assessment: two medium-to-hard coding questions and two Roblox games.
  2. One game asked them to maximize a score and explain the choices in writing; another had them build a robot.
  3. They were also asked to explain the reasoning behind their solution. The coding statements and scoring were not described.

31: A car, a factory pipeline and workplace choices

Report date: Sep 14, 2025 · Role: SWE, early career · Location: San Mateo, CA · Result: No offer

  1. Built a car for different terrains, then raised factory profit by optimizing a pipeline.
  2. Hypothetical workplace choices and a standard coding challenge followed. No prompts were shared.

32: A factory, robots and an unnamed cat game

Interview date: Aug 2025 · Report date: Aug 26, 2025 · Role: New Grad Software Engineer · Location: Palo Alto, CA · Result: No offer

  1. Coding and number games: factory profit and cost trade-offs (factory game), robot building (vehicle game) and a cat game whose name and rules they did not give.
  2. They were invited to interview; the process took about a week.

33: A medium first, then a wordy two-part hard

Report date: Aug 31, 2025 · Role: SWE New Grad

  1. Two technical interviews: the first question medium, the second hard, with two parts and a lot of wording.
  2. Neither problem was named, and no final decision was shared.

34: Designing a feature, then an island-style graph task

Report date: Aug 26, 2025 · Role: SWE New Grad

  1. First technical: a design-heavy round asking for a new Roblox feature that would improve users' lives. No specific feature was named; Design a Like/Unlike Service is a practice take on that broad prompt.
  2. Second technical: a graph traversal problem that reminded them of an islands question. They got about halfway, took a hint, and felt the interviewer was happy with the final solution. Whether they advanced was not stated.

35: A sliding-window question with a harder extension

Report date: Aug 26, 2025 · Role: SWE New Grad

  1. Live coding that started easy-medium and extended to medium-hard. One question used a sliding window.
  2. The prompts were wordy; the interviewers were friendly and helped in discussion. They compared the difficulty to 3Sum, which does not mean 3Sum was asked.

36: Strong game scores and an invitation for the 2026 role

Report date: Aug 25, 2025 · Role: SWE New Grad (2026)

  1. Scores: 600/600 coding, five working robots on the first track and three or four on the second (vehicle game), and a factory score a little above 150k.
  2. The factory essay asked for their reasoning and what they would change with more time.
  3. They were invited to schedule two technical interviews. The post ended before those rounds.

37: Changing car parts, then explaining the choices

Report date: Apr 9, 2025 · Role: SWE, early career · Result: No offer

  1. Logic games followed by written reasoning. One asked them to modify a remote-controlled car to cross several terrain types and reach a goal.
  2. No coding assignment was described.

38: HackerRank, then timed system-optimization games

Report date: Apr 4, 2025 · Role: SWE New Grad · Result: No offer

  1. A portal invite led to a HackerRank coding test.
  2. Roblox activities covered performance, personality and critical thinking. In one game they improved a system against a time limit; the system and the coding tasks were not named.
  3. The process lasted about two months.

39: Robot cars and toys in a recent-graduate assessment

Report date: Mar 24, 2025 · Role: Software Engineer (recent graduates) · Location: Jacksonville, FL · Result: Failed the assessment

  1. Four assessments, which they described as two coding and two written questions, plus building robot cars and toys.
  2. They enjoyed the activities but did not pass. How those parts map to four components is unclear.

40: Coding, two logic games and a workstyle section

Report date: Mar 12, 2025 · Role: Software Engineer New Grad · Result: No offer

  1. Two to three hours on coding (one easy and one medium task), two logic activities partly in Roblox, and a personality/workstyle assessment.
  2. No problem statements or workstyle questions were shared.

41: Two OA questions before live coding

Report date: Mar 6, 2025 · Role: Software Engineer, New Grad · Result: No offer

  1. A two-question online coding assessment of standard data-structure and algorithm problems, not named.
  2. Passing it led to a recruiter scheduling a live coding interview, with more rounds after.

42: A 20-minute recruiter screen and two different engineers

Interview date: Feb 2025 · Report date: Oct 10, 2025 · Role: SWE New Grad · Location: San Mateo, CA · Result: No offer

  1. OA, then a 20-minute recruiter screen, then two 45-minute technicals with different engineers, one question each, then behavioral.
  2. Topics: two pointers and array partitioning, plus an object-oriented question. The partition rule and the object model were not given. The process took two weeks.

43: One question per 45-minute technical

Interview date: Feb 2025 · Report date: Mar 5, 2025 · Role: Software Engineer New Grad · Location: San Mateo, CA · Result: No offer

  1. An assessment of about three hours, a recruiter follow-up, then two technicals with different engineers, 45 minutes and one question each.
  2. Behavioral: two 30-minute interviews with engineering managers or directors. One asked about convincing someone to adopt a different approach or solution.
  3. They called both the technical and behavioral questions familiar. The process took about four weeks.

44: A two-week window, with easy extensions

Interview date: Feb 2025 · Report date: Feb 25, 2025 · Role: SWE New Grad · Result: No offer

  1. A multi-part assessment covering coding and aptitude, with two weeks to finish. Getting an extension was easy.
  2. No coding or aptitude items were named.

45: A medium and a hard HackerRank question

Interview date: Jan 2025 · Report date: Feb 12, 2026 · Role: SWE New Grad · Location: San Mateo, CA · Result: No offer

  1. Critical-thinking games on the desktop app and HackerRank coding: one medium and one hard data-structure and algorithm question.
  2. The games reminded them of Kaiju-style activities. No game or coding details were given. The process took about two weeks.

46: The game mechanics were the hard part

Interview date: Jan 2025 · Report date: Apr 22, 2025 · Role: Software Engineer New Grad · Location: San Francisco, CA · Result: No offer

  1. A campus applicant struggled to work out two games: building a factory to make the most money and building a car that could cross a map. The process took two weeks.

47: Long prompts in a four-hour assessment

Report date: Jan 20, 2025 · Role: Software Engineer (New Grad) · Location: San Mateo, CA · Result: No offer

  1. An OA of about four hours, with long coding statements around medium to hard.
  2. Their note that they reached a technical without being asked questions is ambiguous; no extra live round or task is confirmed.

48: A 90-minute technical and a 60-minute behavioral

Report date: Dec 20, 2024 · Role: SWE New Grad · Result: No offer

  1. OA: coding, brainteaser games and a behavioral test.
  2. Live: a technical of about 90 minutes and a behavioral of about an hour. One question asked for a time they showed leadership. No coding prompt was given.

Patterns across the reports

  1. Two technicals, one question each. Five reports described two live coding rounds (28, 29, 33, 42, 43); the two that gave timings said 45 minutes each (42, 43).
  2. The second question is the hard one. Live rounds paired a medium with a hard or multipart question in 28, 29, 33 and 35, and the hard ones were often long to read (33, 35).

Common questions

What coding questions does Roblox ask new grads?

Named tasks here: one-digit-difference pairs (26), largest square under heights (27), pagination over arrays (28), island traversal (34) and array partitioning (42). Trie and sliding window came up as topics (29, 35).

How long are Roblox new grad technical interviews?

45 minutes with one question each, in both reports that gave timings (42, 43). One earlier report had a single 90-minute technical (48).

What is the Roblox new grad behavioral round like?

Two 30-minute interviews with managers or directors (43); one candidate had a one-hour behavioral (48). Questions named: convincing someone to change approach (43) and showing leadership (48).

How long do you get for the Roblox assessment?

Two weeks in one report, with extensions easy to get (44). Candidates spent two to four hours on it (40, 43, 47).

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.