Medium
Shopify

Design a Rare Book Condition Management System Object-Oriented Design Interview

Model the core domain objects for tracking physical condition assessments of rare library books, with immutable scan history and structured condition report generation.

1. Problem Statement

Design an in-memory system for a library to manage the physical condition of rare books. Librarians register condition scans for each book, and curators can request a structured condition report. Start by clarifying the scope and key objects.

2. Live Coding Format

Work in the provided coding workspace while explaining your decisions to the live interviewer. Validation may use inline tests, examples, comments, or a verbal walkthrough.

3. Key Focus Areas

  • 1
    Book and ConditionScan entity responsibilities
  • 2
    Immutable scan history and audit trail integrity
  • 3
    ConditionReport contract: comparison, trend, and summary generation
  • 4
    AssessmentStrategy interface for extensible scoring
  • 5
    Repository and service boundary separation

4. What Strong Candidates Should Demonstrate

  • Model Book and ConditionScan as distinct domain entities with clear ownership.
  • Enforce immutability on the scan history so the audit trail cannot be altered.
  • Design a ConditionReport as a derived, read-only view over the scan history.
  • Abstract assessment scoring behind a strategy interface for extensibility.
  • Write handwritten tests for scan registration, report generation, and extension scenarios.

Want interactive feedback?

Practice this problem in the live coding workspace while the interviewer probes your clarification, implementation, trade-offs, and validation.

Continue to Dashboard

Core Concepts

Object-Oriented DesignImmutable HistoryStrategy PatternDomain Modeling

Continue preparing

Build a complete software engineer mock interview plan

Related Object-Oriented Design

Design a Car Rental System

Design a car rental domain model covering vehicle categories and vehicles, branches, customers and drivers, a rental date range, rate-based quotes, reservations, pickup rental agreements, and return inspection with extra charges — preventing overlapping rentals of the same vehicle.

Related Object-Oriented Design

Design a Library Management System

Design a library that models catalog titles versus physical copies, members and librarians, checkout/return/renew/reserve flows with loan due dates, an overdue fine policy, and notifications as a boundary.

Related Object-Oriented Design

Design a Question and Answer Platform

Design a Q&A platform domain model with users, questions, answers, comments, tags, votes, an accepted-answer rule, and a reputation policy, with the voting, acceptance, and reputation invariants enforced in the model.

Related Object-Oriented Design

Design a Restaurant Management System

Design a restaurant domain model covering tables and capacity, reservations for time slots, seated parties, a menu, orders with priced line items, kitchen status, and bills with payments, keeping booking and order/kitchen state transitions correct.