App Dev → DBA Path

A structured progression from application developer to database engineer on PostgreSQL 18.4 - indexes, MVCC, and your first migration review with milestones you can self-assess quarterly.

Recipe

App Dev → DBA Path (typical 18-36 months)
  Phase 1 (0-6 mo):  Query author + EXPLAIN fluency
  Phase 2 (6-12 mo): MVCC, locks, safe migrations
  Phase 3 (12-18 mo): Secondary reviewer + staging drill
  Phase 4 (18-24 mo): On-call shadow + HA/PITR ownership
  Staff (24+ mo):     Fleet governance, RTO/RPO, major upgrades

When to use this path:

• Backend engineer wants formal database career track
• Team lacks dedicated DBA but needs internal depth
• Mentoring plan for Skills Matrix gaps

Working Example

Phase 1: Indexes and EXPLAIN

-- Learn b-tree leftmost prefix rule
CREATE INDEX idx_orders_tenant_created ON orders (tenant_id, created_at DESC);
 
EXPLAIN (ANALYZE, BUFFERS)
SELECT * FROM orders
WHERE tenant_id = $1
ORDER BY created_at DESC
LIMIT 20;

Milestone: Three merged PRs with EXPLAIN evidence approved without rewrite requests.

Study: B-tree Indexes, EXPLAIN Review Skill

Phase 2: MVCC and Locks

-- See xmin/xmax visibility (conceptual)
SELECT xmin, xmax, ctid FROM orders WHERE id = $1;
 
-- Lock modes during migration
SELECT mode, granted FROM pg_locks WHERE relation = 'orders'::regclass;

Milestone: Score a migration medium risk correctly using Migration Safety Skill before DBA does.

Study: PostgreSQL Architecture, Zero Downtime DDL

Phase 3: First Migration Review

## Reviewer checklist (your first secondary review)
- [ ] Lock risk labeled
- [ ] CONCURRENTLY where needed
- [ ] Rollback SQL present
- [ ] EXPLAIN if query change
- [ ] Approve or request changes with specific SQL comments

Milestone: Review five migration PRs; zero prod incidents traced to approved DDL.

Study: Code Review for SQL

Phase 4: Operations

# Failover drill participation
patronictl list
psql -c "SELECT pg_is_in_recovery();"

Milestone: Lead one staging failover drill scribe role; document RTO in ticket.

Study: Failover Drill Skill, PITR Basics

Deep Dive

Skills Transfer Table

Mentorship Pairing

Week A: Mentee authors migration; mentor reviews with EXPLAIN Review Skill rubric
Week B: Mentee reviews app teammate PR; mentor audits review quality
Week C: Joint incident bundle on staging simulated alert

Anti-Patterns

• Jumping to HA without EXPLAIN depth - misdiagnoses query storms as failover problems
• Cert collection without on-call shadow - theory without pressure
• Only reading, never reviewing - review skill needs repetition

Gotchas

• Titles without scope - "DBA" title but no prod access policy leads to unsafe heroics. Fix: formal rotation and guardrails.
• Ignoring application domain - best database engineers keep product context. Fix: stay embedded in one service squad.
• Skipping Linux CLI - cannot triage disk full incidents. Fix: Linux CLI for DBAs Basics in phase 2.
• ORM-only mental model - misses partial indexes and constraint-trigger interactions. Fix: write raw SQL monthly.

Alternatives

FAQs

Related

• Onboarding Basics - day one setup
• Skills Matrix - junior to staff grid
• Mentoring App Teams - lead perspective
• Career Growth DBA → Staff - staff track
• Pairing on Query PRs - hands-on review

Stack versions: This page was written for PostgreSQL 18.4 OLTP teams with Flyway migrations and Patroni or RDS HA.