off-the-stack
cd ~/careers
Data infrastructureaka "DBRE / DBA"

Database Reliability Engineer

Everything runs on a database. Almost no one can keep a big one healthy under load.

Entry
$85k
Mid
$125k
Senior
$175k+
Demand
Steady

The modern DBA — increasingly called a Database Reliability Engineer — keeps the systems of record fast, available, and correct: query tuning, replication, scaling, backups that actually restore, and the migrations everyone else is afraid of. It's a deep, specialized skill that fewer and fewer people are learning, which is precisely why it pays so well and is so hard to replace.

The myth

The cloud and ORMs killed the DBA.

The reality

Managed databases moved the problems, not removed them. At scale, query performance, data modeling, replication, and migrations are harder than ever — and fewer engineers understand them deeply.

cat ./what_you_actually_do.md

  • Diagnose and fix the slow queries and bad indexes quietly choking an application.
  • Design schemas and data models that survive real growth instead of collapsing under it.
  • Own replication, high availability, scaling, and backups you've actually tested by restoring.
  • Plan and run zero-downtime migrations on databases that can't go offline.
  • Be the person who can actually answer 'why is the database on fire?'

cat ./why_underrated.md

Managed cloud databases convinced a generation that nobody needs to understand databases anymore, so almost nobody learned the deep skills — even as applications got bigger and more data-hungry than ever. The result is a widening gap: every company depends utterly on its databases, and fewer and fewer people can keep a large one healthy under pressure. That scarcity makes the deep specialist enormously valuable and remarkably secure, in a discipline that transfers across every company that stores data.

grep -i 'good fit' ./who.md

  • People who enjoy going deep on one hard thing rather than wide on many.
  • Methodical engineers who like performance puzzles and high-stakes correctness.
  • Anyone who finds satisfaction in being the calm expert in a crisis.

cat ./pay.md

Specialists are scarce and load-bearing, so they're paid like it. Senior DBREs at data-heavy companies reach $170k+, and independent database consultants command premium rates because a serious database problem is an emergency nobody else in the building can solve.

./break_in.sh

  1. Pick one database and go deep

    PostgreSQL is the best place to start — open source, ubiquitous, and superbly documented. Learn how it really works inside.

  2. Study query plans and indexing

    Understanding EXPLAIN and how indexes actually work is the core skill that separates a DBRE from an app developer.

  3. Break and restore things on purpose

    Set up replication, simulate failures, practice restores. Confidence under pressure is the whole job.

  4. Grow from a backend role

    Backend or platform engineers who keep volunteering for the gnarly database problems are the natural pipeline into DBRE.

tail -f ./a_day.log

  • 09:00An endpoint went slow overnight; read the query plan and add the missing index.
  • 11:00Review a schema change for a new feature so it won't become a scaling problem later.
  • 14:00Plan a zero-downtime migration for a table that can't be locked.
  • 16:00Run a restore drill, because a backup you haven't tested isn't a backup.

ls ./toolbelt

  • PostgreSQL / MySQL
  • SQL & query plans
  • Replication / HA
  • Backup & recovery
  • A cloud database
  • Monitoring