Role overview
A senior database engineering role focused on the PostgreSQL and AWS Aurora backbone of a high-volume legal services platform. The position combines deep schema work, query tuning, production troubleshooting, and cross-team collaboration to keep operational workflows, mobile field tools, billing, and reporting running reliably at scale. It is a fit for someone who enjoys the unglamorous craft of making complex relational systems safer and faster.
Responsibilities
- Serve as the PostgreSQL and AWS Aurora subject-matter expert for the operational database behind a large internal platform
- Manage and improve a broad relational schema with hundreds of tables, high-volume workloads, and long-lived historical data
- Review schema changes for correctness, performance, safety, indexing, grants, triggers, foreign keys, and migration hygiene
- Triage production database issues such as slow queries, lock contention, blocking transactions, runaway queries, replication lag, and regressions
- Improve query performance and indexing for large tables, reporting, assignment and routing workflows, mobile API payloads, and operational dashboards
- Automate routine maintenance and operational tasks, support refresh, backup, restore, and release workflows, and collaborate with infrastructure and data teams
Requirements
- 5+ years of production relational database experience, with 8+ years preferred
- Strong production experience with PostgreSQL, ideally including AWS Aurora PostgreSQL
- Strong SQL skills covering joins, CTEs, query plans, indexes, constraints, triggers, transactions, and lock behavior
- Experience investigating high-volume databases with large tables, long-lived schemas, and real production load
- Strong attention to detail when reviewing schema migrations and operational changes
- Clear written communication for documenting findings, trade-offs, and recommended fixes
Nice to have
- Linux, Bash, scripting, cron, or similar orchestration and automation experience for database maintenance
- Java experience, especially with applications using MyBatis, Spring, or similar data access frameworks