Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Situation:** My manager wanted to build a custom scheduling solution instead of adopting Airflow. I believed Airflow would be faster to implement and easier to maintain. **Task:** Advocate for my view without undermining their authority or damaging trust, and support the...
This easy-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 (airflow) will help you answer variations of this question confidently.
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: My manager wanted to build a custom scheduling solution instead of adopting Airflow. I believed Airflow would be faster to implement and easier to maintain.
Task: Advocate for my view without undermining their authority or damaging trust, and support the final decision once made.
Action: (1) I requested a 1:1 to discuss—not in a group where it could feel confrontational. (2) I listened to their rationale (control, no vendor dependency, internal expertise). (3) I shared my perspective with evidence: "If we build custom, we gain X but take on Y (maintenance, hiring). If we use Airflow, we get Z (ecosystem, community) but lose W (vendor dependency)." (4) I proposed a lightweight benchmark: implement a representative DAG in both approaches and compare dev time, operational overhead, and extensibility. (5) After the benchmark showed Airflow was 2 months faster to a production-ready state, they agreed to adopt it. (6) When they’ve made decisions differently, I’ve supported them and documented the rationale for future reference.
Result: We adopted Airflow and saved ~2 months of dev time. Our working relationship stayed strong because the discussion was evidence-based and respectful.
Leadership takeaway: Frame disagreements as trade-offs, not right vs. wrong. Use data when possible. Once a decision is made, commit to it.
Pro-Move: Show you proposed a benchmark or pilot and that you support the final decision even when it differs from your view. Red Flag: Implying you were "right" and the manager "finally saw reason," or going around them to others.
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.