Database Engineering.

Database problems compound — a bad schema today means painful migrations tomorrow. I design schemas that scale, write migrations that don't break production, and tune indexes so your app stays fast as data grows. You get a database that's an asset, not a liability.

I treat database changes like infrastructure changes — planned, tested, and reversible. Every migration gets a rollback script. Every schema change gets benchmarked against realistic data volumes. I use Alembic for version-controlled migrations and test against staging before touching production.