Design and implement an object-oriented music management player in Go. Requirements: represent Song, Playlist, and Player types; support adding/removing songs, reordering, and optional deduplication; support merging two playlists while preserving order and handling duplicates according to a policy you define; support playing a playlist with play, pause, next, previous, shuffle, and repeat; expose clear APIs and data structures and discuss their time/space complexity; consider concurrency for simultaneous edits and playback, thread safety, and persistence; and outline unit tests for core behaviors.

This question evaluates object-oriented system design, API and data-structure modeling, state and concurrency management, persistence considerations, and algorithmic time/space complexity within a Go-based music player domain.

How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a hard difficulty System Design question, commonly asked during Technical Screen rounds at Paramount Commerce.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Paramount Commerce during technical interviews.

Design a Go music player with playlists | Paramount Commerce Interview Question

Design and Implement an Object-Oriented Music Player in Go

You are asked to design and implement a small, object-oriented music management and playback system in Go.

Requirements

Core domain types:
- Song
- Playlist
- Player
Playlist features:
- Add/remove songs
- Reorder/move songs
- Optional deduplication toggle (prevent duplicate songs by ID)
Merging playlists:
- Merge two playlists while preserving the relative order of songs from each source
- Define and implement a duplicate-handling policy (e.g., keep-first, keep-last, keep-both)
Player controls and behavior:
- Play, pause, next, previous
- Shuffle
- Repeat modes (off, one, all)
Engineering aspects:
- Expose clear APIs and data structures
- Discuss time and space complexity of core operations
- Consider concurrency for simultaneous edits and playback; design for thread safety
- Consider persistence (saving/loading playlists)
- Outline unit tests for core behaviors

Assume a console-based player (no actual audio) where playback means managing state and current song position.

Requirements

Core domain types:

Song
Playlist
Player

Playlist features:

Add/remove songs
Reorder/move songs
Optional deduplication toggle (prevent duplicate songs by ID)

Merging playlists:

Merge two playlists while preserving the relative order of songs from each source
Define and implement a duplicate-handling policy (e.g., keep-first, keep-last, keep-both)

Player controls and behavior:

Play, pause, next, previous
Shuffle
Repeat modes (off, one, all)

Engineering aspects:

Expose clear APIs and data structures
Discuss time and space complexity of core operations
Consider concurrency for simultaneous edits and playback; design for thread safety
Consider persistence (saving/loading playlists)
Outline unit tests for core behaviors

Assume a console-based player (no actual audio) where playback means managing state and current song position.

Design a Go music player with playlists

Quick Overview

Design and Implement an Object-Oriented Music Player in Go

Requirements

Solution

Submit Your Answer to Earn 20XP

Design a Go music player with playlists

Quick Overview

Design and Implement an Object-Oriented Music Player in Go

Requirements

Solution

Submit Your Answer to Earn 20XP