Back to jobs

Database Platform Engineer

Pay
Pay not listedSimilar roles state $127K–$190K
Work setting
Not stated
Employment
Full-time — employment source
Employment type in the employer’s posting: FullTime
From the employer’s posting

What you’ll work on

Full posting
  • Build one shared module per database engine covering provisioning, config, monitoring, backups and teardown protection

  • Consolidate databases to one server per engine with per-service roles, dynamic credentials and audit trails

  • Build backup jobs, restore tests, and self-service point-in-time restore and forking in the IDP

  • Enforce forward-only, backward-compatible migrations with schema diffs and expand/contract gating in the pipeline

  • Replace static passwords with short-lived per-service Vault credentials and short-TTL admin escalation via IDP and…

From the employer’s posting
each gets a single shared module covering provisioning, config, monitoring, backups, and teardown protection
you own the move to consolidate databases to one server per engine and the controls that make sharing safe
the backup jobs and the restore tests that prove them, with point-in-time restore and forking as self-service actions in our IDP
forward-only, backward-compatible migrations enforced in the shared pipeline: migration tests on scratch databases, a schema diff on every merge request, and unsafe DDL gated behind an explicit expand/contract acknowledgment
short-lived, per-service credentials from Vault in place of static passwords

What you’ll bring

All qualifications

Core experience

  • 5+ years running Postgres or MySQL in production: replication, failover, backup and restore, connection pooling, and enough scar tissue to distrust a green health check
Qualification wording
5+ years running Postgres or MySQL in production: replication, failover, backup and restore, connection pooling, and enough scar tissue to distrust a green health check

About Hydra Host

Hydra Host is a Founders Fund-backed NVIDIA Cloud Partner building the infrastructure platform that powers AI at scale.

In the employer’s words · Read in context

Apply at Hydra Host

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 16, 2026today
Recorded sightings
1

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

$127K–$190K is typical

The middle half of what similar US postings state. This one doesn’t list pay.

From 2,380 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 6 and day 56.

From 13,902 similar postings that came down. Coming down is not always a hire.

Hydra Host is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • TypeScript
  • Azure
  • ClickHouse
  • Kafka
  • Kubernetes
  • MySQL
  • Redis
  • Terraform
  • Go
  • PostgreSQL
Where the posting names them
- Stateful workloads on an orchestrator (Nomad or Kubernetes) do not scare you - You read HCL, Python, TypeScript, Go, shell, and SQL without complaint — all are in rotation here - You have run database automation in production and know where it breaks: migrations through a connection pooler, instances racing the same migration, lock contention, credential rotation that drops the pool, provider quirks that turn a rename into a destroy. You design so a failed run never leaves a database half-migrated, credential-less, or unrecoverable.
- You have designed forward-only, backward-compatible migration flows (Drizzle, Prisma, Alembic, Atlas, Flyway, or similar) and can explain why "just run the down migration" is not a rollback strategy - You have run both managed database platforms (Aiven, RDS, Cloud SQL, Redis Cloud) and self-hosted databases, and can defend a choice between them for a given workload - Strong HashiCorp Vault experience: the database secrets engine, policies, auth methods, lease lifecycle
- Strong HashiCorp Vault experience: the database secrets engine, policies, auth methods, lease lifecycle - You have built OIDC-backed access to infrastructure with Zitadel, Keycloak, Azure AD, Okta, or similar - Stateful workloads on an orchestrator (Nomad or Kubernetes) do not scare you
One pattern per engine - Dev Patterns: Postgres, MySQL, Redis, Clickhouse, and the next engine someone adopts: each gets a single shared module covering provisioning, config, monitoring, backups, and teardown protection. A dev team invokes from our IDP, not a recipe a platform engineer follows. - Database Modules in IaC Catalog: manage and consolidate the ones we have; build more as needed.
- Restore-tested backup tooling: restic, pgBackRest, WAL-G - Data infrastructure beyond OLTP: ClickHouse, Kafka, CDC/Debezium - You have produced compliance evidence for database access or change management (SOC 2 or similar)
- You have built OIDC-backed access to infrastructure with Zitadel, Keycloak, Azure AD, Okta, or similar - Stateful workloads on an orchestrator (Nomad or Kubernetes) do not scare you - You read HCL, Python, TypeScript, Go, shell, and SQL without complaint — all are in rotation here
Preferred - Nomad and nomad-pack, not just Kubernetes - Zitadel, or another self-hosted OIDC provider you ran yourself
- Self-starting attitude and extreme ownership — you see a gap in the platform, you close it - 5+ years running Postgres or MySQL in production: replication, failover, backup and restore, connection pooling, and enough scar tissue to distrust a green health check - You automate database lifecycle with Terraform and can tell from a plan when it is about to eat data
- 5+ years running Postgres or MySQL in production: replication, failover, backup and restore, connection pooling, and enough scar tissue to distrust a green health check - You automate database lifecycle with Terraform and can tell from a plan when it is about to eat data - You have designed forward-only, backward-compatible migration flows (Drizzle, Prisma, Alembic, Atlas, Flyway, or similar) and can explain why "just run the down migration" is not a rollback strategy
- PgBouncer or another pooler sitting in front of automated credential rotation - Aiven: its Terraform provider, forking, and PITR. - Restore-tested backup tooling: restic, pgBackRest, WAL-G

