Loading...
Loading...
Browse 6 real-world technical and behavioral interview questions about Data engineering. Review scenarios, edge cases, and architectural best practices.
An authoritative discussion on Apache Iceberg's table format, focusing on hidden partitioning, the trade-offs of copy-on-write versus merge-on-read, and managing schema drift at scale. Use this data engineering answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects data lakes to the point an interviewer is testing.
An examination of decentralised data governance, exploring dynamic masking in the compute layer, deterministic tokenisation for referential integrity, and standardised tagging. Use this data engineering answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects data governance to the point an interviewer is testing.
An analysis of the architectural reality of exactly-once guarantees in Flink, from distributed snapshots to two-phase commits. Use this data engineering answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects streaming to the point an interviewer is testing.
An analysis of distributed processing bottlenecks, addressing the limitations of AQE, implementing manual key salting for shuffle optimization, and restructuring data layouts. Use this data engineering answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects batch processing to the point an interviewer is testing.
Designing a robust streaming architecture for embedding generation, detailing GPU adaptive batching, Kafka-driven backpressure management, and asynchronous HNSW indexing. Use this machine learning answer to show the decision, trade-off, and evidence rather than a memorised definition. It also connects data engineering to the point an interviewer is testing.
Rebuild a corrupted CQRS read model by replaying the event store into a fresh projection, applying upcasters for old event versions, validating parity, and cutting over with a blue-green deployment.