Internal Developer Platform
Building the platform your developers actually use: where to draw the abstraction line and what leaks through it, golden paths and the fleet of services they generate, a service catalog that stays true, self-service infrastructure with quota and policy at the request, versioning a platform API two hundred services depend on, and measuring adoption honestly. Lifetime updates included.
What you'll learn
Curriculum
9 modules · 35 lessonsThe Platform Is a Product
Why a platform becomes necessary, what developers actually want from it, and the ways it fails to be adopted.
Where the Abstraction Line Goes
The central design decision: how much to hide, what leaks anyway, and what it costs when it does.
Golden Paths
The supported way to build a service, and the fleet of services that way produces.
The Service Catalog
Knowing what exists, who owns it, and what depends on it, accurately enough to act on.
Self-Service Infrastructure
Turning a ticket into an API call, and the guardrails that make that safe.
Environments and Tenancy
What a team gets, what it can see, and how teams stay out of the way of other teams.
The Platform API and Its Versions
The interface developers write against, and changing it after everyone depends on it.
Measuring and Operating the Platform
Whether the platform is working, and what happens when it is the thing that is broken.
Capstone
A complete internal developer platform design for a stated organisation, with explicit tradeoffs.
About the Author

Sharon Sahadevan
AI Infrastructure Engineer
Building production GPU clusters on Kubernetes. H100s, large-scale model serving, and end-to-end ML infrastructure across Azure and AWS.
10+ years designing cloud-native platforms with deep expertise in Kubernetes orchestration, GitOps (Argo CD), Terraform, and MLOps pipelines for LLM deployment.
Author of KubeNatives, a weekly newsletter read by 3,000+ DevOps and ML engineers for production insights on K8s internals, GPU scheduling, and model-serving patterns.