Game Shop / Transaction System Design

System DesignDatabricksLast reported November 2025Low Frequency
Reported
2× across candidate reports
First seen
October 2025
Last reported
November 2025
Reported outcome
unknown

Problem Overview

Design a game shop transaction system. The system should support the following core operations: 1. Add credit to a user's account (recharge/top-up). 2. User purchase of an in-game item — including a discussion of why a "pending" status is used, and whether the API request body should use item quantity…

  • 5 candidate-reported follow-ups — the exact probes interviewers asked, with the trigger for each
  • The rest of the problem statement — full requirements, constraints, and edge cases
  • Approach and trade-offs — what passing candidates did, and the mistakes that sink people
Unlock the full Databricks catalog
Full problem statements, candidate-reported follow-ups, and walkthroughs — for every Databricks question.
Unlock with Pro
Already a member? Sign in
Verified Source
Every question is reconstructed from multiple independent candidate reports. Verbatim follow-ups, not invented ones.
Codex Fact-Checked
Technical claims, formulas, and scale numbers are reviewed against primary sources.
Interviewer Follow-ups
The exact follow-ups reported by candidates, with the trigger that prompts each one — plus the mistakes that sink people.
Is this helpful?