Whenever you're ready, walk me through how you'd approach this.
Design a phonebook that stores names, address, and phone numbers with Add/Delete/Search/Modify; multiple addresses and phone numbers per name are allowed.
Asked in the Onsite design stage. Treat this as a practical API and data-modeling exercise. Explain the core entities, operation semantics, lookup structures, validation, and consistency behavior. Since this is fundamentally a deterministic lookup system, discuss why machine learning is unnecessary unless search ranking or duplicate detection becomes a later requirement.