Essential cookies keep authentication working. With your permission, we also use analytics cookies to understand and improve the product. Read our Privacy Policy

DataEngPrep.tech
QuestionsPracticeAI CoachDashboardPricingBlog
ProLogin
Home/Questions/Behavioral/Discuss a time you had to push back on a requirement.

Discuss a time you had to push back on a requirement.

Behavioralhard0.5 min read

Reviewed by Aditya Kumar · Last reviewed 2026-03-24

Situation: Stakeholders requested real-time dashboards with sub-second latency on a batch-oriented warehouse. Task: Manage expectations and deliver value without over-investing. Action: I analyzed cost and complexity—real-time would require Kafka, streaming infra, and...

🤖 Analyze Your Answer
Frequency
Low
Asked at 1 company
Category
144
questions in Behavioral
Difficulty Split
100E|18M|26H
in this category
Total Bank
1,863
across 7 categories
Asked at these companies
Verizon
Key Concepts Tested
spark

Why This Question Matters

This hard-level Behavioral question appears frequently in data engineering interviews at companies like Verizon. 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.

How to Approach This

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.

Expert Answer
100 words

Situation: Stakeholders requested real-time dashboards with sub-second latency on a batch-oriented warehouse. Task: Manage expectations and deliver value without over-investing. Action: I analyzed cost and complexity—real-time would require Kafka, streaming infra, and significant new headcount. I proposed a compromise: micro-batch every 15 minutes with the existing Spark stack, delivering ~90% of value at ~20% of cost. I documented trade-offs (freshness vs. cost) and built a prototype to validate. Result: We implemented micro-batch; stakeholders accepted after seeing the prototype. Trust improved; we avoided a costly rebuild. Lesson: Push back with data; propose alternatives that meet core needs. Transparent communication builds trust.

⚡
Pro Tip

Red Flag: 'I told them no.' Pro-Move: 'I proposed micro-batch at 90% value and 20% cost'—quantified trade-offs and alternatives. Shows cost awareness and business alignment.

Want all answers as a PDF for offline study?
Seven focused volumes with 750+ in-depth answers — Answer Vault →

Related Behavioral Questions

hardTell me about yourself and your experience.FreeeasyTell me about your family backgroundFreeeasyWhat are your salary expectations for this role?FreeeasyWhere do you see yourself in your career five years from now?FreehardBriefly introduce yourself and walk us through your journey as a Data Engineer so far.Free

Level up your prep

Recommended
Educative
Educative Unlimited

800+ hands-on courses — Grokking System Design, Coding Patterns, and AI mock interviews for your DE loop.

Start learning →

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.

← Back to all questionsMore Behavioral questions →
Categories
All QuestionsSQLSpark / Big DataPython / CodingSystem DesignCloud / ToolsBehavioral
By Company
AmazonGoogleDatabricksSnowflakeAWSAzureMicrosoftNetflixUberTCS
Interview Guides
All GuidesTop SQL QuestionsTop Spark QuestionsPySpark QuestionsTop Python QuestionsTop System DesignKafka QuestionsAirflow QuestionsSQL Window FunctionsETL QuestionsData Modeling
Products
AI Interview CoachAnswer AnalyzerSQL PlaygroundResume AnalyzerAnswer Vault PDFsPricing
Company
About & Editorial PolicyContact UsAI DisclosureDisclaimerTerms of ServicePrivacy Policy
© 2026 DataEngPrep.tech. All rights reserved.
AboutBlogContactDisclaimer