Roblox · OA → Phone screen → Onsite
In processRoblox New Grad Engineer Rounds: 13 Experiences (Part 6 of 7)
Roblox new grad SWE reports, Sep to Nov 2020: a 90-minute HackerRank OA, then two 45-minute engineer rounds with browser history and weighted random tasks.
At a glance
- Process: a three-question, 90-minute HackerRank OA, then two technical interviews (45 minutes each where timed), then manager, bar-raiser or executive rounds (116, 117, 120, 121, 122, 126).
- Asked in this period: Browser History Operations, Common Prefix Length Sums and Largest Subgrid in 2 reports each; 13 more named tasks once each.
- Difficulty: OA questions were easy to medium where described (118, 122), though one candidate called the OA hard (121). Largest Subgrid and Paint the Ceiling timed out for two candidates (124, 127).
- Practise first: Browser History Operations, Weighted Random Key Selection and Design a Player Matchmaking Queue.
Coverage: New grad SWE (one Java engineer report), from the OA to offers. Washington, DC, San Francisco and the U.S., plus unstated locations. September to November 2020, by interview month when given, otherwise report date. All 13 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: 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 (current): 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
Fall 2020 candidates named a lot of tasks: 16 coding problems and one matchmaking design across 13 reports. The live rounds leaned on practical tasks such as browser history and weighted random picks.
| Topic | Reports | Last seen |
|---|---|---|
| Coding | 13 of 13 | Nov 2020 |
| Grids and matrices | 3 of 13 | Nov 2020 |
| Resume, projects or behavioral | 5 of 13 | Nov 2020 |
| Strings and prefixes | 3 of 13 | Nov 2020 |
| Dynamic programming | 2 of 13 | Nov 2020 |
| System or product design | 4 of 13 | Nov 2020 |
A candidate can appear in more than one row.
Questions we found
Algorithms / Data Structures
| Question | Reports | Last seen |
|---|---|---|
| Browser History Operations | 2 | Nov 2020 |
| Largest Subgrid | 2 | Nov 2020 |
| Common Prefix Length Sums | 2 | Nov 2020 (report date) |
| Run-Length String Compression | 1 | Nov 2020 |
| Slowest Key Press | 1 | Nov 2020 |
| Competitive Gaming Ranks | 1 | Nov 2020 (report date) |
| University Career Fair | 1 | Nov 2020 (report date) |
| Weighted Random Key Selection | 1 | Oct 2020 |
| Robot Shortest Walkable Path | 1 | Oct 2020 (report date) |
| Maximum Units on a Truck | 1 | Oct 2020 (report date) |
| Minimize Distinct Item Types After Removals | 1 | Oct 2020 (report date) |
| Prison Break / Largest Opening After Removing Bars | 1 | Oct 2020 (report date) |
| Can All Files Compile? | 1 | Sep 2020 |
| Equalize Piles of Boxes | 1 | Sep 2020 (report date) |
| Lifting Weights | 1 | Sep 2020 (report date) |
| Paint the Ceiling | 1 | Sep 2020 (report date) |
System Design
| Question | Reports | Last seen |
|---|---|---|
| Design a Roblox matchmaking system | 1 | Oct 2020 |
Projects and open-ended questions
| Question | Reports | Last seen |
|---|---|---|
| Walk through your projects | 1 | Nov 2020 |
| How might you handle fraud on Roblox at a strategic level? | 1 | Nov 2020 |
| Introduce yourself | 1 | Oct 2020 (report date) |
| Choose a project and explain its architecture | 1 | Oct 2020 (report date) |
| Explain how Redis was used in that project | 1 | Oct 2020 (report date) |
History (before November 2023): 13 detailed candidate timelines
115: Most OA points, but no next round
Interview date: Nov 2020 · Report date: Feb 23, 2021 · Role: Software Engineer New Grad · Location: Washington, DC · Result: No offer
- HackerRank arrived about three weeks after applying, due around Thanksgiving. They scored most of the points but did not advance, and had no rejection letter when they posted.
- Dynamic programming and an optimization task came up; neither was named.
116: Browser history and a strategic fraud discussion
Interview date: Nov 2020 · Report date: Jan 21, 2021 · Role: New Grad Software Engineer · Result: Accepted offer
- Virtual onsite, about a month after the OA: two 45-minute engineer interviews. One task was to implement browser history with back, forward and visiting a new site; they forgot the other.
- Manager rounds: two managers on the resume, projects and open-ended questions, including how they might handle fraud on Roblox at a strategic level (a discussion, not a fraud-detection design). Then one more engineering-manager interview. They accepted the offer.
117: Two months of silence, then a head recruiter
Interview date: Nov 2020 · Report date: Jan 4, 2021 · Role: Software Engineer New Grad · Result: No offer
- A three-question OA, two technical interviews, then a three-hour onsite mixing technical and behavioral. Medium coding on graphs, sorting and binary search; no tasks named.
- After more than two months without a reply, they contacted a head recruiter and then got a rejection.
118: Compression, a matrix limit and the slowest key
Interview date: Nov 2020 · Report date: Dec 3, 2020 · Role: Software Engineer New Grad · Result: No reply yet
- A 90-minute HackerRank with three medium questions: string compression, the largest matrix square under a sum limit and the longest-pressed key.
- They felt it went poorly and had not heard back.
119: Gaming ranks, a career fair and prefix sums
Report date: Nov 26, 2020 · Role: SWE New Grad
- Three questions in 90 minutes: Competitive Gaming, University Career Fair and Common Prefix Length.
- In the gaming task, tied scores share a rank and the next rank skips ahead (three players tied first are followed by rank four), and a score of zero never qualifies. With scores
[100,50,50,25]and cutoff rank3, three players qualify. No results were shared.
120: Browser history and a disputed weighted-random task
Interview date: Oct 2020 · Report date: Jan 16, 2021 · Role: Software Engineer New Grad · Location: San Francisco, CA · Result: No offer
- A three-question HackerRank, then two technicals. The first, which they called system design, asked for browser history with back and forward.
- In the second, they coded one interviewer's explanation before another engineer said the task was different. With ten minutes left they wrote a naive solution to the corrected task: weighted random selection from a string-to-integer map. Example:
{cat:5, dog:2, human:2, baby:1}, socatcomes up 5/10 of the time andbaby1/10.
121: An offer two months after the final round
Interview date: Oct 2020 · Report date: Jan 5, 2021 · Role: New Grad Software Engineer · Result: Declined offer
- A hard three-question OA, two easy-to-medium technicals, then hiring-manager and bar-raiser interviews. Questions covered algorithms, improving an unnamed system, and the resume.
- Weeks passed between stages, and almost two months after the final round before the offer. By then they had taken another job. They liked the engineers but not the delays.
122: Matchmaking design with an executive
Interview date: Oct 2020 · Report date: Dec 9, 2020 · Role: Software Engineer New Grad · Result: No offer
- OA: one easy and two medium problems. Then a phone/onsite stage with two medium questions. None of the five were named.
- Bar raiser: an executive mixed behavioral questions with designing a Roblox matchmaking system; queue rules and scale were not given.
- Hiring manager: background and tell-me-about-a-time questions.
123: Project architecture, Redis and a robot path
Report date: Oct 27, 2020 · Role: Java engineer / software engineer (campus hire)
- Projects: introduce yourself, pick a project and explain its architecture, then how Redis was used in it.
- Coding: on an
m×ngrid with walkable1s, blocked0s, a start and a target, find the shortest route moving in four directions (Robot Shortest Walkable Path). The interviewer asked about the approach and offered help, but they could not implement it. No rejection was confirmed.
124: Two questions in 15 minutes, then a grid timeout
Report date: Oct 2, 2020 · Role: SWE New Grad · Location: United States
- Maximum Units on a Truck (box counts, units per box, a capacity) and Minimize Distinct Item Types After Removals (remove
kitems to leave the fewest types) took about 15 minutes together. - The third, Largest Subgrid, asked for a square size whose every subgrid stays under a sum bound. Their solution timed out. This recap said "less than" the limit; a fuller statement elsewhere used "at most". No reply was reported.
125: A prefix count, Prison Break and an easy task
Report date: Oct 2, 2020 · Role: SWE New Grad
- They named Common Prefix Length, Prison Break / Largest Opening After Removing Bars and an easy third question they did not identify. No results were shared.
126: File dependencies and a long wait after good feedback
Interview date: Sep 2020 · Report date: Dec 1, 2020 · Role: Software Engineer, New Grad · Result: No offer
- A 90-minute HackerRank, then more than a month of waiting.
- Back-to-back technicals in a shared editor, with positive feedback from both interviewers. One task: given files and their dependencies, can every file compile with all dependencies met and no cycle (Can All Files Compile?).
- About two months later there was still no decision.
127: Full marks on boxes, ceiling timeouts
Report date: Sep 21, 2020 · Role: SWE New Grad
- Piles of Boxes passed 15/15.
- Lifting Weights went unfinished, though they thought DP would work. Pick plates to get the most weight without going over capacity;
[1,3,5]with capacity7gives6(1+5). Up to 42 plates, with weights and capacity up to10^9. - Paint the Ceiling passed 7/11; the rest timed out.
Patterns across the reports
- Two technicals, then managers. Five reports followed the OA with two technical interviews and then manager, bar-raiser or executive rounds (116, 117, 120, 121, 122).
- Long waits. A month or more between stages or before a decision in 116, 117, 121 and 126.
- Practical live tasks. Browser history (116, 120), weighted random (120), file dependencies (126) and a robot path (123).
Common questions
What did Roblox ask new grads in 2020 technical interviews?
Browser history with back and forward (116, 120), weighted random selection (120), file-dependency compilation (126) and a shortest grid path (123).
How long did Roblox take to respond in 2020?
Often over a month: a month before the onsite (116), two months of silence (117), and nearly two months before an offer (121).
Did Roblox ask system design to new grads?
Once, in a bar-raiser round: a matchmaking system (122). Another candidate called the browser-history round system design (120).
Keep practicing
- Browser History Operations (116, 120), Weighted Random Key Selection (120) and Can All Files Compile? (126).
- Design a Player Matchmaking Queue: the design round from 122.
- Roblox problem bank and Roblox system design bank (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.