Well, that might be a long post…..lol

I’ve heard it for years.

  • “DBAs are disappearing.”
  • “Cloud killed the DBA.”
  • “Automation replaced them.”
  • “AI will finish the job.”

And every time I hear it, I smile a little, not because the industry isn’t changing, but because my entire career has been about adapting to change, and that started long before technology.

It started in sports, basketball.

Before Databases, There Was Competition

I grew up competing. Not casually. Not recreationally. Competing.

  • Training when nobody was watching
  • Losing and having to show up again
  • Winning and realizing the next level would be harder
  • Learning that talent opens the door discipline keeps you there

Sports shaped how I think more than any technical certification ever did.

You learn early:

  • To win, to lose
  • Politics
  • Group dynamics, leadership, profissionalism
  • You are not entitled to the next level
  • You earn it
  • And when you get there, you start over

Every jump in competition feels the same:

  • You were dominant yesterday
  • Today, you’re average
  • Tomorrow, you might not even make the cut

That cycle of humility and growth became normal to me.

And I didn’t realize how much that mattered until my second professional career started unfolding.

I Tried to Be a Developer First

When I entered tech, I thought I would become a developer.

That was the plan. Write code. Build applications. Ship features and I quickly discovered something about myself.

I could code, but my brain didn’t light up there.

What pulled me in was different:

  • Why did this fail?
  • What happens if the system crashes?
  • Where’s the bottleneck?
  • How do we recover cleanly?
  • What breaks under pressure?

While others were building features, I was dissecting failure modes.

That’s when I realized something important: My mind leaned operational. In athletics, I lived for the hard game days, not to the grind to get there.

That awareness moved me into database administration. Not because I couldn’t develop. But because I knew where I was strongest.

Sports had already taught me to assess myself honestly.

  • Play where you’re most effective
  • Train where you’re weakest
  • Move where you can compete

The DBA Years: Discipline Under Pressure

Being a DBA felt like competition again.

No applause when everything works.
High visibility when it doesn’t. Talking about pressure…

Backups had to be tested. Never a priority until you needed it.
Recovery had to be rehearsed. Again.
Replication had to be monitored. DataGuard on early days was fun.
Performance had to hold under stress.

You don’t get credit for “nothing happened.” That’s why there was a joke in the community that sometimes we need to break something. :-)

But when something does happen, it’s game time. Did you say “GAME TIME”??? Sing me up…

And in those moments, athletics paid dividends.

  • Pressure didn’t feel foreign
  • Noise didn’t shake me
  • Focus narrowed

You execute what you practiced.

That phase built something deep:

  • Respect for failure
  • Respect for preparation
  • Respect for data

If you lose data, you don’t just lose a match. You lose trust.

When the Field Expanded

Then the industry changed. Stability wasn’t enough. Data had to move.

  • Real-time dashboards
  • Streaming pipelines
  • Multi-cloud architectures
  • APIs everywhere
  • Distributed systems that don’t forgive simplistic view

The database wasn’t disappearing. But it wasn’t the entire field anymore.

So I moved into data engineering and it felt exactly like moving up a competitive division.

  • New players
  • New speed
  • New complexity
  • New humility

Suddenly, the problems weren’t just about tuning queries. They were about designing systems that survive distributed failure.

But the fundamentals carried.

  • Understanding transactions
  • Consistency
  • Recovery
  • Operational discipline

Sports had trained me for level transitions. DBA work had trained me for system responsibility. Data engineering stretched both.

The Current Arena: Product (Still in Progress)

Product management is the newest arena for me and it’s not a finished chapter. It’s ongoing.

I stepped into product not because technology bored me but because I wanted to influence what gets built, not just how it’s built.

But this field is different.

  • There is no clean scoreboard
  • There is no immediate feedback loop like uptime metrics
  • Influence takes time
  • Alignment is earned
  • Vision must be communicated, not just understood

Some days I feel strong in it, other days I feel like the rookie again, and I recognize that feeling.

Some days I listen to engineers and think:
We’re solving the wrong problem.

Other days I listen to customers and think:
They have no idea how complex this really is.

The job of a product manager is to live in that tension, turning customer intent into something engineers can realistically build.

It’s the same feeling from sports. The same feeling from stepping into distributed systems after years in database operational world.

Growth feels like discomfort.

The athlete in me knows:

  • Stay in the discomfort
  • Train
  • Improve
  • Repeat

So yes, product manager is a work in progress, and I’m okay with that.

So back to the original question… Is the DBA Career Dead?

No. But the static DBA is:

  • The DBA who refuses to evolve
  • The DBA who stays instance-focused in a distributed world
  • The DBA who ignores automation and cloud
  • The DBA who thinks AI eliminates the need for discipline

That version is fading. But the core DBA mindset?

It’s more relevant than ever. In the AI era, data is the raw material and AI amplifies whatever data quality you feed it.

  • If the data is inconsistent, AI scales inconsistency
  • If governance is weak, AI scales risk
  • If performance is fragile, AI pipelines collapse

The AI world doesn’t eliminate database thinking. It depends on it. But it requires evolution.

What Sports Taught Me About This

The reason I never felt threatened by “DBA is dead” narratives is simple:

I was trained to move levels.

Athletics wired me to expect change:

  • To adapt
  • To rebuild
  • To compete again

My career isn’t a sequence of exits. It is a sequence of expansions.

From stability. To movement. To direction.

And I’m still expanding.

  • Still building
  • Still training
  • Still uncomfortable at new levels
  • Still competing

Final Thought

The DBA career isn’t dead. It’s evolving, just like every competitive field does. The ones who stay still fall behind. The ones who adapt move up. The question was never whether the DBA would survive.

The real question is: Are you willing to evolve when the game changes? Because it always does.

A Message to the Young DBAs

If you’re early in your DBA career and you keep hearing that the role is dying — don’t panic.

Every generation hears that about something.

The truth is simpler:

Foundations don’t die.
They evolve.

If you are learning:

  • How transactions really work
  • Why consistency matters
  • What failure looks like under pressure
  • How recovery actually happens
  • How performance behaves at scale

You are not learning something obsolete. You are learning the physics of data, and physics doesn’t go out of style.

Yes, the tools will change.
Yes, cloud will abstract parts of your job.
Yes, automation and AI will remove repetitive tasks.

Good. That means you get to level up. Don’t cling to the manual work. Cling to the thinking.

  • Learn cloud
  • Learn distributed systems
  • Learn how data moves
  • Understand AI pipelines
  • Stay curious

But never abandon the discipline that DBA work builds in you.

Because in a world rushing toward automation and AI, the people who deeply understand how data behaves under pressure will be the ones designing the future.

Not just operating it.

I started trying to be a developer. I discovered I was wired operationally. That awareness led me into databases. Databases led me into distributed systems. Distributed systems led me into product.

None of those steps erased the previous one. They stacked.

Your career doesn’t have to be linear. It has to be evolving.

So no , the DBA career is not dead.

It’s a starting point for people willing to grow beyond it.

  • Train
  • Adapt
  • Level up

The game will keep changing. Ai is here to challenge you like never before.

Make sure you do too.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.