D8Loop · Field notes
Read the concepts, patterns, and interview signals behind every module — eight knowledge bases, read like an archive. Scroll to move through them; jump from the index on the left.
Grain, keys, ownership, and governance decisions that make data products durable instead of merely diagrammed.
Ingestion, orchestration, lakehouse choices, streaming edges, and failure paths for systems that must be operated.
Spark internals interviews actually probe: jobs, stages, and tasks; shuffles and skew; partitioning, caching, joins, and the memory model.
Relational thinking, analytical query patterns, and the habit of explaining results before optimizing syntax.
Transformation code that stays legible under messy inputs, edge cases, and interviewer follow-up questions.
Scheduling semantics that trip everyone up, DAGs that survive review, and the concurrency, executor, and failure-mode decisions that separate a scheduled script from an orchestrated system.
Models, refs, and materializations; tests, contracts, and lineage — the transformation layer most warehouses are actually built on, and the half of the stack Airflow triggers.
A drilled bank of the questions data engineers actually get across SQL, Python, Spark, modeling, and design — with the reasoning each answer should show.
End-to-end builds that double as portfolio proof: ingestion, transformation, orchestration, and serving on realistic datasets and stacks.