Shift Time: 3 PM IST - 12 AM IST

Duties and Responsibilities:

1) Produce clear scaling options (e.g. "replicas + routing”, "move to Aurora + N readers”, "proxy + tune”, "partition hot tables”) with tradeoffs, cost modeling, and risk, not only tuning the current box.
2) Performance: Profile workloads (pg_stat_statements, EXPLAIN ANALYZE, logs), tune queries and indexes, reduce lock contention and bloat, advise on connection pooling and transaction patterns.
3) Schema & migrations: Own database migration scripts – review DDL changes, migration risk, and rollout strategy; help design partitioning, constraints, and data lifecycle (archival, retention).
4) RDS / Aurora operations: Size instances, storage, and I/O; understand replication, failover, reader endpoints, RDS parameter groups, backups, PITR, major version upgrades, and maintenance windows.
5) Observability: Define SLIs for DB latency and errors; work with metrics, slow query logs, and Performance Insights (or equivalent).
6) Incidents: Own end-to-end performance investigations (metrics, logs, EXPLAIN, wait events) and produce actionable index/query/schema changes.
7) Collaboration: Document playbooks, review high-risk SQL in PRs, and mentor engineers on PostgreSQL best practices.

Required Qualifications :

1) 8+ years of experience as a database engineer/administrator with at least 3 years of experience managing PostgreSQL on AWS RDS or Aurora.
2) BS or higher in Computer Science or related field. Required Skills
3) Deep PostgreSQL: Query planner behavior, indexing (B-tree, partial, covering), MVCC, vacuum/autovacuum, statistics, concurrency and isolation levels, extensions when appropriate.
4) Amazon RDS for PostgreSQL: Parameter groups, version upgrades, backups, Multi-AZ, read replicas, RDS Proxy, monitoring, and security (IAM, encryption, networking). 5) Amazon Aurora PostgreSQL-Compatible: Cluster topology, reader/writer behavior, failover, storage and replication concepts, and operational tradeoffs vs. standard RDS.
5) Cost optimization: Right-sizing, IOPS, storage.
6) Hands-on production experience tuning PostgreSQL under real load (not only local/dev).
7) Experience with high migration velocity (many schema changes, zero-downtime patterns, backfills).
8) Strong communication: explain tradeoffs to non-DB specialists and write clear runbooks.