Learn Computer Stuff
Home / IT, Systems & Cloud / Platform Engineer
IT, Systems & Cloud

Platform Engineer

You build the paved road other engineers ship on, so they stop reinventing the same pipeline.

No degree needed Hard, and half of it is judging what other engineers will actually adopt.


Can I actually do this?

Open without a degree, but not open from a standing start. Platform teams exist inside organisations big enough to have a shared internal toolchain, and they hire people who have already felt the pain of not having one. The usual route is devops or sysadmin work first. Learning Kubernetes deeply is free and is the single highest-leverage thing you can do here.

Who it suits. People who would rather fix a problem once for fifty people than fifty times for one.

Runway. Years. This is a second or third role.

Coming from another job?

Coming from devops, sysadmin or cloud work? That is the normal path. The shift is treating your own engineers as the users. DevOps Engineer Systems Administrator Cloud Engineer

Also advertised as

  • Infrastructure Engineer
  • Developer Experience Engineer
  • Internal Platform Engineer
  • Cloud Platform Engineer

The route

Four stations, in order. Each one is a thing you finish before the next matters.

  1. Station one

    Learn it free

    Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.

    Kubernetes — concepts

    Free to learn · no certificate

    The substrate nearly every internal platform is built on now. Free and thorough; read concepts before tutorials or you will cargo-cult.

    Kubernetes — tutorials

    Free to learn · no certificate

    Hands-on once the concepts land. Free.

    GitHub Actions — quickstart

    Free to learn · no certificate

    A platform is mostly the paths your builds take. Start by owning one properly.

    See the full catalog in the explorer →

  2. Station two

    Attest strategically

    The CNCF Kubernetes exams are hands-on rather than multiple choice, which makes them one of the few certificates here that is hard to pass without the skill. They still are not what gets you the job — production experience is. If your employer will fund one, take it; if you are paying yourself, do the free material first and see how far it carries you.

    Certified Kubernetes Administrator (CKA)

    Free to learn · paid certificate Recognized

    The honest cost
    Cost$445
    ValidityNot stated on the certification page. CNCF does not print a validity period there, so we record it as unknown rather than repeat a figure from elsewhere.
    RenewalNot stated on the certification page.
    AssessmentPerformance-based, hands-on exam in a live environment (not multiple choice)
    ProctoredYes
    Verify viaunknown
    Cost per active yearUnknowncannot be computed — CNCF publishes the $445 fee but not a validity period

    The standard Kubernetes credential, and AI infrastructure runs largely on Kubernetes.

    Read this before you buy

    The $445 fee includes one free retake, which is unusual and worth weighing against cheaper exams that charge again on a resit. HONEST GAP: CNCF does not print a validity period on this page, so we cannot tell you the cost per active year. Check before you budget. It is listed because a performance-based exam is a stronger signal than a quiz.

    · Official page

  3. Station three

    Prove it

    A certificate says you passed a test. These say you can do the job.

    A paved road someone else used

    Build something — a template, a pipeline, a self-service deploy — that another engineer adopted without you sitting next to them. Adoption is the metric.

    A golden path with its escape hatch documented

    Show the default route AND what to do when a team genuinely needs to leave it. Platforms that forbid the exception get bypassed.

    Something you deleted

    A tool or step you removed and what it cost the team to maintain. Restraint is the senior signal here.

  4. Station four

    Get hired

    Search these exact titles

    • platform engineer
    • infrastructure engineer
    • developer experience engineer
    • internal tools engineer

    Who hires for this. Companies with enough engineers that a shared toolchain pays for itself — typically fifty engineers and up. Scale-ups, big tech, banks.

    Interviews here probe whether other people actually used what you built, which is why the role is hard to enter without having worked on a team. That is our reading of the field, not a verified hiring statistic.

    On salary

    We don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.


Where this route continues

· How we verify