Lv.1 IntroRDBMS(General)

2026.04.1920 min readLv.1 Intro

SeriesDA? DBA? DBE? — Understanding the roles · Part 3/4View series hub

DA? DBA? DBE? — Part 3: Career Roadmap (How to Get Started and How Far Can You Go?)

Breaking into the field as a new-hire DBA is, in practice, a narrow path. This article compares three realistic entry routes — backend developer, SI engineer, and DA entry-level — along with their trade-offs for each target role, then lays out a concrete stage-by-stage growth roadmap from junior to senior. It guides you through domestic and international certifications by recommended order per role, and covers DBA salary data from the Jumpfit 2025 report alongside the key variables that most reliably lift compensation. Finally, it maps how natural role transitions between DA, DBA, and DBE work, and explains why keeping your options open is the stronger long-term strategy.

Series Overview

• Part 1 — Concepts: What Do DA, DBA, and DBE Actually Do?
• Part 2 — Real-World Comparison: How They Differ in Practice
• Part 3 — Career Roadmap: How to Get Started and How Far Can You Go? (current)
• Part 4 — The 2026 Landscape: Will These Roles Survive AI and Cloud? (upcoming)

Table of Contents

1. Introduction
2. The Reality: Why "Junior DBA" Hires Are Rare
3. Three Entry Routes
4. Stage-by-Stage Growth Roadmap
5. Certifications: A Complete Guide
6. 2025 Real Salary Data
7. Can You Move Between Roles?
8. Wrap-Up — Part 3 Summary

1. Introduction

"I want to become a DBA — where do I even start?"

It's the question people new to data roles ask most often.

And it's also the one working professionals hesitate to answer honestly, because there is no single right answer.

Part 3 tackles realistic entry paths, a stage-by-stage growth roadmap, the certifications worth pursuing, and current compensation — all in one place.

2. The Reality: Why "Junior DBA" Hires Are Rare

Landing a DBA role straight out of school is difficult. The work is too consequential to hand to someone who hasn't seen production failure, so the market leans heavily toward experienced hires.

Working DBAs explain the dynamic clearly:

"There's really no good answer for DBA new-grads right now. Startups need a senior who can fix a broken database from day one. New-grad openings exist at a handful of large enterprises, financial firms, and major tech companies — and that's about it."

— RastaLion.dev, working DBA blog

This isn't a reason to give up.

The narrow gate is "entering directly as a junior DBA," not "becoming a DBA." In many cases an indirect path is more reliable.

What about DA and DBE? DA entry is comparatively more open — roles like modeling assistant or data standards specialist exist for new hires, mainly at large enterprise and financial data-governance teams and SI modeling divisions. DBE new-grad hiring is similarly uncommon; most DBEs start as backend engineers and transition after accumulating DB platform experience.

3. Three Entry Routes

🛤️ Route A — Backend / Full-Stack Developer → DBA or DBE

The most natural path if DBE is your target. Valid for DBA transitions too.

Many future DBAs begin as database developers or data analysts. Starting as a backend or full-stack developer lets you build DB design and operations experience naturally through product work — experience that carries real weight when you pivot to DBA or DBE.

Backend Developer (1–3 years)
    → SQL query optimization experience
    → DB design and operations experience
    → Transition to DBA / DBE

Advantage: You develop coding skills alongside DB skills — the combination most in demand for "coding DBAs" post-2026.

Drawback: The gap between your job title and target role can make it hard to stay motivated early on.

🛤️ Route B — SI Engineer → DBA

The most direct path if DBA is your goal.

A common approach is earning a certification from an Oracle-authorized training organization, then starting as an SI engineer. In SI environments you encounter a variety of DBMS platforms and business domains across projects, accumulating hands-on experience relatively quickly.

SI DB Engineer (1–3 years)
    → DBMS installation / configuration experience
    → Transition to operations DBA or specialist consultant

Advantage: You see many environments in a short time.

Drawback: Frequent project rotations can make it hard to go deep on any single system.

🛤️ Route C — DA Entry → DBA or DBE

Best if DA is your target, or if you want to build business-domain understanding first.

For those drawn to data standards and modeling, starting as a DA is a solid choice. Expanding from DA into physical design and operations leads toward DBA; expanding into architecture and system design leads toward DBE.

Data Modeler / DA (2–4 years)
    → Logical / physical design experience
    → Add operations experience → DBA
    → Expand into architecture / system design → DBE

Advantage: Strong business-domain understanding, with a path toward EA (Enterprise Architect).

Drawback: If you stay in modeling without gaining production experience, your options narrow.

Routes at a Glance

No route is "perfectly set from the start." What matters is getting close to DB work from your first job.

4. Stage-by-Stage Growth Roadmap

📍 Stage 0 — Foundation (Pre-employment)

At this stage, understanding how a DB engine actually works matters more than collecting certifications.

One of the most important things for a DBA is prioritizing a genuine understanding of the fundamentals — how the DB engine works, how data is stored, how the query processor operates. These are the most basic yet most essential areas.

Recommended starting resources by stack:

• MySQL → Real MySQL 8.0 (highly recommended)
• Oracle → Oracle authorized training + OCP certification
• PostgreSQL → Official docs + Korean translations

Goal: SQL basics → index concepts → reading execution plans → basic tuning

📍 Stage 1 — Junior (0–3 years)

In this phase, encountering as many incidents as possible is your greatest asset.

• Pick one DBMS and go deep (Oracle or MySQL / PostgreSQL)
• Master core operations: backup/restore, account management, monitoring
• Build the habit of analyzing slow queries
• Strengthen Linux fundamentals (ps, top, iostat, netstat, etc.)

