DBA: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

Top 5: cloud, sql, postgresql, aws, mysql. DBMSes: PostgreSQL (main demand in CIS — import substitution; Postgres Pro), Oracle (legacy enterprise), MS SQL Server, MySQL / MariaDB; increasingly — NoSQL (MongoDB, Redis) and analytical DBMSes (ClickHouse — very popular in CIS). Fault tolerance: Patroni (PostgreSQL HA cluster — the standard), repmgr, PgBouncer / Odyssey (connection pooling). Backup: pgBackRest, WAL-G, Barman, PITR (point-in-time recovery). Monitoring: Prometheus + exporters, pgwatch, Percona Monitoring, Zabbix, Grafana. Skills: deep SQL and query plan analysis (EXPLAIN ANALYZE), indexes (types, when which one), partitioning, replication (physical / logical), DBMS parameter tuning, VACUUM / autovacuum and fighting bloat in PostgreSQL, locks and transactions, security (roles, permissions, encryption, audit). Infrastructure: Linux (mandatory), scripting (Bash / Python), networks, for DBRE — Ansible / Terraform (infrastructure as code), Docker / Kubernetes and DB operators. Knowledge of DBMS internals (how the planner works, MVCC, WAL) is valued higher than memorized commands.

For a DBA in CIS the answer in 2026 is largely predetermined by import substitution. PostgreSQL — the main choice: open, powerful, actively developed; in Russia — mass migration from proprietary DBMSes, there's a domestic vendor Postgres Pro, regulator and state procurement requirements push toward Postgres. PostgreSQL DBA expertise is now the most in demand and will continue to grow. Oracle — a powerful enterprise DBMS with huge legacy in banks and large corporations; knowledge of Oracle is still valuable (legacy hasn't gone anywhere, specialists are few), but it's a displaced technology — building a career around it is risky, rather as an additional asset. MS SQL Server — strong in the corporate segment, also under pressure from import substitution in RF. MySQL / MariaDB — widely used in web, simpler than Postgres, but less interesting for a serious DBA career. NoSQL and analytics: ClickHouse (analytical DBMS, very popular in CIS), MongoDB, Redis — a useful addition. Strategy 2026: bet on PostgreSQL as the main specialization; ClickHouse — as a strong addition; Oracle / MS SQL — if you get a legacy project (pays well, but not the basis of a career).

DBRE (Database Reliability Engineer) — the modern evolution of the DBA role, emerging under the influence of DevOps and SRE culture. Classic DBA largely works «by hand»: manually configures servers, performs operations, reacts to incidents, often perceived as a function separate from development — a «gatekeeper». DBRE applies the SRE engineering approach to databases: infrastructure as code (DB configuration, clusters — via Terraform / Ansible, not by hand), automation of routine operations, observability (metrics, SLO for DB), self-service for developers (instead of «file a ticket to DBA»), reliability through automation, not through heroism. DBRE is closer to development and DevOps, codes more, thinks in scaling processes. In practice: the boundary is blurred, many «DBA» vacancies essentially require a DBRE approach. The 2026 trend is unambiguous — toward DBRE: manual administration scales poorly, clouds and Kubernetes operators automate classic DBA tasks. Conclusion for career: pure «clicking» DBA is gradually less common; growth is worth pursuing toward DBRE — automation, IaC, observability, owning the DBMS at the level of understanding internals. This is also paid higher.

DBA work is divided into two large profiles (in small companies one person combines them, in large ones — different roles). Production DBA — operations of live databases: configuration and support of DBMS servers, backup and recovery (and regular verification that backups actually restore), replication and fault tolerance (HA clusters, failover), monitoring and incident response, updates and patching, security (access, encryption, audit), capacity planning, migrations. Focus — availability and reliability 24/7. Development DBA — supporting development: schema design, query optimization (plan analysis, indexes, rewriting slow queries), consulting developers, migration review, data modeling. Focus — performance and quality of work with data. Cloud DBA — managed DBs in the cloud (the cloud takes on part of the routine, but configuration, optimization, cost, security remain). DBRE — connects all this with automation and an engineering approach. The general essence of the role: a DBA is an engineer responsible for ensuring data is available, intact, protected and fast; a DBA's mistake (lost backup, fallen cluster) costs the business very dearly — hence the level of requirements and the level of pay.

