{"schemaVersion":"jobsearcher.job.v1","id":"714fc9b464c8be7d8a7c7876","url":"https://jobsearcher.com/jobs/714fc9b464c8be7d8a7c7876","canonicalUrl":"https://jobsearcher.com/jobs/714fc9b464c8be7d8a7c7876","title":"Lead PostgreSQL Database Administrator","description":"Senior PostgreSQL DBAWe're looking for talented professionals to join us in bringing smart money management and payment solutions to everyone's fingertips.\r\nThis position is classified as structured hybrid, with an expectation of three (3) days per week working in the office and flexibility to work remotely on the remaining days. On-site expectations may evolve over time to support business needs, with clear communication provided in advance.\r\nLocation Requirement\r\nThis position is open only to candidates who currently reside in one of the following approved locations:\r\nWest Los Angeles, CA\r\nThe Senior PostgreSQL DBA owns the design, availability, performance, and security of our production PostgreSQL estate hosted in Microsoft Azure. The role covers both Azure Database for PostgreSQL (flexible server) and self-managed PostgreSQL on Azure virtual machines running Red Hat Enterprise Linux, CentOS Stream, and Windows Server.\r\nThis is a hands-on senior engineering role, not a supervisory one. The DBA is the final escalation point for database incidents, the architect of our high-availability and disaster-recovery topology (active-passive and active-active), and the person who keeps us current on PostgreSQL 17, 18, and the upcoming 19 release.\r\nKey responsibilities\r\nDuties marked critical are the core of the role; a candidate who cannot demonstrate them should not advance past the technical screen.\r\n1. High availability and disaster recovery (critical)\r\nActive-passive (primary/standby):\r\nDesign, deploy, and operate zone-redundant high availability on Azure Database for PostgreSQL flexible server: synchronous standby in a second availability zone, automatic failover in 60–120 seconds with zero data loss, and the 99.99% uptime SLA that configuration carries.\r\nDecide between zone-redundant and same-zone (zonal) HA per workload based on latency tolerance and zone-failure risk, and document the trade-off.\r\nRun and document planned, unplanned, and forced failover tests at least quarterly; measure downtime from the application side, not from the service side.\r\nSize max_replication_slots and max_wal_senders correctly (four reserved for HA plus one per read replica and per logical slot) so failovers never fail for lack of slots.\r\nBuild equivalent active-passive clusters on self-managed Azure VMs using streaming replication with Patroni and etcd (Linux) or a supported cluster manager on Windows, fronted by HAProxy, PgBouncer, or an Azure internal load balancer.\r\nDesign cross-region disaster recovery: geo-redundant backups, cross-region read replicas, and promotion runbooks with tested RPO/RTO targets.\r\nPreserve logical replication across failover: pg_failover_slots on PostgreSQL 16 and earlier, native sync_replication_slots = on with hot_standby_feedback = on on PostgreSQL 17 and later.\r\nActive-active (bi-directional / multi-master):\r\nDesign and operate active-active topologies across Azure regions using the pglogical extension or native logical replication, following Microsoft's published bi-directional replication guidance for Azure Database for PostgreSQL.\r\nDefine and enforce conflict-avoidance and conflict-resolution strategy: partitioned write ownership, non-overlapping sequence ranges or UUIDv7 keys, last-writer-wins rules where appropriate, and monitoring for conflict counts.\r\nManage DDL propagation across nodes (pglogical.replicate_ddl_command() or controlled DDL rollout for native replication) and sequence synchronization (PostgreSQL 19 adds native sequence replication via ALL SEQUENCES and REFRESH SEQUENCES).\r\nMonitor replication lag, slot retention, and retain_dead_tuples settings on every node; alert before WAL retention threatens primary disk.\r\nOwn the decision of when active-active is and is not appropriate, and push back on it where a well-run active-passive design meets the requirement at lower risk.\r\n2. Azure platform administration (critical)\r\nProvision and manage Azure Database for PostgreSQL flexible server via the portal, Azure CLI, Az.PostgreSQLFlexibleServer PowerShell module, ARM/Bicep, Terraform, and REST API.\r\nConfigure networking: VNet integration, private endpoints, private DNS zones, firewall rules, and migration from VNet-injected to private-endpoint servers (now supported for HA-enabled servers).\r\nImplement Microsoft Entra ID authentication, Entra group login, managed identities, customer-managed keys (including cross-tenant CMK), and SCRAM-SHA-256 as the password default.\r\nManage compute and storage tiers, including Premium SSD v2 (GA with HA, read replicas, geo-DR, and major version upgrade support) and online storage scaling.\r\nOperate built-in PgBouncer (currently 1.25.x) for connection pooling and tune pool modes per application.\r\nRun in-place major version upgrades on flexible server (PostgreSQL 18 upgrade GA June 2026), including pre-upgrade extension and large-object checks.\r\nManage read replicas (in-region, cross-region, cascading), promote them when required, and keep replica lag within SLA.\r\nConfigure backup retention, long-term retention via Azure Backup, point-in-time restore, and recovery of deleted servers; test restores on a schedule.\r\nEvaluate and deploy elastic clusters (sharded flexible server) for horizontally scaled workloads where appropriate.\r\nSet custom maintenance windows and coordinate Azure-initiated minor version patching with application owners.\r\n3. Self-managed PostgreSQL on Linux and Windows (critical)\r\nInstall, patch, and tune PostgreSQL 15–19 on RHEL 8/9, CentOS Stream, and Windows Server 2019/2022 running as Azure VMs.\r\nOn Linux: manage systemd units, SELinux contexts, firewalld, LVM/managed-disk layout, kernel and huge-page settings, and PGDG repository packaging.\r\nOn Windows: manage the PostgreSQL service, NTFS permissions, Windows Firewall, scheduled tasks for maintenance, and Windows-specific installer and upgrade behavior.\r\nOperate backup tooling: pgBackRest or Barman on Linux, pg_basebackup and WAL archiving to Azure Blob Storage on both platforms, with incremental backups where supported.\r\n4. Performance engineering\r\nDiagnose and tune queries using EXPLAIN (ANALYZE, BUFFERS, WAL, IO), pg_stat_statements, auto_explain, and Azure Query Performance Insight.\r\nTune autovacuum per table, including PostgreSQL 19 parallel autovacuum (autovacuum_max_parallel_workers) and the new prioritization scoring, and prevent transaction-ID wraparound.\r\nReclaim bloat without downtime using REPACK (CONCURRENTLY) on PostgreSQL 19, pg_repack on earlier versions, and VACUUM FULL only as a last resort.\r\nTune asynchronous I/O (io_method, worker counts) introduced in PostgreSQL 18, memory parameters, checkpointing, and WAL compression.\r\nDesign partitioning, indexing (B-tree, BRIN, GIN, GiST, skip-scan on PostgreSQL 18), and extended statistics strategies.\r\nUse pg_plan_advice and pg_stash_advice on PostgreSQL 19 to stabilize problem plans without permanent hints.\r\n5. Security and compliance\r\nEnforce least-privilege roles, row-level security, and predefined roles (pg_read_all_data, pg_write_all_data); retire MD5 passwords before PostgreSQL 19 begins warning on them.\r\nManage TLS, SNI (new in PostgreSQL 19), certificate rotation, and encryption at rest with customer-managed keys.\r\nProduce audit evidence with pgaudit and Azure Monitor diagnostic logs for SOC 2, HIPAA, or PCI as required.\r\nRespond to CVEs within the patching SLA and track Azure-applied minor version patches.\r\n6. Monitoring and incident response\r\nBuild dashboards and alerts in Azure Monitor, Log Analytics, and the Azure HA health status monitor; supplement with Prometheus/Grafana or Datadog for VM-hosted clusters.\r\nInstrument the new PostgreSQL 19 views (pg_stat_recovery, pg_stat_lock, pg_stat_autovacuum_scores) and the per-process-type log_min_messages.","company":"Green Dot","rawCompany":"green dot","city":"New York","state":"NY","isRemote":false,"isActive":true,"createdAt":"2026-11-20T01:31:54.766Z","occupations":[{"code":"15-1242.00","title":"Database Administrators","slug":"database-administrators"},{"code":"15-1243.00","title":"Database Architects","slug":"database-architects"},{"code":"15-1244.00","title":"Network and Computer Systems Administrators","slug":"network-and-computer-systems-administrators"}],"industries":[{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Lead PostgreSQL Database Administrator","description":"Senior PostgreSQL DBAWe're looking for talented professionals to join us in bringing smart money management and payment solutions to everyone's fingertips.\r\nThis position is classified as structured hybrid, with an expectation of three (3) days per week working in the office and flexibility to work remotely on the remaining days. On-site expectations may evolve over time to support business needs, with clear communication provided in advance.\r\nLocation Requirement\r\nThis position is open only to candidates who currently reside in one of the following approved locations:\r\nWest Los Angeles, CA\r\nThe Senior PostgreSQL DBA owns the design, availability, performance, and security of our production PostgreSQL estate hosted in Microsoft Azure. The role covers both Azure Database for PostgreSQL (flexible server) and self-managed PostgreSQL on Azure virtual machines running Red Hat Enterprise Linux, CentOS Stream, and Windows Server.\r\nThis is a hands-on senior engineering role, not a supervisory one. The DBA is the final escalation point for database incidents, the architect of our high-availability and disaster-recovery topology (active-passive and active-active), and the person who keeps us current on PostgreSQL 17, 18, and the upcoming 19 release.\r\nKey responsibilities\r\nDuties marked critical are the core of the role; a candidate who cannot demonstrate them should not advance past the technical screen.\r\n1. High availability and disaster recovery (critical)\r\nActive-passive (primary/standby):\r\nDesign, deploy, and operate zone-redundant high availability on Azure Database for PostgreSQL flexible server: synchronous standby in a second availability zone, automatic failover in 60–120 seconds with zero data loss, and the 99.99% uptime SLA that configuration carries.\r\nDecide between zone-redundant and same-zone (zonal) HA per workload based on latency tolerance and zone-failure risk, and document the trade-off.\r\nRun and document planned, unplanned, and forced failover tests at least quarterly; measure downtime from the application side, not from the service side.\r\nSize max_replication_slots and max_wal_senders correctly (four reserved for HA plus one per read replica and per logical slot) so failovers never fail for lack of slots.\r\nBuild equivalent active-passive clusters on self-managed Azure VMs using streaming replication with Patroni and etcd (Linux) or a supported cluster manager on Windows, fronted by HAProxy, PgBouncer, or an Azure internal load balancer.\r\nDesign cross-region disaster recovery: geo-redundant backups, cross-region read replicas, and promotion runbooks with tested RPO/RTO targets.\r\nPreserve logical replication across failover: pg_failover_slots on PostgreSQL 16 and earlier, native sync_replication_slots = on with hot_standby_feedback = on on PostgreSQL 17 and later.\r\nActive-active (bi-directional / multi-master):\r\nDesign and operate active-active topologies across Azure regions using the pglogical extension or native logical replication, following Microsoft's published bi-directional replication guidance for Azure Database for PostgreSQL.\r\nDefine and enforce conflict-avoidance and conflict-resolution strategy: partitioned write ownership, non-overlapping sequence ranges or UUIDv7 keys, last-writer-wins rules where appropriate, and monitoring for conflict counts.\r\nManage DDL propagation across nodes (pglogical.replicate_ddl_command() or controlled DDL rollout for native replication) and sequence synchronization (PostgreSQL 19 adds native sequence replication via ALL SEQUENCES and REFRESH SEQUENCES).\r\nMonitor replication lag, slot retention, and retain_dead_tuples settings on every node; alert before WAL retention threatens primary disk.\r\nOwn the decision of when active-active is and is not appropriate, and push back on it where a well-run active-passive design meets the requirement at lower risk.\r\n2. Azure platform administration (critical)\r\nProvision and manage Azure Database for PostgreSQL flexible server via the portal, Azure CLI, Az.PostgreSQLFlexibleServer PowerShell module, ARM/Bicep, Terraform, and REST API.\r\nConfigure networking: VNet integration, private endpoints, private DNS zones, firewall rules, and migration from VNet-injected to private-endpoint servers (now supported for HA-enabled servers).\r\nImplement Microsoft Entra ID authentication, Entra group login, managed identities, customer-managed keys (including cross-tenant CMK), and SCRAM-SHA-256 as the password default.\r\nManage compute and storage tiers, including Premium SSD v2 (GA with HA, read replicas, geo-DR, and major version upgrade support) and online storage scaling.\r\nOperate built-in PgBouncer (currently 1.25.x) for connection pooling and tune pool modes per application.\r\nRun in-place major version upgrades on flexible server (PostgreSQL 18 upgrade GA June 2026), including pre-upgrade extension and large-object checks.\r\nManage read replicas (in-region, cross-region, cascading), promote them when required, and keep replica lag within SLA.\r\nConfigure backup retention, long-term retention via Azure Backup, point-in-time restore, and recovery of deleted servers; test restores on a schedule.\r\nEvaluate and deploy elastic clusters (sharded flexible server) for horizontally scaled workloads where appropriate.\r\nSet custom maintenance windows and coordinate Azure-initiated minor version patching with application owners.\r\n3. Self-managed PostgreSQL on Linux and Windows (critical)\r\nInstall, patch, and tune PostgreSQL 15–19 on RHEL 8/9, CentOS Stream, and Windows Server 2019/2022 running as Azure VMs.\r\nOn Linux: manage systemd units, SELinux contexts, firewalld, LVM/managed-disk layout, kernel and huge-page settings, and PGDG repository packaging.\r\nOn Windows: manage the PostgreSQL service, NTFS permissions, Windows Firewall, scheduled tasks for maintenance, and Windows-specific installer and upgrade behavior.\r\nOperate backup tooling: pgBackRest or Barman on Linux, pg_basebackup and WAL archiving to Azure Blob Storage on both platforms, with incremental backups where supported.\r\n4. Performance engineering\r\nDiagnose and tune queries using EXPLAIN (ANALYZE, BUFFERS, WAL, IO), pg_stat_statements, auto_explain, and Azure Query Performance Insight.\r\nTune autovacuum per table, including PostgreSQL 19 parallel autovacuum (autovacuum_max_parallel_workers) and the new prioritization scoring, and prevent transaction-ID wraparound.\r\nReclaim bloat without downtime using REPACK (CONCURRENTLY) on PostgreSQL 19, pg_repack on earlier versions, and VACUUM FULL only as a last resort.\r\nTune asynchronous I/O (io_method, worker counts) introduced in PostgreSQL 18, memory parameters, checkpointing, and WAL compression.\r\nDesign partitioning, indexing (B-tree, BRIN, GIN, GiST, skip-scan on PostgreSQL 18), and extended statistics strategies.\r\nUse pg_plan_advice and pg_stash_advice on PostgreSQL 19 to stabilize problem plans without permanent hints.\r\n5. Security and compliance\r\nEnforce least-privilege roles, row-level security, and predefined roles (pg_read_all_data, pg_write_all_data); retire MD5 passwords before PostgreSQL 19 begins warning on them.\r\nManage TLS, SNI (new in PostgreSQL 19), certificate rotation, and encryption at rest with customer-managed keys.\r\nProduce audit evidence with pgaudit and Azure Monitor diagnostic logs for SOC 2, HIPAA, or PCI as required.\r\nRespond to CVEs within the patching SLA and track Azure-applied minor version patches.\r\n6. Monitoring and incident response\r\nBuild dashboards and alerts in Azure Monitor, Log Analytics, and the Azure HA health status monitor; supplement with Prometheus/Grafana or Datadog for VM-hosted clusters.\r\nInstrument the new PostgreSQL 19 views (pg_stat_recovery, pg_stat_lock, pg_stat_autovacuum_scores) and the per-process-type log_min_messages.","datePosted":"2026-11-20T01:31:54.766Z","dateModified":"2026-11-20T01:31:54.766Z","hiringOrganization":{"@type":"Organization","name":"Green Dot","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"New York","addressRegion":"NY","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"714fc9b464c8be7d8a7c7876"},"url":"https://jobsearcher.com/jobs/714fc9b464c8be7d8a7c7876"}}