Not a brutal problem but OOD always trips me up a little because there's no single right answer and I never know how deep to go on the class hierarchy.
Start by clarifying functional and non-functional requirements, then design a layered object-oriented model with clear abstractions for files, storage, and metadata. Focus on extensibility and trade-offs, especially for ML workloads like feature stores or model artifact management.
Pro tip: Emphasize how your design supports ML-specific needs such as versioning, large file handling, and efficient similarity search, while keeping the core file system abstractions clean and reusable.
Ask questions to understand expected scale, file types, access patterns, consistency needs, and ML-specific use cases like model versioning or feature retrieval.
Identify key objects such as File, Directory, StorageBackend, MetadataStore, and AccessControl, and define their responsibilities and relationships.
Choose appropriate data structures and algorithms for storing file content and metadata, and for efficient lookup by path, ID, or content similarity.
Discuss partitioning, caching, replication, and consistency models, and explain trade-offs between latency, throughput, and cost.
Show how the design can be extended to support ML-specific features like versioned model artifacts, feature stores, and embedding-based search.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.