Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Situation:** Stakeholders requested real-time dashboards with sub-second latency on top of our batch-oriented data warehouse. Initial ask was "make it real-time." **Task:** Assess feasibility, cost, and alternatives—then push back constructively if the ask was misaligned with...
This hard-level Behavioral question appears frequently in data engineering interviews at companies like Accenture. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (spark) will help you answer variations of this question confidently.
This is a senior-level question that tests architectural thinking. Lead with the high-level design, then drill into specifics. Discuss trade-offs explicitly - there is rarely one correct answer. Show awareness of scale, fault tolerance, and operational complexity.
Situation: Stakeholders requested real-time dashboards with sub-second latency on top of our batch-oriented data warehouse. Initial ask was "make it real-time."
Task: Assess feasibility, cost, and alternatives—then push back constructively if the ask was misaligned with value and budget.
Action: (1) I analyzed cost and complexity: real-time would require Kafka, streaming infrastructure, new monitoring, and likely 3–4 months of work. Estimated 5x TCO vs. current batch. (2) I interviewed stakeholders to understand the actual need: "What decisions would change if data was 15 minutes vs. 1 second old?" Most use cases were operational, not algorithmic. (3) I proposed a compromise: micro-batch every 15 minutes using our existing Spark stack—delivering ~90% of value at ~20% of cost. (4) I documented trade-offs (latency vs. cost vs. complexity) in a one-pager and shared prototypes. (5) I presented options: real-time (5x cost), micro-batch (recommended), or keep batch (no change).
Result: Stakeholders chose micro-batch after seeing prototypes. Delivered in 3 weeks. Transparent framing of trade-offs built trust; they’ve since asked for similar analysis on other requests.
Leadership takeaway: Push back with data, alternatives, and clarity on trade-offs—not with "that’s too hard" or "we can’t."
Pro-Move: Show you discovered the real need (e.g., "What decisions would change?") before pushing back. Red Flag: Pushing back without proposing alternatives or quantifying impact—comes across as obstructionist.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked Behavioral interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.