Database Platform Engineer

Who actually decided that we should tuck our data (the soul of our organization) away inside a black box we barely have visibility into, let alone influence over? What you actually want is control, direction, oversight, and the certainty that you’re not paying more than you need to.

And yet the opposite keeps happening: data and workloads disappear into a managed cloud service or a container in a Kubernetes cluster, and everyone assumes that means it’s taken care of. Until performance disappoints, the bill climbs, or an AI project runs aground on data nobody ever actually looked at. So the question isn’t whether you put your database in the cloud. It’s who still genuinely understands and manages it once it’s there. Someone you can actually trust with your soul.

The classic DBA kept the database running. The data engineer builds pipelines into the analytics platform. But who takes care of the platform the database itself lives on: the managed cloud service (RDS, Aurora, Cloud SQL, Azure Database for…), the Kubernetes cluster, the operator, the storage underneath it all?

That’s the Database Platform Engineer. Someone who understands the database down to query level, and at the same time masters the modern platform underneath it, whether that’s a container or a managed cloud database. Two worlds that are usually kept apart, united in one discipline.

Ik hoef me nergens meer druk om te maken, het wordt geregeld

Jacob Ordelman

ICT Manager

Databases no longer run on a server under someone’s desk. They run as a managed cloud service (RDS, Aurora, Cloud SQL, Azure Database for…), in containers, on Kubernetes, behind operators, spread across availability zones. The platform has become just as decisive for reliability as the database itself.

And it’s precisely with those managed cloud services that a misunderstanding sits. “Managed” doesn’t mean “optimized.” It means the power stays on in the data center and the patches get applied. That’s where it stops. Nobody’s looking at your queries, your indexes, your data model, or your costs.

The problem: most people only know one side of this. The platform engineer knows everything about pods, storage, and failover, but not why a query is slow or an index is missing. The classic DBA knows that side, but loses their footing the moment the database disappears into a cluster or behind a managed cloud service. That’s the gap where systems fall over and bills climb.

The Database Platform Engineer sits exactly on that boundary.

Wat mij vooral opviel was de daadkrachtige en inhoudelijk sterke opvolging op ons vraagstuk naar een stabiel, toekomstvast en high performing PostgreSQL database setup in GCP.

Fred Kroon

MyWheels

Our engineers work across the full breadth, not locked into one engine or one layer:

• PostgreSQL, MySQL, MariaDB, MongoDB, SQL Server, and Oracle: both management and migration
• Managed cloud databases (RDS, Aurora, Azure Database for…, Cloud SQL): not just switching them on, but actually managing them, tuning them, and steering them on cost
• Databases on Kubernetes with operators like CloudNativePG, including high availability, failover, and persistent storage
• Query and performance tuning down to the level where the cloud bill actually drops
• Observability that looks beyond the infrastructure: not just whether the pod or instance is running, but what’s actually happening inside the database
• Right-sizing and cloud cost management, because we see what a managed service doesn’t show you
• The data foundation underneath your AI applications, so that what you build on top of it actually holds up

We’re a CNCF partner for CloudNativePG and active in the PostgreSQL community. This isn’t theory: it’s what we run in production every day, on-prem, in containers, and on managed cloud alike.

The market pushes you to choose between someone who knows the database and someone who knows the platform. We deliver both in one person, whether your database runs on-prem, in a container, or as a managed cloud service.

That’s the difference. A managed cloud database keeps the engine running and lines up the patches. A platform team keeps the cluster standing. But only once someone understands the database and the platform at the same time can you be sure the whole thing actually holds together, performs, and stays affordable.

At OptimaData, that someone is called a Database Platform Engineer.