What experience do you have in data modeling, specifically regarding data breaks? Which recent project did you work on, what was your role, and can you give a brief overview?

In my most recent role at Acme Corp, I led the data modeling effort for a customer‑relationship management (CRM) system. The project involved consolidating data from three legacy systems, which caused frequent data breaks such as duplicate customer records and inconsistent address formats. I started by conducting a data audit to identify anomalies, then designed a unified entity‑relationship model that mapped each legacy source to a common schema. I defined primary keys, enforced referential integrity, and applied 3NF to eliminate transitive dependencies. During implementation, I worked closely with the ETL team to create transformation rules that resolved data breaks, such as deduplication logic and address standardization. The result was a clean, scalable database that reduced data errors by 85% and improved reporting accuracy. My role required strong analytical skills, stakeholder communication, and hands‑on SQL and modeling tool usage, demonstrating my ability to translate business requirements into robust data structures.