Job Description

We are looking for a Senior PostgreSQL Database Engineer to own Our platform's relational data architecture, data integrity, query performance and database evolution.

n

n

This is not a traditional DBA role.

n

n

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.

n

n

What You'll Do

n

n
- Own Our platform's canonical PostgreSQL data model
n
- Design schemas for investors, identity/KYC, organizations, properties, ownership, transactions, wallets, documents and audit/history records
n
- Define relationships, primary and foreign keys, constraints and appropriate data types
n
- Design tenant-aware data architecture and appropriate tenant-isolation patterns
n
- Establish database-level integrity controls for sensitive financial and ownership records
n
- Design transaction boundaries and consistency guarantees
n
- Handle concurrency using appropriate PostgreSQL isolation and locking strategies
n
- Diagnose and prevent race conditions, lock contention and deadlocks
n
- Design indexing strategies using:
n
- B-tree
n
- composite indexes
n
- partial indexes
n
- GIN/GiST/BRIN where justified
n
- Use EXPLAIN and EXPLAIN ANALYZE to diagnose and optimize production queries
n
- Identify inefficient joins, N+1 access patterns and poor query plans
n
- Review Prisma-generated SQL and identify when raw SQL or database-specific optimization is appropriate
n
- Design safe, backward-compatible zero/low-downtime migrations
n
- Develop migration rollback and recovery strategies
n




- Design database audit/history patterns appropriate for a regulated platform
n
- Establish connection-pooling strategies using PgBouncer or equivalent
n
- Establish database performance baselines and monitoring
n
- Use PostgreSQL statistics and tools such as pg_stat_statements to identify bottlenecks
n
- Plan backup, point-in-time recovery and disaster-recovery strategies
n
- Support database capacity planning as transaction and data volumes increase
n
- Work directly with backend engineers on API-to-schema contracts and transaction behavior
n

n

n

Required Qualifications

n

n
- 4–8+ years of professional database, backend or data-platform engineering experience
n
- Deep hands-on PostgreSQL production experience
n
- Personally designed or significantly owned PostgreSQL schemas for production applications
n
- Solid relational data-modeling skills
n
- Advanced SQL proficiency
n
- Strong understanding of PostgreSQL constraints and referential integrity
n
- Hands-on experience with EXPLAIN / EXPLAIN ANALYZE
n
- Demonstrated production query optimization experience
n
- Strong indexing knowledge, including composite and partial indexes
n
- Practical understanding of PostgreSQL MVCC
n
- Experience with transaction isolation, concurrency, row-level locking and deadlock diagnosis
n
- Experience planning and executing migrations on active production databases
n
- Experience with connection pooling
n
- Experience with backup and recovery strategies
n
- Ability to collaborate with application engineers and translate application requirements into durable data models
n

n

n

PostgreSQL is non-negotiable

n

n





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.

n

n

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 .

n

n

Preferred

n

n
- AWS RDS/Aurora PostgreSQL
n
- pg_stat_statements
n
- PgBouncer
n
- PostgreSQL partitioning
n
- Point-in-time recovery
n
- Large production database migrations
n
- Multi-tenant SaaS data architecture
n
- Financial transaction, payments, investment or ledger-like data models
n
- Immutable/auditable data-history patterns
n
- Fintech, regulated SaaS or digital-asset platforms
n
- Prisma ORM and experience reviewing ORM-generated SQL
n
- Basic Node.js/TypeScript familiarity sufficient to work effectively with backend engineers
n
- Database observability using CloudWatch, Prometheus/Grafana, Datadog or equivalent
n
- Experience using AI-assisted engineering tools while independently validating generated schemas, SQL and optimization recommendations
n

n

n

What You Are Not Expected to Own

n

You do not need to be the primary Node.js application developer. The Senior Backend Engineer owns services, APIs and business logic.

n

You also do not need Solidity or ERC-3643 experience. Blockchain development is a separate specialist function.

n

n

What Success Looks Like

n

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 at 10× or 100× the volume? And how do we change the schema later without disrupting production?

n

n

That is the level of database ownership we're looking for.

📌 Senior PostgreSQL Database Engineer (North Goa)
🏢 MeridianSquare
📍 North Goa