# Platform Engineering Fundamentals
All Platform Engineering Fundamentals notes →1 — The Evolution of Infrastructure Engineering
Traces infrastructure engineering from physical servers through virtualization, the rise of cloud computing, and infrastructure automation to the point where platform engineering became necessary.
2 — From System Administration to Platform Engineering
Contrasts traditional system administration with the DevOps revolution, cloud-native transformation, and the modern platform team model that emerged from both.
3 — DevOps, SRE, and Platform Engineering
Separates what DevOps, SRE, and Platform Engineering each solve, where their responsibilities and boundaries lie, and how the three disciplines work together in practice.
4 — Why Platform Engineering Exists
Grounds platform engineering's existence in scaling engineering organizations, reducing developer cognitive load, increasing velocity, and balancing standardization against flexibility.
5 — The Evolution of Developer Experience (DevEx)
Follows developer experience (DevEx) from early pain points through self-service engineering, the developer journey, and how developer happiness gets measured.
1 — Conway's Law
How Conway's Law ties software architecture to organizational communication structure, and what that implies for platform team boundaries.
2 — Team Topologies
Introduces the four fundamental team types from Team Topologies — stream-aligned, platform, enabling, and complicated-subsystem — and their interaction modes.
3 — Cognitive Load
Defines the types of cognitive load a platform absorbs on behalf of stream-aligned teams, and how a platform's scope should be sized against it.
4 — Platform Teams
Covers a platform team's mission, responsibilities, composition, and the criteria used to judge whether it's succeeding.
1 — Platform as a Product
Frames an internal platform as a product with real users, not an internal utility — the shift in mindset that separates platform engineering from traditional infrastructure teams.
2 — Product Management for Platforms
Applies product management discipline — understanding users, running user research, building roadmaps, and prioritizing features — to an internal platform.
3 — Developer Experience (DevEx)
Covers user-centered design, developer workflows, platform usability, and the feedback loops that keep a platform's DevEx honest.
4 — Platform Adoption
Covers adoption strategy, removing friction from onboarding, building developer trust, and the continuous improvement loop that sustains adoption.
1 — Self-Service Platforms
Why self-service matters, what developer independence looks like in practice, and how service provisioning and self-service workflows get designed.
2 — Golden Paths
Defines golden paths, their benefits, what a standardized workflow looks like, and how to balance a golden path against the flexibility teams still need.
3 — Internal Developer Platforms (Introduction)
Introduces what an Internal Developer Platform is, its core components, the capabilities it exposes, and who its consumers are.
4 — APIs Everywhere
Covers API-first platform design across platform APIs, infrastructure APIs, and service APIs.
5 — Automation First
Covers eliminating manual operations through infrastructure automation, workflow automation, and event-driven automation.
6 — Standardization
Covers platform standards, engineering standards, reusable building blocks, and governance enforced through standardization.
7 — Opinionated Platforms
Why opinionated platforms outperform unopinionated ones — guardrails versus restrictions, sensible defaults, and convention over configuration.
1 — Abstraction
How abstraction hides complexity behind platform interfaces, and the layers of abstraction a platform typically exposes.
2 — Composability
Covers modular platform design, reusable building blocks, and composable services as a platform design principle.
3 — Scalability
Covers organizational and technical scalability, and how a platform is expected to grow with the organization it serves.
4 — Reliability by Design
Covers designing for failure, platform resilience, and the reliability principles a platform bakes in by default.
5 — Security by Default
Covers secure defaults, least privilege, and security built into the platform rather than bolted on afterward.
1 — Discover
Covers understanding user needs, platform research, identifying pain points, and defining success criteria before building anything.
2 — Design
Covers platform vision, platform architecture, user experience design, and platform interface design.
3 — Build
Covers delivering platform capabilities through automation, APIs, and platform components.
4 — Operate
Covers day-2 operations, platform reliability, support models, and operational excellence.
5 — Measure
Covers platform KPIs, adoption metrics, reliability metrics, and productivity metrics.
6 — Improve
Covers feedback loops, product iteration, continuous improvement, and platform evolution.
1 — Developer Productivity
Covers flow efficiency, lead time, deployment frequency, and time to first deployment as developer productivity signals.
2 — DORA Metrics
Covers the four DORA metrics, their known limitations, and how to read them from a platform team's perspective.
3 — SPACE Framework
Covers the SPACE framework's five dimensions — satisfaction, performance, activity, communication, and efficiency.
4 — Platform KPIs
Covers platform-specific KPIs: platform adoption, self-service success rate, platform reliability, and operational efficiency.
1 — Ticket-Driven Platforms
Why routing every platform request through a ticket queue defeats the self-service premise a platform is supposed to deliver.
2 — Platform as an Operations Team
Why a platform team that only reacts to operational tickets has become an ops team wearing a platform label.
3 — Building Technology Instead of Products
Why building infrastructure tooling without product discipline produces technology nobody adopts.
4 — Excessive Standardization
Why over-standardizing every workflow trades away the flexibility teams need to ship.
5 — Platform Monoliths
Why an unbounded, tightly-coupled platform becomes as hard to change as the monolith it replaced.
6 — Ignoring Developer Experience
Why treating developer experience as an afterthought quietly kills platform adoption.
7 — Low Platform Adoption
Diagnosing why a platform sees low adoption despite real investment, and what usually causes it.
1 — Scaling Platform Teams
Covers organizational growth, multi-team collaboration, and platform ownership models as a platform org scales.
2 — Platform Governance
Covers platform standards, policies, compliance, and the decision frameworks that govern a platform at enterprise scale.
3 — Platform Maturity Models
Covers the crawl/walk/run maturity stages and continuous evolution of a platform engineering practice.
4 — Building a Platform Engineering Culture
Covers engineering excellence, shared responsibility, continuous learning, and building platform communities.
1 — Platform Engineering Fundamentals Interview Questions
A working set of fundamentals-level platform engineering interview questions and how to structure the answers.
2 — Architecture Trade-Off Discussions
Framing for architecture trade-off discussions specific to platform engineering interviews.
3 — Platform Design Case Studies
Worked platform design case studies in the style MAANG system-design interviews expect.
4 — Common Staff/Principal Platform Engineering Questions
Common Staff/Principal-level platform engineering interview questions and what differentiates a strong answer at that level.
5 — Whiteboard Exercises
Whiteboard exercises for practicing platform design live, under interview conditions.
6 — Platform Engineering Interview Cheat Sheet
A condensed cheat sheet for last-mile review before a platform engineering interview.
1 — Platform Engineering Glossary
A glossary of platform engineering terminology used throughout this book.
2 — Team Topologies Reference
A quick reference for the Team Topologies team types and interaction modes.
3 — Platform Principles Cheat Sheet
A cheat sheet condensing this book's platform design principles into a single reference.
4 — DORA & SPACE Metrics Quick Reference
A quick reference for the DORA metrics and SPACE framework dimensions covered in Part VII.
5 — Platform Maturity Assessment
A self-assessment for gauging a platform's maturity stage.
6 — Recommended Reading & Research Papers
Recommended reading and research papers for going deeper on platform engineering.
Platform Engineering Fundamentals
A book-shaped table of contents for platform engineering fundamentals: evolution and organizational foundations, platform-as-a-product thinking, core principles (self-service, golden paths, automation, APIs), design principles, the platform lifecycle, DORA/SPACE metrics, anti-patterns, enterprise governance, and MAANG interview prep — cross-linking existing sre/patterns/observability/projects notes instead of duplicating them.