InterviewStack.io LogoInterviewStack.io

Batch and Stream Processing Questions

Covers design and implementation of data processing using batch, stream, or hybrid approaches. Candidates should be able to explain when to choose batch versus streaming based on latency, throughput, cost, data volume, and business requirements, and compare architectural patterns such as lambda and kappa. Core stream concepts include event time versus processing time, windowing strategies such as tumbling sliding and session windows, watermarks and late arrivals, event ordering and out of order data handling, stateful versus stateless processing, state management and checkpointing, and delivery semantics including exactly once and at least once. Also includes knowledge of streaming and batch engines and runtimes, connector patterns for sources and sinks, partitioning and scaling strategies, backpressure and flow control, idempotency and deduplication techniques, testing and replayability, monitoring and alerting, and integration with storage layers such as data lakes and data warehouses. Interview focus is on reasoning about correctness latency cost and operational complexity and on concrete architecture and tooling choices.

EasyTechnical
0 practiced
Explain the differences between batch processing and stream processing in production data platforms. Compare them across latency, throughput, cost, operational complexity, data volume, correctness, and typical use-cases. Give concrete examples of workloads that favor each approach and describe one scenario where a hybrid approach is appropriate.
MediumTechnical
0 practiced
Explain strategies for testing and replayability of streaming pipelines. Include local unit testing, integration tests, controlled replay of historical events for production jobs, and how to verify stateful operators after replay.
EasyTechnical
0 practiced
Explain what a watermark is in stream processing, how it's used to handle late-arriving data, and describe at least two strategies for dealing with late events (e.g., side outputs, retraction/updates, allowed-lateness). Provide an example policy for a source with occasional 10-minute delays.
EasyTechnical
0 practiced
List and compare common windowing strategies used in stream processing (tumbling, sliding, session). For each, describe typical use cases, configuration considerations (size, gap), and how they affect state size and latency.
HardSystem Design
0 practiced
Architect a solution to provide incrementally-updated, queryable materialized views derived from event streams for low-latency dashboards. Discuss how to maintain correctness, support rollbacks or re-compute, and keep these views in sync with the canonical event log.

Unlock Full Question Bank

Get access to hundreds of Batch and Stream Processing interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.