Your next step

Complete your application on jobs.gohire.io. The employer’s form will show what is required.

Already applied? Track this application

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 7% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 2. The fewest in a week was 861, the most 1,353, and the latest week had 1,335.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Job description

View original posting ↗

About Hydra Host

Our Company

Hydra Host is a Founders Fund-backed NVIDIA Cloud Partner building the infrastructure platform that powers AI at scale. We connect AI Factories, high-performance GPU data centers, with the teams that depend on them: research labs training foundation models, enterprises running production inference, and developer platforms that need compute capacity on demand. 

The Role

Hydra Host's Platform Team owns our internal developer portal: change management, full-stack release candidates, self-service rollbacks, and disaster recovery. Database management is where those promises go to die. A rollback that ignores the schema is a lie; a DR plan that ignores the data is a wish. We are hiring the engineer who makes every lifecycle promise hold for every database we run. As the company scales, database management becomes central to the integrity and security of every application across our footprint.

This is a pattern-building role. Every database already deploys through CI/CD with backups and migrations, integrated with our automated secrets and identity engines. You will develop those patterns to secure, consolidate, optimize, and scale each database we run. You will own the canonical patterns for how dev teams provision databases, credentials, backups, restores, migrations, and reversions, and you will build the self-service features in our IDP that dev teams use to manage them. You will also be the subject matter expert on all things database: current on business needs and industry standards, with a clear opinion on every architecture question.

What You'll Own

One pattern per engine

  • Dev Patterns: Postgres, MySQL, Redis, Clickhouse, and the next engine someone adopts: each gets a single shared module covering provisioning, config, monitoring, backups, and teardown protection. A dev team invokes from our IDP, not a recipe a platform engineer follows.
  • Database Modules in IaC Catalog: manage and consolidate the ones we have; build more as needed.
  • Consolidation: you own the move to consolidate databases to one server per engine and the controls that make sharing safe: per-service roles and grants in code, dynamic credentials per service, network allowlists, per-tenant restore, and an audit trail per database.
  • Cost Scaling: database spend should scale with load, not with the service count.
  • DB hosting architecture: you own the decision where a database should be hosted: managed service or self-hosted, how and why.
  • Protection of database content: survival beyond deletion events; rollbacks; access; and everything else related to reliability and security of database content.
  • Change Management: forward-only, backward-compatible migrations enforced in the shared pipeline: migration tests on scratch databases, a schema diff on every merge request, and unsafe DDL gated behind an explicit expand/contract acknowledgment.
  • Backup and Recovery: the backup jobs and the restore tests that prove them, with point-in-time restore and forking as self-service actions in our IDP.
  • Access: short-lived, per-service credentials from Vault in place of static passwords; human admin access as a short-TTL escalation through our IDP and Zitadel; roles and grants in code; an audit trail that answers who touched which database, when, with what credential.

Requirements

  • Self-starting attitude and extreme ownership — you see a gap in the platform, you close it
  • 5+ years running Postgres or MySQL in production: replication, failover, backup and restore, connection pooling, and enough scar tissue to distrust a green health check
  • You automate database lifecycle with Terraform and can tell from a plan when it is about to eat data
  • You have designed forward-only, backward-compatible migration flows (Drizzle, Prisma, Alembic, Atlas, Flyway, or similar) and can explain why "just run the down migration" is not a rollback strategy
  • You have run both managed database platforms (Aiven, RDS, Cloud SQL, Redis Cloud) and self-hosted databases, and can defend a choice between them for a given workload
  • Strong HashiCorp Vault experience: the database secrets engine, policies, auth methods, lease lifecycle
  • You have built OIDC-backed access to infrastructure with Zitadel, Keycloak, Azure AD, Okta, or similar
  • Stateful workloads on an orchestrator (Nomad or Kubernetes) do not scare you
  • You read HCL, Python, TypeScript, Go, shell, and SQL without complaint — all are in rotation here
  • You have run database automation in production and know where it breaks: migrations through a connection pooler, instances racing the same migration, lock contention, credential rotation that drops the pool, provider quirks that turn a rename into a destroy. You design so a failed run never leaves a database half-migrated, credential-less, or unrecoverable.

Preferred

  • Nomad and nomad-pack, not just Kubernetes
  • Zitadel, or another self-hosted OIDC provider you ran yourself
  • PgBouncer or another pooler sitting in front of automated credential rotation
  • Aiven: its Terraform provider, forking, and PITR.
  • Restore-tested backup tooling: restic, pgBackRest, WAL-G
  • Data infrastructure beyond OLTP: ClickHouse, Kafka, CDC/Debezium
  • You have produced compliance evidence for database access or change management (SOC 2 or similar)

 

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

United States

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.