Karka
All courses

Free course

Platform Engineering Fundamentals

A plain-English introduction to what an internal platform is, the problems it exists to reduce, and how platform and product teams share the work.

What this course does not do

Awareness-level course. It builds shared understanding and vocabulary only, and makes no competence claim about designing, building, securing or operating a platform.

AwarenessBeginnerPlatform Engineering
6 modules 30 lessons 3 enrolled ~6h of material
Start learning — freeAlready a member? Sign in

First three lessons free. Full access with Founding Annual Access, ₹3,999 for your first year.

Platform Engineering Fundamentals

By the end

What you'll build

  • Explain in plain terms what an internal platform is and which delivery problems it is meant to reduce
  • Distinguish a platform team from a shared services team and from a tooling team
  • Describe how responsibility is divided between a platform team and the teams consuming the platform
  • Read a platform service description and identify what is supported, what is self-service and what is out of scope
  • Recognise the common signals that a platform is or is not being adopted

Curriculum

What's inside

6 modules · 30 lessons

  1. 01

    Why internal platforms exist

    5 lessons
    • What a platform actually is, and what it is not
    • How the delivery problem changed as teams took on more of the stack
    • Cognitive load as the core design constraint
    • Platforms, shared services and tooling teams compared
    • Platform, load and ownership: match the idea to its meaningmatch pairs
  2. 02

    The shape of an internal platform

    5 lessons
    • The planes of a platform: developer control, integration, monitoring and resource
    • Golden paths and paved roads in plain language
    • Self-service as a design goal rather than a portal
    • Where the platform ends and the product team begins
    • Planes, paved roads and self-service: complete the statementfill blank
  3. 03

    Who does what

    5 lessons
    • Reading a responsibility boundary between a platform team and the teams it serves
    • Common operating models at a glance
    • Enablement, as-a-service and collaboration interactions
    • Support expectations and escalation in everyday language
    • Settle a boundary dispute before writing any codesequence order
  4. 04

    How platforms are judged

    5 lessons
    • Adoption is the most honest measure of an internal platform
    • Delivery flow signals every engineer should recognise
    • Cost, reliability and developer time as competing pressures
    • Warning signs of a platform nobody chooses to use
    • The platform nobody is usingscenario
  5. 05

    Working with a platform day to day

    5 lessons
    • Requesting, consuming and giving feedback on a platform capability
    • Reading platform documentation and service contracts
    • Raising a paved-road exception responsibly
    • Where security and compliance sit in the everyday flow
    • Requests, contracts and exceptions: match the situation to the right movematch pairs
  6. 06

    Practice and check

    5 lessons
    • Planes and boundary verbsmatch pairs
    • Moving onto the paved roadsequence order
    • Getting the words rightfill blank
    • The queue the paved road does not supportscenario
    • Course quizquiz

The shape of it

How this course works

Short lessons

30 lessons across 6 modules, each small enough to finish in one sitting.

Practice as you go

Every lesson ends with a small space for what you noticed — the doing is the learning.

Progress you can see

Your progress is saved lesson by lesson, ready whenever you come back.

Ready when you are.

Make an account and this course opens up — your progress is saved from the very first lesson.

Start learning — freeSign in