🎁 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 →
We are looking for a Senior PostgreSQL Database Engineer to own Our platform's relational data architecture, data integrity, query performance and database evolution. This is not a traditional DBA role. We are not primarily looking for someone to administer database servers, patch installations or manage user accounts. We need a hands-on PostgreSQL engineer who can design a production schema from the ground up, enforce data integrity at the database layer, analyze query execution plans, solve performance and concurrency problems, and safely evolve a live database as the platform scales. You will work closely with our Lead Full Stack Platform Engineers and Senior Backend Engineers. What You'll Do Own Our platform's canonical PostgreSQL data modelDesign schemas for investors, identity/KYC, organizations, properties, ownership, transactions, wallets, documents and audit/history recordsDefine relationships, primary and foreign keys, constraints and appropriate data typesDesign tenant-aware data architecture and appropriate tenant-isolation patternsEstablish database-level integrity controls for sensitive financial and ownership recordsDesign transaction boundaries and consistency guaranteesHandle concurrency using appropriate PostgreSQL isolation and locking strategiesDiagnose and prevent race conditions, lock contention and deadlocksDesign indexing strategies using:B-treecomposite indexespartial indexesGIN/GiST/BRIN where justifiedUse EXPLAIN and EXPLAIN ANALYZE to diagnose and optimize production queriesIdentify inefficient joins, N+1 access patterns and poor query plansReview Prisma-generated SQL and identify when raw SQL or database-specific optimization is appropriateDesign safe, backward-compatible zero/low-downtime migrationsDevelop migration rollback and recovery strategiesDesign database audit/history patterns appropriate for a regulated platformEstablish connection-pooling strategies using PgBouncer or equivalentEstablish database performance baselines and monitoringUse PostgreSQL statistics and tools such as pg_stat_statements to identify bottlenecksPlan backup, point-in-time recovery and disaster-recovery strategiesSupport database capacity planning as transaction and data volumes increaseWork directly with backend engineers on API-to-schema contracts and transaction behavior Required Qualifications 48+ years of professional database, backend or data-platform engineering experienceDeep hands-on PostgreSQL production experiencePersonally designed or significantly owned PostgreSQL schemas for production applicationsStrong relational data-modeling skillsAdvanced SQL proficiencyStrong understanding of PostgreSQL constraints and referential integrityHands-on experience with EXPLAIN / EXPLAIN ANALYZEDemonstrated production query optimization experienceStrong indexing knowledge, including composite and partial indexesPractical understanding of PostgreSQL MVCCExperience with transaction isolation, concurrency, row-level locking and deadlock diagnosisExperience planning and executing migrations on active production databasesExperience with connection poolingExperience with backup and recovery strategiesAbility to collaborate with application engineers and translate application requirements into durable data models PostgreSQL is non-negotiable This is not a generic relational-database position. Candidates whose experience is primarily SQL Server, Oracle or MySQL without substantial production PostgreSQL ownership are unlikely to be a fit. We specifically need someone who understands PostgreSQL deeply enough to explain not only what query or schema change should be made, but why PostgreSQL is behaving the way it is. Preferred AWS RDS/Aurora PostgreSQLpg_stat_statementsPgBouncerPostgreSQL partitioningPoint-in-time recoveryLarge production database migrationsMulti-tenant SaaS data architectureFinancial transaction, payments, investment or ledger-like data modelsImmutable/auditable data-history patternsFintech, regulated SaaS or digital-asset platformsPrisma ORM and experience reviewing ORM-generated SQLBasic Node.js/TypeScript familiarity sufficient to work effectively with backend engineersDatabase observability using CloudWatch, Prometheus/Grafana, Datadog or equivalentExperience using AI-assisted engineering tools while independently validating generated schemas, SQL and optimization recommendations What You Are Not Expected to Own You do not need to be the primary Node.js application developer. The Senior Backend Engineer owns services, APIs and business logic. You also do not need Solidity or ERC-3643 experience. Blockchain development is a separate specialist function. What Success Looks Like A backend engineer should be able to bring you a new Our platform workflow and rely on you to determine: How should this data actually be modeled What invariants belong in PostgreSQL How do we prevent inconsistent ownership or transaction records How will this query behave
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.