Part VIII — Synthesis
Chapters 38–40
Three chapters: one to finish the platform, one to get the job, one to build the career.
Chapter 38 is the capstone, and it is the point of the whole book. Everything built across the previous thirty-seven chapters gets assembled, run end to end, tested, documented, and — the part that matters — reconciled to the source.
The acceptance criterion was stated in Chapter 1 §1.7 and has not changed:
For any calendar month, total net revenue computed from the gold layer equals total net revenue computed directly from the source database, to the cent — and every difference is explained by a documented, tested rule rather than discovered after the fact.
You compute that reconciliation. The figures do not appear anywhere in Chapters 1–37, and the book's build validator enforces it, because a result you read is not a result you have verified. This is a deliberate design: the difference between finishing a tutorial and finishing an engineering project is that at the end of the second one, you are the person who knows whether the number is right.
Chapter 39 is the interview. System design, coding, SQL, and the behavioral questions, with worked answers and the reasoning behind what interviewers are actually testing. Data engineering interviews have a distinctive shape — heavier on system design and SQL than a general software interview, lighter on algorithms — and the shape is learnable. The chapter includes the questions you should ask them, which is how you avoid a job titled "data engineer" that is actually dashboard maintenance.
Chapter 40 is the career: junior to staff, the specialization tracks (streaming, platform, analytics engineering, ML infrastructure, governance), what changes at each level, how to tell a healthy data team from an unhealthy one from the outside, the failure modes that make people leave the field, and how to stay current in a discipline whose tools turn over every five years without chasing every new one.
What you will have when you finish: a complete, running, tested, documented data platform in a repository you own, that reconciles to its source, with a cost model and a runbook. That artifact is worth more in an interview than any certification, and Chapter 39 tells you exactly how to present it.
The single idea to carry out of the whole book: you are the reason a number on a screen means what someone thinks it means. Nearly nobody downstream is in a position to check. That is not plumbing — it is custody, and the practices in this book are what taking it seriously looks like.