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.” The rest of the author's notes on Software Engineer interview at Roblox, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.
View Post