Reviewed by Aditya Kumar · Last reviewed 2026-03-25
**Situation**: Ingestion job exceeds SLA; need to find and fix bottleneck. **Task**: Systematically isolate slow stage (source, transfer, or Spark). **Action**: (1) **Add timestamps**—log start/end per stage; identify largest delta. (2) **Spark UI**—Jobs/Stages: which stage...
This hard-level Spark/Big Data question appears frequently in data engineering interviews at companies like Swiggy. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (partition, spark) will help you answer variations of this question confidently.
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.
Situation: Ingestion job exceeds SLA; need to find and fix bottleneck.
Task: Systematically isolate slow stage (source, transfer, or Spark).
Action: (1) Add timestamps—log start/end per stage; identify largest delta. (2) Spark UI—Jobs/Stages: which stage dominates? Task duration histogram shows skew. (3) Source checks—DB: connection pool exhaustion? Network latency? Lock contention? (4) Sqoop/Kafka—Sqoop: --num-mappers, --fetch-size, --split-by. Kafka: consumer lag, partition count vs. parallelism. (5) Shuffle/GC—Spark metrics: shuffle read/write, GC time. (6) Sampling—Run on 1% sample to confirm if data-size related.
Result: Identified source DB as bottleneck; increased fetch-size and mappers within connection limit; 40% faster.
Cost Implications: Faster job = fewer cluster hours. Spark UI is free; distributed tracing adds minor overhead.
Pro-Move: 'We log stage durations to Datadog; alert when p99 exceeds baseline.' Red Flag: Optimizing without measuring—guessing shuffle when source is slow.
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 Spark/Big Data interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.