Learn Computer Stuff
Home / Software Engineering / Site Reliability Engineer
Software Engineering

Site Reliability Engineer

You keep the thing running at scale, and you use software to do it rather than heroics.

No degree needed Hard. You need both the systems knowledge and the ability to write real software.


Can I actually do this?

Not an entry-level job, and we would be misleading you to suggest otherwise. It is genuinely open without a degree, but essentially everyone arrives from sysadmin, devops, backend or operations work. If you are starting from zero, start at help desk or devops and come back. The canonical texts below are free, and reading them early is not wasted.

Who it suits. People who are calm when something is on fire and interested in why it caught fire.

Runway. Years. This is a second or third role, not a first one.

Coming from another job?

Coming from devops, sysadmin or backend? That is the normal path. What you add is measuring reliability rather than feeling it. DevOps Engineer Systems Administrator Backend Developer

Also advertised as

  • SRE
  • Production Engineer
  • Infrastructure Engineer
  • Reliability 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.

    Site Reliability Engineering (the Google SRE book)

    Free to learn · no certificate

    The book that named the discipline, free to read in full online. Error budgets, SLOs, toil, on-call. This is the shared vocabulary of the field.

    The Site Reliability Workbook

    Free to learn · no certificate

    The practical companion — how to actually implement SLOs rather than admire them. Also free in full.

    Kubernetes — the official documentation

    Free to learn · no certificate

    Most reliability work now happens on or around this. Free; the CNCF exams that test it are separately paid.

    See the full catalog in the explorer →

  2. Station two

    Attest strategically

    Nothing named here. The Kubernetes certifications from the CNCF are real, hands-on and respected, and they appear in our directory — but they are priced in the hundreds and they are not what gets you into SRE. What does is production experience and being able to talk about an incident you handled. If your employer will pay for a CNCF exam, take it; do not fund one yourself as a way in.

    Nothing here is worth paying for

    No credential needed

    Nothing named here. The Kubernetes certifications from the CNCF are real, hands-on and respected, and they appear in our directory — but they are priced in the hundreds and they are not what gets you into SRE. What does is production experience and being able to talk about an incident you handled. If your employer will pay for a CNCF exam, take it; do not fund one yourself as a way in.

  3. Station three

    Prove it

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

    A postmortem you wrote

    A real incident, with a timeline, a root cause and what changed afterwards — and no blame in it. This is the single most characteristic artifact of the role.

    An SLO with the reasoning behind the number

    Not 99.9% because it sounds good. Why that number, what it costs, and what happens when you spend the budget.

    Toil you automated away

    Something manual and repeated that you deleted. Show the before, the after and the hours saved.

  4. Station four

    Get hired

    Search these exact titles

    • site reliability engineer
    • SRE
    • production engineer
    • infrastructure engineer

    Who hires for this. Companies large enough for reliability to be someone's whole job — big tech, fintech, infrastructure providers, and anyone running a platform other businesses depend on.

    Interviews here lean heavily on incidents you have personally handled, which is why the role resists being entered straight from study. 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