🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
JD Overview: We're looking for a Database Engineer with strong, hands-on PostgreSQL ownership experience to support database migration and real-time replication work on Google Cloud. This is a build-and-run role — you'll be the person accountable for the database itself: sizing, securing, deploying, operating, and migrating it, not just connecting to it or transforming data that flows through it. Day-to-day, this role leans DBA/DataDevOps rather than pipeline development. What Success Looks Like The databases you own are fast, available, recoverable, and cost-efficient — and you're the one who gets paged when they're not. Key Responsibilities Migration Plan and execute database migrations to Cloud SQL (PostgreSQL), including schema conversion, data validation, and cutover planning Use Database Migration Service (DMS) to migrate on-prem or cloud-based databases into Cloud SQL with minimal downtime Configure and manage Datastream for change data capture (CDC) and near real-time replication from source databases Own rollback planning for migrations — able to explain what happens if a cutover goes wrong, not just what happens if it goes right Day-to-Day Operations Administer and tune Cloud SQL (PostgreSQL) instances — performance, indexing, backups, high availability Diagnose slow-running databases: query analysis, missing indexes, CPU/memory/IO bottlenecks, locking/contention Set up and maintain monitoring and alerting (CPU, memory, storage, connections, replication lag, error rates) Manage database users, permissions, and secure connectivity (private networking, encryption, connection pooling) Own backup strategy and — critically — have actually performed a restore, not just configured a backup schedule Plan and execute database version upgrades and maintenance windows on live systems Automate recurring database work (provisioning as code, scheduled maintenance, index upkeep) Design & Sizing Size database instances (CPU, memory, storage) based on workload and growth projections Design and configure high-availability setups (multi-zone/multi-region, read replicas) Make and justify cost/performance tradeoffs Required Skills & Experience Strong hands-on PostgreSQL experience — administration, performance tuning, schema design, Experience with Cloud SQL (PostgreSQL) on GCP — ideally provisioned and configured, not just used Experience with Database Migration Service (DMS) and Datastream (or equivalent CDC tools) for migration and replication Demonstrated on-call/incident-response experience for a database (not just for pipeline job failures) Solid understanding of migration best practices — minimal-downtime cutovers, validation, rollback strategies Comfortable troubleshooting replication lag and data consistency issues Preferred Experience with heterogeneous migrations (e.g., Oracle → PostgreSQL) Google Professional Cloud Database Engineer certification, or willingness to complete it (client requests this post-hire) Experience with Terraform or similar for database infrastructure automation
Here's where they are and how to stand out in your next interview.
24.795Jobs
9.577IN
74%EN
That number includes positions in India (9,577), Poland (3,429), the United States (1,753), Singapore (787), and Brazil (779). If you're looking to move or work remotely, check which countries match your goals — then filter WorkMundi by location to see what's actually hiring near you.
Most developer ads you'll see are written in English: 18,397 of the 24,795. That doesn't tell you whether the job itself requires you to speak English or work in English daily, so read each posting carefully. Don't assume the language of the ad matches the language of the team.
The employers posting the most developer roles are Link Group (369 jobs), Upvanta (257), jobgether (226), and OfferZen (212). If you're applying to any of these, research their hiring patterns. They move fast and post often, which means they're either scaling hard or replacing people who didn't fit.
In your interview, expect this: 'Walk me through the last time you had to debug something that took you more than an hour. What was it, what did you try first, and what would you do differently?' Hiring managers ask this to see if you think systematically or just try random fixes. Have a real example ready with specifics.