Database Engineer
serevelNew York (NY)
About the role
seRevel is an AI-native POC management platform built by Sales Engineers for Sales Engineers, and all of it lives in Postgres: every POC, every use case, everything the connectors pull in from Salesforce, Gong, Jira and Slack, and everything the AI worker writes back. You will own that database. Schema, performance, migrations, backups, encryption, and the tenant isolation that keeps one company's data invisible to the next. Small team, early stage, and the data model is still yours to shape.
What you will do:
Own schema design for a multi-tenant SaaS: POCs, use cases, customer portals, synced integration data, and the AI outputs built on top of them.
Enforce tenant isolation at the database layer so no query, job, or connector can cross workspace boundaries.
Design and run zero-downtime migrations alongside the engineers shipping the Next.js and Node code that depends on them.
Tune performance where it matters here: connector sync writes, the AI worker's reads, and the queries behind customer-facing pages. Indexes, query plans, connection pooling.
Build and test backup, restore, and recovery. Prove it works before anyone needs it.
Set up encryption at rest, TLS to the database, and least-privilege roles for every service that talks to it.
Plan for growth: partitioning, archiving, and capacity for what happens when the connectors sync ten times the data.
What we are looking for:
Hands-on Postgres in production: schema design, indexing, query tuning, and day-to-day operations.
You have designed and run a multi-tenant data model and can explain the trade-offs you made.
You have shipped migrations on a live system without breaking it, and you have restored from a backup for real, not just configured one.
Comfortable enough in TypeScript and Node to read the code that queries the database and change it when needed.
You write clearly and work well async. We are remote-first.
Nice to have:
Experience with Docker-based deployments and the infrastructure around a Postgres instance.
You have built or maintained connectors that sync third-party data (Salesforce, Jira, Slack, Gong, or similar) into a relational store.
You have been through a security review or compliance audit for B2B SaaS and know what gets asked about the database.
You have been an SE, or worked closely with sales engineering teams, and know what POC data looks like in practice.
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
More like this