**Flow:** GET API (paginate if needed) → write to S3/GCS (path: prefix/YYYY/MM/DD/file.json). Schedule via cron or Airflow. Use idempotent path (date-based) for reruns.
**Production:** Retries with backoff. Pagination for large APIs. Incremental: pass since/date param. Secrets from env or secrets manager. Log response size, row count....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like Swiggy. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Python/Coding interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.