Need a Google Cloud & PostgreSQL DevOps engineer to run a 5-stage production DB backup runbook: read-only preflight check, GPG public-key encrypted dump, isolated Docker restore test, and verified upl

Job Post: GCP & PostgreSQL DevOps Specialist — Runbook Execution & Encrypted Backup Project Overview We are looking for an experienced Google Cloud Platform (GCP) and PostgreSQL DevOps engineer to execute a structured, 5-stage production database verification, GPG-encrypted export, isolated restore test, and private Google Cloud Storage (GCS) upload for our Node.js/PostgreSQL application *Batkahi*. All bash scripts (`00_preflight.sh` through upload) are already prepared; we need a disciplined operator to execute them cleanly under strict milestone gates and zero-trust security practices. Scope of Work & Milestones Milestone 1 — Preflight Inspection Only (`00_preflight.sh`): Connect via least-privilege IAM to our GCP project (`coral-computing-zv9wh`), run the read-only preflight verification script to confirm Cloud SQL instance details, active databases, PostgreSQL version, and local disk capacity, and deliver the preflight report for founder sign-off before proceeding. Milestone 2 — GPG-Encrypted Export & Isolated Restore Verification: Upon written approval of the preflight report, execute the encrypted export using our provided GPG Public Key only, then perform an isolated restore into a separate temporary test environment to verify data integrity and table row counts without touching production. Milestone 3 — Private Bucket Upload & Final Verification: Once the isolated restore is verified, upload the encrypted bundle and confirm all 9 required objects (archives, checksums, and manifests) are present and verified in the designated private GCS bucket, followed by clean teardown of temporary local files. Mandatory Security & Operational Rules 1. Zero-Trust Key Handling: You will only receive a GPG public key. You will never ask for or handle our GPG private key or passphrase. 2. Strict Gatekeeping: No export or upload commands may be executed until the `00_preflight.sh` report is reviewed and approved. 3. Live Verification: Steps 4 and 5 (isolated restore check and 9-object bucket verification) will be reviewed over a brief live screen-share. Required Qualifications * Proven hands-on experience with Google Cloud SQL (PostgreSQL), `gcloud` CLI, IAM permissions, and GCS private buckets. * Strong command-line fluency in Linux bash scripting, `pg_dump` / `pg_restore`, SHA-256 checksums, and GPG asymmetric encryption. * Available for overlap during IST business/evening hours. To Apply, Please Answer This Screening Question: In our runbook, we encrypt the database dump with GPG before uploading to GCS, and we verify the backup via an isolated restore first. Why do we use only the recipient's GPG public key during encryption, and how do we prevent an isolated restore from accidentally colliding with our live production database?