Scalable data models matter because query patterns, storage growth, and pipeline complexity all change as Salesforce data volume increases. A model that works for a small reporting use case can become slow, expensive, and hard to maintain at larger scale.
You are asked to explain how you ensure a PostgreSQL data model remains scalable when ingesting and serving Salesforce data such as account, opportunity, and activity records. Describe how you decide between normalized operational models and analytics-friendly dimensional models, how you use indexes and partitioning, and how you prevent common performance and data integrity issues as volume grows.
The interviewer expects a practical design discussion rather than abstract theory. You should cover schema design choices, query access patterns, growth planning, and trade-offs between write efficiency, read efficiency, and maintainability. It is also useful to mention what you would monitor or revisit as usage changes.