🎁 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 →
Why Harvey At Harvey, we’re transforming how legal and professional services operate. By combining frontier agentic AI, an enterprise-grade platform, and deep domain expertise, we’re reshaping how critical knowledge work gets done for decades to come. This is a rare chance to help build a generational company at a true inflection point. We have strong product-market fit and world-class investor support. We’re scaling fast and defining a new category in real time. The work is ambitious, the bar is high, and the opportunity for growth — personal, professional, and financial — is unmatched. Our team moves fast, takes ownership, and is deeply committed to the mission — operating with intensity, staying close to our customers, and pushing each other for excellence. We live by three values: Decisiveness, Simplicity, and Job's Not Finished. We act quickly on clear judgment over perfect information, we believe simplicity is what scales, and we're never satisfied with where we are. If you want to do the best work of your career alongside people who share that drive, we'd love to build with you. At Harvey, the future of professional services is being written today — and we’re just getting started. Role Overview As a Staff Database Engineer on the Engineering team at Harvey, you will define how our database infrastructure operates and evolves across our legal AI platform. Harvey runs a global fleet of PostgreSQL databases spanning multiple regions and availability zones. You’ll own the technical strategy for this fleet—setting the standards for migration governance, driving architecture decisions for multi-region scaling, and establishing the operational practices that keep our data layer reliable as we grow. This is a leadership role with deep hands-on expectations. You’ll partner directly with Principal and Staff Engineers on infrastructure roadmap decisions while also being the person who can diagnose a replication lag spike at 2am. You’ll build the migration review framework, define the tooling strategy, and raise the bar for how the entire engineering organization thinks about database safety and performance. This role is based in San Francisco, CA. We use an in-person work model and offer relocation assistance to new employees. What You'll Do Migration Governance – Own the migration governance framework end-to-end—design the review workflow, CI gate checks, automated rollback procedures, and fleet-wide deployment sequencing that makes safe migrations the default across the org Architecture & Scaling – Drive the technical strategy for Harvey’s global database fleet—multi-region replication design, capacity planning, sharding and partitioning approaches, and fleet-wide observability as we scale into new markets Reliability & Performance – Own database reliability and performance at the fleet level—monitoring replication health, optimizing query performance, tuning vacuum and connection management, and building the alerting that gives us confidence across all production environments Platform & Tooling – Build self-service tooling and developer guardrails—migration dry-runs, schema diff previews, automated health checks, performance regression detection—so engineering teams can move fast without bottlenecking on a single DBA Incident Leadership – Lead database incident response and drive systemic improvements—triage production issues, run post-incident reviews, and turn lessons learned into durable process and tooling fixes Even Better If You Can Security & Compliance – Partner with Security and Compliance to design and enforce data-layer controls for SOC 2, GDPR, and data residency requirements—access controls, audit logging, encryption standards, and data lifecycle policies Strategic Partnership – Represent database engineering in vendor evaluations, build-vs-buy decisions, and technology strategy discussions with engineering leadership Team Building – Shape the database engineering function at Harvey—define the operating model, set the hiring bar, mentor engineers on database best practices, and build the culture where teams proactively think about data safety What You Have 10+ years of hands-on experience in database administration, database reliability engineering, or infrastructure engineering with PostgreSQL as your primary database, with demonstrated staff-level scope—you’ve set standards across teams, not just operated within one Expert-level PostgreSQL knowledge (required)—WAL mechanics, vacuum tuning, logical and physical replication, partitioning strategies, and the ability to debug production issues others can’t. PostgreSQL is our core database and deep fluency is non-negotiable Track record of building migration governance systems—not just reviewing migrations, but designing the frameworks, tooling, and organizational processes that make safe migrations the default Experience architecting database infrastructure for multi-region, high-availability environments—replication topologies, failover automation, and data consistency trade-offs at fleet scale Deep fluency with database observability—you’ve built monitoring strategies using Datadog, pganalyze, or custom instrumentation, and you know which metrics actually predict incidents Experience leading database major version upgrades (e.g., PostgreSQL 14 → 16) or sharding initiatives in production with zero downtime Proven ability to influence technical direction across teams without direct authority—you’ve written RFCs, set standards, and changed how an engineering organization thinks about database operations Proficiency with cloud database services at scale (Azure Database for PostgreSQL, GCP Cloud SQL, or AWS RDS/Aurora) and infrastructure-as-code (Terraform, Pulumi) Clear communication across audiences—you can present a database architecture decision to the VP of Engineering and explain a migration risk to a junior developer with equal clarity Bonus Strong software engineering skills (Python, Go, or similar)—you build production-grade tooling and automation, not one-off scripts Exposure to vector databases, embedding storage, or adjacent systems (Redis, Elasticsearch, Kafka) relevant to AI/ML workloads in regulated industries Background building or leading a database engineering function from scratch — defining the team charter, hiring, and operating model Compensation $190,720 - $290,000 Depending on your location, an Applicant Privacy Notice may apply to you. You can find all of our Applicant Privacy Notices [ here ]. Harvey is an equal opportunity employer and does not discriminate on the basis of race, gender, sexual orientation, gender identity/expression, national origin, disability, age, genetic information, veteran status, marital status, pregnancy or related condition, or any other basis protected by law. We are committed to providing reasonable accommodations to applicants with disabilities, and requests can be made by emailing accommodations@harvey.ai
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.