**Situation**: Complex platforms have multiple stakeholders, ambiguous scope. **Action**: (1) Stakeholder workshops—personas, use cases, success metrics; (2) Data discovery—sources, volume, quality, latency; (3) Gap analysis—current vs. desired; (4) Prioritization—MoSCoW or...
Pro-Move: 'We run discovery sprints before design—uncovered 3 undocumented sources that changed the architecture.'
This easy-level System Design/Architecture question appears frequently in data engineering interviews at companies like BCG. While less common, it tests deeper understanding that distinguishes strong candidates.
Start by clearly defining the core concept being asked about. Interviewers want to see that you understand the fundamentals before diving into implementation details. Structure your answer with a definition, then explain the practical application with a concise example.
Situation: Complex platforms have multiple stakeholders, ambiguous scope.
Action: (1) Stakeholder workshops—personas, use cases, success metrics; (2) Data discovery—sources, volume, quality, latency; (3) Gap analysis—current vs. desired; (4) Prioritization—MoSCoW or RICE; (5) PRD—scope, assumptions, acceptance criteria.
BCG Style: Align with business strategy; quantify impact. Iterative refinement—prototype early, validate. Define MVP and iterate.
Want feedback on your answer?
Paste your answer to this question and our AI Coach scores it, finds gaps, and shows you the FAANG-level version.
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer — FreeAccording to DataEngPrep.tech, this is one of the most frequently asked System Design/Architecture interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.