Airflow Interview Questions 2026
Published July 22, 2026 · Updated July 22, 2026
3 Airflow interview questions from General, Deloitte, Grab. All difficulty levels, all roles. Upvoted by engineers who were asked them.
3 questions
Companies: General, Deloitte, Grab
125 upvotes
Airflow Questions by Company
General (1)
General
Hard
Scenario round
5–8 YearsSnowflakePySparkAirflow
Design an end-to-end data pipeline using Python, PySpark, Snowflake, Airflow, and AWS S3. Explain data flow, orchestration, monitoring, and failure handling.
↑ 87 upvotes · 62 engineers asked this · Data Engineer
Deloitte (1)
Deloitte
Medium
Technical round
2-6 yearsAirflow
A single Airflow DAG has grown to 40 tasks and is hard to reason about or debug. What signs indicate it should be split into multiple DAGs, and how would you handle dependencies between them?
↑ 18 upvotes · 9 engineers asked this · Data Engineer
Grab (1)
Grab
Medium
Technical round
2-6 yearsAirflow
Your Airflow DAG needs to process each day's ride data only after all regional data files for that day have landed, but files can arrive up to 6 hours late from some regions. How would you design the trigger logic?
↑ 20 upvotes · 11 engineers asked this · Data Engineer
Practice these questions with AI feedback
Get instant grading on your answers, identify your weak areas, and generate a personalised 14-day study plan — all free.
Build my study plan →
Frequently asked questions
Design an end-to-end data pipeline using Python, PySpark, Snowflake, Airflow, and AWS S3. Explain data flow, orchestration, monitoring, and failure handling.
Design an end-to-end data pipeline using Python, PySpark, Snowflake, Airflow, and AWS S3. Explain data flow, orchestration, monitoring, and failure handling.
A single Airflow DAG has grown to 40 tasks and is hard to reason about or debug. What signs indicate it should be split into multiple DAGs, and how would you handle dependencies between them?
A single Airflow DAG has grown to 40 tasks and is hard to reason about or debug. What signs indicate it should be split into multiple DAGs, and how would you handle dependencies between them?
Your Airflow DAG needs to process each day's ride data only after all regional data files for that day have landed, but files can arrive up to 6 hours late from some regions. How would you design the trigger logic?
Your Airflow DAG needs to process each day's ride data only after all regional data files for that day have landed, but files can arrive up to 6 hours late from some regions. How would you design the trigger logic?