Skip to content
RED SAGSkills
mediumData Engineer interview question

Your main nightly Airflow DAG failed at 3 a.m. and dashboards are due at 8 a.m. Walk me through how you handle it.

What the interviewer wants to hear

  • Check the failed task logs and identify the root cause first
  • Tell stakeholders early about the delay and impact
  • Fix or work around the cause, then clear and rerun from the failed task
  • Rely on idempotent tasks so reruns do not duplicate data
  • Validate the output with row counts and quality checks before announcing
  • Write a short post-mortem and add alerts or tests to prevent a repeat

Model answer

First I open the failed task in the Airflow UI and read its logs to find the real cause: a source outage, a schema change, bad data, credentials or resources. If the 8 a.m. deadline is at risk, I post early in the data channel saying which dashboards are affected and when I expect an update. Then I fix the cause, for example by adjusting a query for a renamed column or waiting for the source to recover, and clear the failed task so it and its downstream tasks rerun. Our tasks overwrite their date partition or MERGE on a key, so reruns are safe. Before saying it is fixed, I check row counts, freshness and key metrics against previous days. Afterwards I write a brief post-mortem and add whatever was missing, like a contract test, a source freshness alert or retries for transient errors.

Can you answer it under time pressure?

Take a timed medium round and get scored on every answer.

Start mock interview

More medium Data Engineer questions