Recommended Reading Order

Instead of reading all 12 books sequentially, I’d recommend this path:

Foundation

1. Platform Engineering Fundamentals
2. Infrastructure Platform Engineering
3. Kubernetes Platform Engineering
4. CI/CD Platform Engineering

Core Platform

5. Internal Developer Platforms
6. Observability Platform Engineering
7. Platform Security Engineering
8. Reliability Engineering

Senior/Staff Level

9. Platform Architecture
10. Platform Operations
11. Platform Product Management
12. Advanced Platform Engineering

Platform Engineering Fundamentals

Building the Mental Model for Modern Platform Engineering

Goal: Build a strong conceptual foundation in Platform Engineering before learning Internal Developer Platforms (IDPs), Kubernetes platforms, Infrastructure Platforms, and Platform Operations. This book focuses on the why, what, and principles of Platform Engineering rather than implementation details. See SRE for the build-it-and-operate-it layer this book is the conceptual prerequisite to.

If this were a book, this page is the table of contents. Each Part below is a chapter; each chapter links out to the concepts, designs, and platform notes that already exist elsewhere in this wiki instead of duplicating them. Unwritten chapters are listed with a — _(stub)_ marker, not empty files.

Parts

00 — The Evolution of Platform Engineering

The mental models that separate platform engineering from what came before it: the infrastructure eras that preceded it, the SysAdmin → DevOps → Platform Engineering lineage, and the forces (org scale, cognitive load, velocity) that made a dedicated platform team a good bet. See also DevOps vs. SRE vs. Platform Engineering in the SRE book for that book’s treatment of the same boundary question.

• 1 — The Evolution of Infrastructure Engineering — (stub)
• 2 — From System Administration to Platform Engineering — (stub)
• 3 — DevOps, SRE, and Platform Engineering — (stub)
• 4 — Why Platform Engineering Exists — (stub)
• 5 — The Evolution of Developer Experience (DevEx) — (stub)

01 — Organizational Foundations

The organizational theory a platform team’s shape has to answer to — Conway’s Law, Team Topologies, and cognitive load — before any platform capability gets designed. See also Conway’s Law and Team Topologies in the Patterns book for the pattern-level treatment of the same organizational theory.

• 1 — Conway’s Law — (stub)
• 2 — Team Topologies — (stub)
• 3 — Cognitive Load — (stub)
• 4 — Platform Teams — (stub)

02 — Platform as a Product

Treats the internal platform as a product with real users — product thinking, user research, roadmaps, and adoption strategy — rather than a shared-infrastructure team with a mandate.

• 1 — Platform as a Product — (stub)
• 2 — Product Management for Platforms — (stub)
• 3 — Developer Experience (DevEx) — (stub)
• 4 — Platform Adoption — (stub)

03 — Core Platform Principles

The recurring principles a platform is built around: self-service, golden paths, the Internal Developer Platform shape, API-first design, automation, standardization, and opinionation. See also the SRE book’s own Platform Engineering section — Self-Service Infrastructure, Golden Paths, and Internal Developer Platforms — for the build-it-and-run-it layer these principles inform.

• 1 — Self-Service Platforms — (stub)
• 2 — Golden Paths — (stub)
• 3 — Internal Developer Platforms (Introduction) — (stub)
• 4 — APIs Everywhere — (stub)
• 5 — Automation First — (stub)
• 6 — Standardization — (stub)
• 7 — Opinionated Platforms — (stub)

04 — Platform Design Principles

The cross-cutting design principles — abstraction, composability, scalability, reliability, security — that every platform capability gets evaluated against before it ships.

• 1 — Abstraction — (stub)
• 2 — Composability — (stub)
• 3 — Scalability — (stub)
• 4 — Reliability by Design — (stub). See also SLOs and Error Budgets for the operational mechanics behind reliability targets.
• 5 — Security by Default — (stub)

05 — The Platform Engineering Lifecycle

The full platform lifecycle a capability moves through: Discover, Design, Build, Operate, Measure, Improve.

• 1 — Discover — (stub)
• 2 — Design — (stub)
• 3 — Build — (stub)
• 4 — Operate — (stub)
• 5 — Measure — (stub)
• 6 — Improve — (stub)

06 — Measuring Platform Success

How platform success gets measured — developer productivity signals, the DORA metrics, the SPACE framework, and platform-specific KPIs. No existing note in this wiki covers DORA or SPACE yet — this Part is their canonical home.

• 1 — Developer Productivity — (stub)
• 2 — DORA Metrics — (stub)
• 3 — SPACE Framework — (stub)
• 4 — Platform KPIs — (stub)

07 — Platform Anti-Patterns

The recurring ways a platform initiative fails even with real investment behind it — patterns worth recognizing early, not fixing after adoption has already stalled.

• 1 — Ticket-Driven Platforms — (stub)
• 2 — Platform as an Operations Team — (stub)
• 3 — Building Technology Instead of Products — (stub)
• 4 — Excessive Standardization — (stub)
• 5 — Platform Monoliths — (stub)
• 6 — Ignoring Developer Experience — (stub)
• 7 — Low Platform Adoption — (stub)

08 — Enterprise Platform Engineering

Platform engineering at enterprise scale: scaling the team itself, governance, maturity models, and the culture that sustains a platform practice long-term. See also the ShipSolid platform project’s Platform & Cloud Maturity Model for a concrete, real-world maturity assessment.

• 1 — Scaling Platform Teams — (stub)
• 2 — Platform Governance — (stub)
• 3 — Platform Maturity Models — (stub)
• 4 — Building a Platform Engineering Culture — (stub)

09 — Platform Engineering Interview Preparation (MAANG)

Interview preparation specific to platform engineering roles at the Staff/Principal (L6/L7) level — fundamentals questions, trade-off discussions, design case studies, and whiteboard practice.

• 1 — Platform Engineering Fundamentals Interview Questions — (stub)
• 2 — Architecture Trade-Off Discussions — (stub)
• 3 — Platform Design Case Studies — (stub)
• 4 — Common Staff/Principal Platform Engineering Questions — (stub)
• 5 — Whiteboard Exercises — (stub)
• 6 — Platform Engineering Interview Cheat Sheet — (stub)

10 — Appendices

Reference material — glossary, cheat sheets, and further reading — for quick lookup after working through the book.

• 1 — Platform Engineering Glossary — (stub)
• 2 — Team Topologies Reference — (stub)
• 3 — Platform Principles Cheat Sheet — (stub)
• 4 — DORA & SPACE Metrics Quick Reference — (stub)
• 5 — Platform Maturity Assessment — (stub)
• 6 — Recommended Reading & Research Papers — (stub)

Learning Outcomes

After completing this book, you will be able to:

• Explain the evolution from SysAdmin → DevOps → SRE → Platform Engineering.
• Distinguish the responsibilities and interactions of Platform Engineering, DevOps, and SRE.
• Apply Team Topologies, Conway’s Law, and Cognitive Load Theory to platform organization design.
• Think of an internal platform as a product with users, roadmaps, metrics, and adoption strategies.
• Design platforms around self-service, golden paths, automation, APIs, and standardization.
• Understand the complete platform lifecycle: Discover → Design → Build → Operate → Measure → Improve.
• Evaluate platform success using DORA, SPACE, platform KPIs, and adoption metrics.
• Identify common platform engineering anti-patterns and avoid them.
• Build the conceptual foundation required for the remaining books in the Platform Engineering series and for MAANG Staff/Principal (L6/L7) platform engineering interviews.

Metadata

Author	Amit Singh
Scope	platform-engineering-fundamentals