"Unlike a developer where creativity and logic drive you, a DBA needs experience grounded in precise theory. Theory alone isn't enough, and half-baked experience just creates incidents."

— Remember Community, working DBA

📍 Stage 2 — Mid-level (3–7 years)

Real differentiation starts here.

• Expand to multiple DBMS: A MySQL engineer who adds PostgreSQL, MongoDB, and Redis sees a significant jump in market value.
• Adapt to cloud environments: Gain managed DB operations experience — AWS RDS, Aurora, GCP Cloud SQL, etc.
• Add automation skills: Write automation scripts in Python + Bash.
• Build a monitoring stack: Set up Prometheus + Grafana + Alertmanager hands-on.

As cloud and microservices architectures reshape how services are built, the DBA role evolves with them. Knowing versus not knowing the new environment creates an extreme difference.

📍 Stage 3 — Senior (7+ years)

Seniors need judgment and communication as much as technical depth.

• Lead DB architecture design: sharding strategy, replication configuration, disaster recovery plans
• Own technology adoption decisions: which DB to introduce, when, and how
• Serve as the technical coordination bridge between engineering and infrastructure teams
• Onboard junior DBAs and write internal guides

At this stage, paths diverge:

• Operations specialist → DB Architect, Principal DBA
• Expand into development → DBE, Platform Engineer
• Expand into business → DA, EA (Enterprise Architect), Data Consultant

5. Certifications: A Complete Guide

Certifications aren't proof of skill — treat them as "evidence of commitment to learning." That said, they do make a real difference at resume screening and salary negotiation.

🇰🇷 Korean National Certifications (KDATA / HRDK)

SQLD and ADsP typically take 1–2 months; SQLP, ADP, and the Big Data certification require 3–4+ months.

🌐 International Certifications

Recommended Certification Order

6. 2025 Real Salary Data

Certifications and roadmap covered — now let's talk money.

According to the 2025 Developer Salary Report published by Jumpfit (Saramin's developer recruitment platform, released January 2026, based on data from over 10,000 job-changers in 2025), DBA compensation breaks down as follows.

📊 DBA Salary Overview (Jumpfit 2025 Report)

In the senior developer salary rankings for 10+ years of experience, DBA came in at approximately ₩73.53 million (~$55K USD), placing it in the top tier alongside blockchain, AI, and big data engineers.

At the senior level, the extreme shortage of professionals who can handle architecture design, security, and large-scale service operations drives premium compensation.

What about DA and DBE? The Jumpfit report tracks DBA separately; comparable figures for DA and DBE were not publicly disclosed. In the field, senior DAs who transition into data consulting or EA roles tend to reach compensation levels comparable to or exceeding senior DBAs. Senior DBEs are increasingly commanding above-DBA market rates as demand for database platform engineering grows.

💡 Key Variables That Drive Compensation

Beyond years of experience, several factors consistently lift salaries.

① Multi-DBMS Skills

A DBA who handles Oracle alone versus one who covers Oracle + MySQL + PostgreSQL + MongoDB commands a very different market value. That said, shallow breadth across everything is less valuable than a T-shaped profile: deep in one, broad across the rest.

② Cloud Experience

Managed DB operations experience on AWS, GCP, or Azure is now a standard preferred requirement in job postings as of 2026.

③ Coding Ability

A DBA who can write automation scripts in Python or Bash has a clear edge in salary negotiation. As cloud environments and open-source DBs like MySQL grow their share, more organizations are requiring engineering skills from their DBAs.

④ Finance / Enterprise Background

At the same seniority level, experience operating high-volume DBs at a financial institution or large enterprise commands a significant premium when changing jobs.

7. Can You Move Between Roles?

One of the advantages of data roles is that transitions between them are relatively natural.

• DBA → DA: Expanding into modeling and standards based on operations experience. The most common transition in practice.
• DBA → DBE: Adding coding skills to move into platform engineering.
• DA → Data Consultant: Deep design experience across multiple domains opens a path into consulting.
• DBE → Data Engineer: A growing interest in pipelines and ETL leads naturally toward data engineering.

8. Wrap-Up — Part 3 Summary

• Direct entry as a "junior DBA" is a narrow gate. An indirect route (backend → DBA) is more reliably achievable.
• Certifications are markers of commitment, not proof of skill — understanding how a DB engine actually works is the real differentiator.
• Senior DBA compensation exceeds ₩70 million; finance/enterprise veterans can reach ₩100 million+.
• The highest-leverage variables are multi-DBMS skills + cloud experience + coding ability.
• Transitions between DA, DBA, and DBE are natural. Keeping your direction flexible and accumulating diverse experience is the stronger long-term play.

Next up, Part 4: The 2026 Outlook — how AI and cloud are reshaping these roles, and what it takes to stay relevant.

References

• A DBA's Perspective on Data Roles — RastaLion.dev
• Reflections on a Recent DBA Job Search — RastaLion.dev
• Career Change to DBA: Considerations — WorkingUS.com
• 6 Things You Must Know to Become a DBA — JobIndex
• Ask a Working DBA — Remember Community
• 2025 Data Certification Guide — FanRuan
• Saramin Jumpfit 2025 Developer Salary Report — Brand News
• Korea Data Industry Promotion Institute (KDATA) Certification — kdata.or.kr
• AWS Certified Database — Specialty — aws.amazon.com/certification/certified-database-specialty/
• GCP Professional Data Engineer — cloud.google.com/learn/certification/data-engineer