Learn Computer Stuff
Home / Data / Database Administrator
Data

Database Administrator

You keep the database fast, backed up, and awake at three in the morning.

No degree needed Hard, and the consequences of getting it wrong are permanent in a way most software is not.


Can I actually do this?

Open without a degree and often entered from sysadmin work. Fewer pure DBA roles exist than a decade ago because cloud managed services absorbed much of the routine work — we would rather say that plainly. What remains is deeper: performance, recovery, and the databases too critical to hand to a managed service. The documentation below is free and unusually good.

Who it suits. People who take backups seriously and find performance puzzles satisfying.

Runway. A year or more. The failure modes take time to meet.

Coming from another job?

Coming from sysadmin work? You already understand backups, monitoring and being on call. The database is the new part. Systems Administrator Data Engineer Backend Developer

Also advertised as

  • DBA
  • Database Engineer
  • Database 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.

    PostgreSQL — server administration

    Free to learn · no certificate

    Configuration, backup, recovery, monitoring and tuning, from the project itself. Free, thorough, and the best free database administration text we know of.

    PostgreSQL — the official tutorial

    Free to learn · no certificate

    Start here if SQL is not yet second nature.

    Site Reliability Engineering (the Google SRE book)

    Free to learn · no certificate

    Modern database work is reliability work. Free in full.

    See the full catalog in the explorer →

  2. Station two

    Attest strategically

    Nothing worth buying speculatively. Database certifications are strongly vendor-specific, so which one is worth anything depends entirely on what your employer runs — and buying the wrong one is money gone. A restore you can prove works is a better argument than any of them.

    Nothing here is worth paying for

    No credential needed

    Nothing worth buying speculatively. Database certifications are strongly vendor-specific, so which one is worth anything depends entirely on what your employer runs — and buying the wrong one is money gone. A restore you can prove works is a better argument than any of them.

  3. Station three

    Prove it

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

    A restore you actually performed

    Not a backup — a restore, timed, from scratch. Anyone can take backups. The job is proving they work.

    A slow query you made fast

    Show the plan before, what you changed, the plan after, and the numbers.

    A failover you rehearsed

    Break it deliberately in a lab and document what happened. The first time should not be in production.

  4. Station four

    Get hired

    Search these exact titles

    • database administrator
    • DBA
    • database engineer
    • database reliability engineer

    Who hires for this. Banks, health systems, government, large retailers — anywhere the data is too critical or too large to leave entirely to a managed service.

    Interviews here dwell on recovery scenarios, which rewards people who have actually restored something. 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