Yes, 54% of DBA vacancies — remote or hybrid. Database administration is done well at a distance (server access via secure channels, monitoring via dashboards). Nuance — part of banks, fintech and public sector for security reasons and regulatory requirements prefer office or hybrid (especially for access to live DBs with sensitive data). Russian large companies offer different formats. English — needed for the international market and documentation. The move toward DBRE (automation, IaC) makes the role even more remote-friendly.

DBA rarely is the first role — people more often come from system administration, backend development or operations. Roadmap: 1) SQL — thoroughly: queries of any complexity, JOIN, window functions, aggregations; then DDL, transactions, ACID. 2) PostgreSQL as the main DBMS (priority for CIS) — installation, configuration, roles and permissions, configuration. 3) Internal structure — how the query planner works, MVCC, WAL, VACUUM / autovacuum; this distinguishes a DBA from «a person who knows commands». 4) Optimization — EXPLAIN ANALYZE, reading plans, indexes (types and when to apply), finding and fixing slow queries. 5) Backup and recovery — pgBackRest / WAL-G, PITR; you must learn not only to make a backup, but also to recover from it. 6) Replication and fault tolerance — streaming and logical replication, HA via Patroni. 7) Monitoring — Prometheus + exporters, Grafana, pgwatch. 8) Linux and scripting (Bash / Python) — a mandatory base. 9) For moving into DBRE — Ansible / Terraform, Docker / Kubernetes, DB operators. 10) Pet project: deploy a fault-tolerant PostgreSQL cluster with Patroni, set up pgBackRest backups, monitoring, conduct a training failover and recovery. Resources: official PostgreSQL documentation (one of the best in the industry), Postgres Professional courses (some free), books on PostgreSQL administration, DBMS materials on Otus / Slurm. In a DBA resume, practical cases (recovery, optimization, migration) are valued, not a list of DBMSes.

11 active open DBA vacancies in the Zorky CRM sample — a narrow but steadily in-demand specialization. Geography: Russia / remote / Poland. Sources: hh.ru («database administrator», «DBA», «PostgreSQL DBA», «DBMS operations engineer»), Habr Career, getmatch, LinkedIn (international segment), Telegram (PostgreSQL and DBA communities, specialized channels). Demand concentrates in fintech, telecom, public sector and large products; in CIS 2026 the main driver is import substitution and the wave of migrations to PostgreSQL, which has separately raised demand for Postgres DBAs. Senior vacancy closing time — 6-12 weeks (shortage of qualified specialists). Shortage and regulatory pressure make the segment stable and well-paid; vacancies are few in number, but they're «expensive».

Senior DBA — an engineer responsible for critical data infrastructure. DBMS at the level of internals: deep understanding of the main DBMS (for CIS — PostgreSQL) — query planner, MVCC, WAL, locking mechanisms, VACUUM / autovacuum and fighting bloat, index structure. Performance: fine tuning of DBMS and OS parameters, diagnosis and optimization of slow queries, plan analysis, index strategy, partitioning, optimization for specific load. Reliability: designing fault-tolerant clusters (Patroni), replication strategies, thoughtful backup with regular recovery verification, PITR, disaster recovery, RPO / RTO calculation and compliance. Scaling: partitioning, sharding, connection pooling, read replicas, capacity planning. Security: access model, encryption, audit, compliance with regulator requirements. Operations: monitoring and alerting, incident analysis, safe updates and migrations under load (without downtime). Infrastructure: Linux at a good level, scripting (Bash / Python), networks, storage. DBRE skills: infrastructure as code (Ansible / Terraform), routine automation, Docker / Kubernetes and DB operators, observability and SLO for DBs. Outlook: understanding of different DBMS classes (relational, analytical — ClickHouse, NoSQL) and when to apply which. Communication: work with development (review of schemas and migrations, consulting), explaining risks to management, mentoring. English — for documentation and the international market. Senior DBA is valued primarily for the ability to ensure reliability and performance of data under real load and not lose data in an incident.