Related Object-Oriented Design
Design a Multi-Elevator Dispatch System
Design a controller for multiple elevators that accepts hall and cabin requests, schedules cars, models movement and doors safely, and supports replaceable dispatch policies.
1. Problem Statement
Design a platform that scores a limited-overs cricket match ball by ball and produces batting and bowling scorecards. Cover teams and players, the match and its innings, overs and deliveries, extras and wickets, and how the match result is decided. State your assumptions about format and rules. Start by clarifying scope and the core 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
- 1Delivery modeling: legal balls, extras, and credited runs
- 2Over completion (6 legal balls) and innings-ending conditions
- 3Striker rotation on odd runs and at over end
- 4Scorecards consistent with the deliveries, and the target/chase result
4. What Strong Candidates Should Demonstrate
- Model teams, players, match, innings, overs, and deliveries with clear ownership.
- Account for legal vs. illegal deliveries and extras correctly.
- Implement striker rotation and over completion rules.
- Keep batting and bowling scorecards consistent with the recorded deliveries and compute match results.
Want interactive feedback?
Practice this problem in the live coding workspace while the interviewer probes your clarification, implementation, trade-offs, and validation.
Continue to DashboardCore Concepts
Hidden because they name the technique, which a real interviewer would not tell you.
Show core concepts
Object-Oriented DesignDomain ModelingState ModelingRule Validation
Continue preparing
Build a complete software engineer mock interview plan
Related Object-Oriented Design
Design an Online Stock Brokerage System
Design a brokerage domain model covering accounts and portfolios, instruments, a cash ledger, market and limit orders, immutable fills, derived positions, order state transitions, and an external exchange gateway boundary — without building a matching engine.
Related Object-Oriented Design
Design a Two-Player Chess Game Engine
Design a chess engine that models a board and pieces, validates legal turns and moves, records move history, and detects check, checkmate, stalemate, resignation, and forfeit.
Related Object-Oriented Design
Design a Group Expense-Splitting Ledger
Design a system where users form groups, log shared expenses split equally, by exact amounts, or by percentage, maintain pairwise balances, and settle debts.