Roblox Software Engineer interview questions

46 Software Engineers have shared notes from their Roblox interviews, with the questions they were asked in each round. That is 77% of the 60 Roblox interview notes on Screna AI.

46 Software Engineer interview notes

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Roblox system design round, one big question about deferred payment flows. Pretty intense scope for a single session, they really wanted you to go deep on every layer rather than just sketch a high-level diagram.
  • Design a payment hold system that authorizes funds at one time and either captures or releases them later. Cover the full flow with payment providers, how you'd schedule and retry capture/expiry jobs, partial captures, refunds, reconciliation between your internal ledger and provider state, and how you guarantee exactly-once semantics for the eventual capture.

“This question is basically five questions stapled together.”

View Post

Roblox·Software Engineer·Technical Phone Screen

Jun 2026
Roblox coding round, one tree traversal problem. Pretty clean question but the tie-breaking constraint is the kind of thing that trips you up if you're not careful.
  • Given the root of a tree, return the node at the maximum depth. If multiple nodes share that depth, return whichever appears first in pre-order traversal.

“The base problem is easy but I almost missed the tie-breaking rule.”

View Post

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Roblox for a software engineer role. The whole session was basically one deep question about scheduled payments, and they kept pulling on threads I didn't fully think through.
  • Design a payment system that supports scheduled payments, where a user submits a payment now but it executes at a future time.
  • How would you handle cancellation or modification of a payment that's already been queued for future execution?
  • What happens if the payment gateway is down when a scheduled payment fires? Walk through your failure handling approach.
  • How do you guarantee exactly-once execution for a scheduled payment if the scheduler fires the job more than once?

“I started with a DB row and a polling job, which felt safe but they immediately pushed on scale.”

View Post

Roblox·Software Engineer·Technical Phone Screen

Jun 2026
Roblox technical phone screen, one meaty design question about autocomplete with some interesting follow-ups on trade-offs. The problem sounds like a standard trie question until they start pushing on memory and latency.
  • You have three parallel arrays: query strings, timestamps for each query, and a list of prefix strings to look up. For each prefix, return the matching queries ranked by frequency descending, then by earliest timestamp on ties. Design a data structure to build this index and answer prefix lookups efficiently.

“My first instinct was a trie and I went with it, but I fumbled explaining what to store at each node.”

View Post

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Roblox for a software engineering role, focused entirely on designing a matchmaking system for a large-scale multiplayer game. Dense question with a lot of moving parts and I don't think I covered everything as cleanly as I wanted to.
  • Design a matchmaking system for an online multiplayer game at scale, covering game modes, party sizes, latency targets, skill-based bucketing, region sharding, and how you'd handle millions of concurrent players.
  • How would you handle players who go stale or disconnect while waiting in the matchmaking queue?
  • How would you design fairness into the matchmaking system, specifically to detect and handle smurfing or account boosting?

“This is one of those questions where the scope is so wide that you almost have to negotiate with yourself about what to skip.”

View Post

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Roblox system design round for a software engineer role. The whole session was basically one big question about matchmaking, and it went deeper than I expected across like five different sub-topics.
  • Design a matchmaking service for an online multiplayer game that queues players, matches them by skill rating and region, forms groups of N players, and notifies them when a match is found.
  • How would you handle cross-region matchmaking given latency constraints, and what are the trade-offs between match quality and queue wait time?
  • Walk through your storage choices for the player queue. Would you use in-memory storage or a persistent store, and how do you handle failures or service crashes?

“I started with the data model which felt safe, but they kept pushing me toward the algorithm side faster than I wanted.”

View Post

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Roblox for a software engineer role. One question, the whole session, and it went deeper than I expected for what sounds like a simple feature on the surface.
  • Design a like button counter system similar to Facebook's, supporting like/unlike per user, real-time-ish total counts, and whether the current user has liked a post. How do you scale it to billions of posts with high read throughput?

“I started with the obvious stuff, a likes table keyed on (user_id, post_id) with a unique constraint for idempotency.”

View Post

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Roblox for a software engineering role, focused entirely on building a Likes system from scratch. The question had a lot of surface area and pushed into some genuinely tricky territory around consistency and scale.
  • Design a Likes system that supports liking/unliking items, checking if a user liked something, listing all items a user has liked (paginated), and fetching the total like count for an item. Focus on scalability and data schema.

“This looked simple at first and then just kept expanding.”

View Post

Roblox·Software Engineer·Technical Phone Screen

Jun 2026
Did a technical phone screen for a Software Engineer role at Roblox. One coding question, grid traversal, felt pretty standard but there were a few details I fumbled on under pressure.
  • Given a 2D grid with walkable cells and obstacles, a start cell, and an end cell, determine if a character can reach the end using 4-directional movement. Implement a graph traversal solution and explain how you handle visited tracking.

“I went with DFS because it felt more natural to code quickly.”

View Post

Roblox·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Roblox for a software engineer role, focused entirely on payment processing. It was a deep one, they really wanted to see if you could go beyond the happy path and get into the weeds on consistency, fraud, and PSP retries.
  • Design a payment processing system. Walk through the functional requirements including payment requests, support for multiple payment methods like cards, wallets, and bank transfers, refunds, idempotency, and reconciliation.
  • What are the non-functional requirements you'd prioritize for a payment system, and how do you handle exactly-once semantics and PCI compliance?
  • Describe the high-level architecture of the payment system. How do the API gateway, payment service, ledger, PSP integration, async event pipeline, and fraud detection fit together?
  • How would you implement idempotency keys and handle retries when a PSP call fails or returns an ambiguous response?
  • How would you handle distributed transactions across the payment service and ledger? Would you use sagas or two-phase commit?
  • How would you scale this payment system and what would your monitoring and alerting strategy look like?

“The scope of this thing hit me pretty fast.”

View Post