Senior PostgreSQL Database Engineer

What You'll Do

Own Our platform's canonical PostgreSQL data model
Design schemas for investors, identity/KYC, organizations, properties, ownership, transactions, wallets, documents and audit/history records
Define relationships, primary and foreign keys, constraints and appropriate data types
Design tenant-aware data architecture and appropriate tenant-isolation patterns
Establish database-level integrity controls for sensitive financial and ownership records
Design transaction boundaries and consistency guarantees
Handle concurrency using appropriate PostgreSQL isolation and locking strategies
Diagnose and prevent race conditions, lock contention and deadlocks
Design indexing strategies using:
B-tree
composite indexes
partial indexes
GIN/GiST/BRIN where justified
Use EXPLAIN and EXPLAIN ANALYZE to diagnose and optimize production queries
Identify inefficient joins, N+1 access patterns and poor query plans
Review Prisma-generated SQL and identify when raw SQL or database-specific optimization is appropriate
Design safe, backward-compatible zero/low-downtime migrations
Develop migration rollback and recovery strategies
Design database audit/history patterns appropriate for a regulated platform
Establish connection-pooling strategies using PgBouncer or equivalent
Establish database performance baselines and monitoring
Use PostgreSQL statistics and tools such as pg_stat_statements to identify bottlenecks
Plan backup, point-in-time recovery and disaster-recovery strategies
Support database capacity planning as transaction and data volumes increase
Work directly with backend engineers on API-to-schema contracts and transaction behavior


Required Qualifications

4–8+ years of professional database, backend or data-platform engineering experience
Deep hands-on PostgreSQL production experience
Personally designed or significantly owned PostgreSQL schemas for production applications
Strong relational data-modeling skills
Advanced SQL proficiency
Strong understanding of PostgreSQL constraints and referential integrity
Hands-on experience with EXPLAIN / EXPLAIN ANALYZE
Demonstrated production query optimization experience
Strong indexing knowledge, including composite and partial indexes
Practical understanding of PostgreSQL MVCC
Experience with transaction isolation, concurrency, row-level locking and deadlock diagnosis
Experience planning and executing migrations on active production databases
Experience with connection pooling
Experience with backup and recovery strategies
Ability 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 PostgreSQL
pg_stat_statements
PgBouncer
PostgreSQL partitioning
Point-in-time recovery
Large production database migrations
Multi-tenant SaaS data architecture
Financial transaction, payments, investment or ledger-like data models
Immutable/auditable data-history patterns
Fintech, regulated SaaS or digital-asset platforms
Prisma ORM and experience reviewing ORM-generated SQL
Basic Node.js/TypeScript familiarity sufficient to work effectively with backend engineers
Database observability using CloudWatch, Prometheus/Grafana, Datadog or equivalent
Experience 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 at 10× or 100× the volume? And how do we change the schema later without disrupting production?



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