Skip to main content
PreparationZone Logo
PrepZone

Design Snake and Ladder

Board, dice, snakes, ladders, and player positions.

Pass checkpoint below

Read these first

Why this matters

  • Board with cells 1–100
  • Scope — what "Board cells" covers inside Snake and Ladder and what it does not
  • Scope — what "Dice" covers inside Snake and Ladder and what it does not
  • Scope — what "Game loop" covers inside Snake and Ladder and what it does not
  • Games and architecture patterns signal staff+ depth.
Waiting
InProgress
Finished
Turn-based games map cleanly to State pattern — one handler per game phase.

CampusOS context

CampusOS is the fictional smart-campus platform used across this track. Treat this module as a real product slice:

Context

  • Belongs to CampusOS — same naming and design vocabulary as parking, library, and booking modules
  • Scope is one JVM — persistence is in-memory or behind a repository interface
  • Goal is a class diagram + core Java that an interviewer can follow in 35–45 minutes
  • Extension paragraph at the end links to System Design when scale exceeds one process

Requirements snapshot

Functional requirements

  • Board with cells 1–100
  • Snakes move player down; ladders move up
  • Dice roll 1–6; move token accordingly
  • First to cell 100 wins
  • Multiple players take turns

Non-functional requirements

  • Single JVM, in-process design for this LLD article
  • Core flows testable with in-memory repositories
  • Extension points for new rules without editing central god classes
  • Clear public API on facade/service layer
  • CampusOS extension links to System Design when scale demands distribution

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 6 sections

  • Overview
  • Requirements
  • Board cells
  • Dice
  • Game loop
  • CampusOS extension

Test yourself

Answer these before moving on — recall is what makes it stick.