Data Architect: market
Data as of November 19, 2026: 620 open Data Architect jobs, 38% remote among jobs that state a work format; median advertised salary $10,507/mo (from 81 postings that state a salary). Source: Zorky, updated daily.
Data Architect — architect specialisation responsible for designing the data landscape of an organisation: data models, data flows, storage strategy, data governance, integration between systems. Unlike a Data Engineer (builds pipelines hands-on) — Data Architect designs the structure: how data is modelled, where it's stored, how it flows, who owns it, how governance works. Role family: Data Architect (general — owns data architecture of one system / domain), Senior / Principal Data Architect (enterprise-wide data architecture + strategy), Data Warehouse Architect (DWH / analytics-focused), Data Platform Architect (modern data platform / lakehouse design), Data Modeler (focus on data modelling — narrower), Master Data Architect (MDM specialty), Information Architect (overlap — data governance + information management). Stack 2026: Data modelling — core skill: conceptual / logical / physical models, dimensional modelling (Kimball — star / snowflake schemas, facts + dimensions), 3NF / Inmon (normalised enterprise DWH), Data Vault 2.0 (hubs + links + satellites — for agile enterprise DWH — popular 2026), One Big Table (OBT) / wide tables (modern analytics trend). Tools: erwin Data Modeler (enterprise classic), SqlDBM, dbdiagram.io, dbt (semantic models + lineage — became de-facto modelling layer 2026). Storage / platforms: cloud data warehouses, Databricks (Lakehouse — Delta Lake), data lakes (S3 / ADLS / GCS + open table formats — Apache Iceberg / Delta Lake / Apache Hudi), ClickHouse (real-time analytics — popular in Russia — Yandex origin). Russian: Arenadata (Greenplum-based — DWH leader in Russia after the Teradata / Oracle departure), Yandex.Cloud DataLens. Data architecture patterns: data warehouse (structured analytics), data lake (raw + schema-on-read), lakehouse (warehouse + lake convergence — recommended default 2026 — Databricks / Snowflake), data mesh (decentralised — domain-owned data products — Zhamak Dehghani — for large organisations), data fabric (unified metadata-driven access layer). Data integration: ETL vs ELT (ELT dominates 2026), CDC (Change Data Capture — Debezium), data streaming (Kafka — see also data engineer), batch + streaming unification. Orchestration: Airflow / Dagster / Prefect (architecture-level — not hands-on). Data governance: data catalog (Collibra / Alation / Atlan / DataHub open-source / OpenMetadata), data lineage, data quality frameworks (Great Expectations / Soda), master data management (MDM) (Informatica MDM / Reltio), data classification + data privacy (PII handling / GDPR / 152-FZ), data contracts (rising 2024+ — formalise producer-consumer agreements). Semantic layer: dbt Semantic Layer / Cube / metrics layer — single source of truth for metrics. Modelling notation: ER diagrams, ArchiMate (for enterprise context), data flow diagrams. Cross-domain: Data Architect works at the intersection with Data Engineering (implementation), Analytics / BI (consumers), Enterprise Architecture (org-level), Security (data protection). According to Zorky, 620 active openings with explicit data-architect scope (narrow senior niche — real pool is wider due to overlap with Senior Data Engineer / Data Platform Engineer). Top stack: cloud, aws, azure, enterprise architect, sql. Among jobs with a stated work format, 38% are remote.
Data as of:
Key numbers for the Data Architect market: open jobs, median salary, observed talent pool and remote share.
The Data Architect market currently has 620 open roles, 531 of them freshly observed. Median salary $10,507/mo.
Among jobs with a stated work format, 38% are remote. Data architecture work (modelling + design + cloud platforms) — remote-friendly. Outsourcers — almost always remote. Russian banks — hybrid (data governance — management contour). Cross-functional role → hybrid often optimal. International tech companies + cloud data vendors — full-remote standard.
⚠ salary known for 81 of 620 jobs; remote share from 509 with a stated format; 531 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Data Architect postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 21 |
| 2026-06-08 | 26 |
| 2026-06-15 | 32 |
| 2026-06-22 | 70 |
| 2026-06-29 | 43 |
| 2026-07-06 | 65 |
| 2026-07-13 | 66 |
| 2026-07-20 | 63 |
| 2026-07-27 | 31 |
| 2026-08-03 | 45 |
| 2026-08-10 | 33 |
| 2026-08-17 | 47 |
| 2026-08-24 | 50 |
| 2026-08-31 | 36 |
| 2026-09-07 | 43 |
| 2026-09-14 | 64 |
| 2026-09-21 | 105 |
| 2026-09-28 | 102 |
| 2026-10-05 | 112 |
| 2026-10-12 | 288 |
| 2026-10-19 | 116 |
| 2026-10-26 | 151 |
| 2026-11-02 | 134 |
| 2026-11-09 | 120 |
Active sources per week
Sources over the period: 104. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 5 |
| 2026-06-08 | 4 |
| 2026-06-15 | 4 |
| 2026-06-22 | 13 |
| 2026-06-29 | 14 |
| 2026-07-06 | 21 |
| 2026-07-13 | 21 |
| 2026-07-20 | 21 |
| 2026-07-27 | 17 |
| 2026-08-03 | 23 |
| 2026-08-10 | 14 |
| 2026-08-17 | 17 |
| 2026-08-24 | 11 |
| 2026-08-31 | 10 |
| 2026-09-07 | 14 |
| 2026-09-14 | 15 |
| 2026-09-21 | 30 |
| 2026-09-28 | 28 |
| 2026-10-05 | 26 |
| 2026-10-12 | 29 |
| 2026-10-19 | 31 |
| 2026-10-26 | 31 |
| 2026-11-02 | 37 |
| 2026-11-09 | 38 |
New sources connected: Jun 22 +10 · Jul 6 +11 · all weeks (21) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +1 | 26 |
| Jun 15 | +2 | 32 |
| Jun 22 | +10 | 70 |
| Jun 29 | +5 | 43 |
| Jul 6 | +11 | 65 |
| Jul 13 | +6 | 66 |
| Jul 20 | +8 | 63 |
| Jul 27 | +6 | 31 |
| Aug 3 | +3 | 45 |
| Aug 10 | +3 | 33 |
| Aug 17 | +5 | 47 |
| Aug 31 | +2 | 36 |
| Sep 7 | +2 | 43 |
| Sep 21 | +7 | 105 |
| Sep 28 | +2 | 102 |
| Oct 5 | +2 | 112 |
| Oct 12 | +4 | 288 |
| Oct 19 | +5 | 116 |
| Oct 26 | +2 | 151 |
| Nov 2 | +5 | 134 |
| Nov 9 | +8 | 120 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 21 | 5 |
| 2026-06-08 | 26 | 4 |
| 2026-06-15 | 32 | 4 |
| 2026-06-22 | 70 | 13 |
| 2026-06-29 | 43 | 14 |
| 2026-07-06 | 65 | 21 |
| 2026-07-13 | 66 | 21 |
| 2026-07-20 | 63 | 21 |
| 2026-07-27 | 31 | 17 |
| 2026-08-03 | 45 | 23 |
| 2026-08-10 | 33 | 14 |
| 2026-08-17 | 47 | 17 |
| 2026-08-24 | 50 | 11 |
| 2026-08-31 | 36 | 10 |
| 2026-09-07 | 43 | 14 |
| 2026-09-14 | 64 | 15 |
| 2026-09-21 | 105 | 30 |
| 2026-09-28 | 102 | 28 |
| 2026-10-05 | 112 | 26 |
| 2026-10-12 | 288 | 29 |
| 2026-10-19 | 116 | 31 |
| 2026-10-26 | 151 | 31 |
| 2026-11-02 | 134 | 37 |
| 2026-11-09 | 120 | 38 |
Salaries over time
Median Data Architect salary per week, USD per month.
Median salary, USD per month
Chart data
| Period | Median | Postings with a salary per week (n) |
|---|---|---|
| 2026-09-28 | 9,982 | 14 |
| 2026-10-05 | 10,507 | 15 |
| 2026-10-12 | 10,416 | 21 |
| 2026-10-19 | 11,077 | 16 |
| 2026-10-26 | 11,584 | 32 |
| 2026-11-02 | 9,837 | 24 |
| 2026-11-09 | 8,274 | 20 |
The series starts on Sep 28: there is no data before that.
Only postings with a USD salary and a known period (month or year), $500–$50,000 per month. Weeks with fewer than 10 such postings are left blank — that means no data, not zero.
Chart data
| Week | Median |
|---|---|
| 2026-06-01 | — |
| 2026-06-08 | — |
| 2026-06-15 | — |
| 2026-06-22 | — |
| 2026-06-29 | — |
| 2026-07-06 | — |
| 2026-07-13 | — |
| 2026-07-20 | — |
| 2026-07-27 | — |
| 2026-08-03 | — |
| 2026-08-10 | — |
| 2026-08-17 | — |
| 2026-08-24 | — |
| 2026-08-31 | — |
| 2026-09-07 | — |
| 2026-09-14 | — |
| 2026-09-21 | — |
| 2026-09-28 | 9,982 |
| 2026-10-05 | 10,507 |
| 2026-10-12 | 10,416 |
| 2026-10-19 | 11,077 |
| 2026-10-26 | 11,584 |
| 2026-11-02 | 9,837 |
| 2026-11-09 | 8,274 |
Remote work over time
Share of Data Architect postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 83.3 |
| 2026-06-08 | 80 |
| 2026-06-15 | 75 |
| 2026-06-22 | 62.1 |
| 2026-06-29 | 64.7 |
| 2026-07-06 | 48.9 |
| 2026-07-13 | 35.5 |
| 2026-07-20 | 36.6 |
| 2026-07-27 | 47.8 |
| 2026-08-03 | 22.2 |
| 2026-08-10 | 34.4 |
| 2026-08-17 | 28.9 |
| 2026-08-24 | 25.5 |
| 2026-08-31 | 15.6 |
| 2026-09-07 | 10.3 |
| 2026-09-14 | 11.1 |
| 2026-09-21 | 32.6 |
| 2026-09-28 | 51.1 |
| 2026-10-05 | 38.6 |
| 2026-10-12 | 33.8 |
| 2026-10-19 | 34.3 |
| 2026-10-26 | 43.3 |
| 2026-11-02 | 26.8 |
| 2026-11-09 | 38.7 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 83.3 |
| 2026-06-08 | 80 |
| 2026-06-15 | 75 |
| 2026-06-22 | 62.1 |
| 2026-06-29 | 64.7 |
| 2026-07-06 | 48.9 |
| 2026-07-13 | 35.5 |
| 2026-07-20 | 36.6 |
| 2026-07-27 | 47.8 |
| 2026-08-03 | 22.2 |
| 2026-08-10 | 34.4 |
| 2026-08-17 | 28.9 |
| 2026-08-24 | 25.5 |
| 2026-08-31 | 15.6 |
| 2026-09-07 | 10.3 |
| 2026-09-14 | 11.1 |
| 2026-09-21 | 32.6 |
| 2026-09-28 | 51.1 |
| 2026-10-05 | 38.6 |
| 2026-10-12 | 33.8 |
| 2026-10-19 | 34.3 |
| 2026-10-26 | 43.3 |
| 2026-11-02 | 26.8 |
| 2026-11-09 | 38.7 |
Technologies over time
How the share of Data Architect postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | cloud | Azure | AWS |
|---|---|---|---|
| 2026-08-17 | 34.6 | 42.3 | 15.4 |
| 2026-08-24 | 26.1 | 26.1 | 13 |
| 2026-08-31 | — | — | — |
| 2026-09-07 | 28.6 | 19 | 14.3 |
| 2026-09-14 | 14.7 | 61.8 | 52.9 |
| 2026-09-21 | 47.5 | 33.9 | 22 |
| 2026-09-28 | 69.4 | 52.8 | 31.9 |
| 2026-10-05 | 59 | 32.5 | 47 |
| 2026-10-12 | 50.8 | 30.7 | 30.2 |
| 2026-10-19 | 60.5 | 48.8 | 26.7 |
| 2026-10-26 | 60.5 | 36.3 | 37.9 |
| 2026-11-02 | 66.7 | 35.3 | 32.4 |
| 2026-11-09 | 48.2 | 34.1 | 36.5 |
The series starts on Aug 17: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | cloud | Azure | Databricks | AWS | SQL |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | 34.6 | 42.3 | 23.1 | 15.4 | 19.2 |
| 2026-08-24 | 26.1 | 26.1 | 26.1 | 13 | 13 |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | 28.6 | 19 | 19 | 14.3 | 14.3 |
| 2026-09-14 | 14.7 | 61.8 | 14.7 | 52.9 | 2.9 |
| 2026-09-21 | 47.5 | 33.9 | 23.7 | 22 | 16.9 |
| 2026-09-28 | 69.4 | 52.8 | 34.7 | 31.9 | 37.5 |
| 2026-10-05 | 59 | 32.5 | 31.3 | 47 | 33.7 |
| 2026-10-12 | 50.8 | 30.7 | 27.5 | 30.2 | 29.1 |
| 2026-10-19 | 60.5 | 48.8 | 39.5 | 26.7 | 50 |
| 2026-10-26 | 60.5 | 36.3 | 35.5 | 37.9 | 37.1 |
| 2026-11-02 | 66.7 | 35.3 | 35.3 | 32.4 | 36.3 |
| 2026-11-09 | 48.2 | 34.1 | 41.2 | 36.5 | 42.4 |
Countries over time
How the share of Data Architect postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | UK | Poland | USA |
|---|---|---|---|
| 2026-06-01 | 9.5 | 71.4 | 19 |
| 2026-06-08 | 3.8 | 65.4 | 19.2 |
| 2026-06-15 | 3.2 | 71 | 3.2 |
| 2026-06-22 | 0 | 66.7 | 7.2 |
| 2026-06-29 | 2.5 | 50 | 15 |
| 2026-07-06 | 7.3 | 21.8 | 20 |
| 2026-07-13 | 2.2 | 17.8 | 22.2 |
| 2026-07-20 | 44.4 | 20.4 | 13 |
| 2026-07-27 | 30.8 | 26.9 | 3.8 |
| 2026-08-03 | 36.8 | 7.9 | 18.4 |
| 2026-08-10 | 51.7 | 6.9 | 3.4 |
| 2026-08-17 | 52.6 | 0 | 10.5 |
| 2026-08-24 | 71.1 | 2.2 | 4.4 |
| 2026-08-31 | 72.7 | 0 | 6.1 |
| 2026-09-07 | 68.4 | 0 | 2.6 |
| 2026-09-14 | 50 | 2 | 18 |
| 2026-09-21 | 20 | 10 | 21.1 |
| 2026-09-28 | 31.9 | 16.5 | 16.5 |
| 2026-10-05 | 29.6 | 19.4 | 13.3 |
| 2026-10-12 | 19.7 | 15.8 | 22.2 |
| 2026-10-19 | 23 | 14 | 20 |
| 2026-10-26 | 21 | 15.9 | 21.7 |
| 2026-11-02 | 24.3 | 11.3 | 24.3 |
| 2026-11-09 | 32.6 | 5.3 | 28.4 |
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | UK | Poland | USA | India | Germany |
|---|---|---|---|---|---|
| 2026-06-01 | 9.5 | 71.4 | 19 | 0 | 0 |
| 2026-06-08 | 3.8 | 65.4 | 19.2 | 3.8 | 0 |
| 2026-06-15 | 3.2 | 71 | 3.2 | 6.5 | 0 |
| 2026-06-22 | 0 | 66.7 | 7.2 | 7.2 | 0 |
| 2026-06-29 | 2.5 | 50 | 15 | 7.5 | 2.5 |
| 2026-07-06 | 7.3 | 21.8 | 20 | 14.5 | 1.8 |
| 2026-07-13 | 2.2 | 17.8 | 22.2 | 26.7 | 6.7 |
| 2026-07-20 | 44.4 | 20.4 | 13 | 5.6 | 1.9 |
| 2026-07-27 | 30.8 | 26.9 | 3.8 | 15.4 | 0 |
| 2026-08-03 | 36.8 | 7.9 | 18.4 | 10.5 | 5.3 |
| 2026-08-10 | 51.7 | 6.9 | 3.4 | 6.9 | 3.4 |
| 2026-08-17 | 52.6 | 0 | 10.5 | 5.3 | 0 |
| 2026-08-24 | 71.1 | 2.2 | 4.4 | 8.9 | 2.2 |
| 2026-08-31 | 72.7 | 0 | 6.1 | 12.1 | 0 |
| 2026-09-07 | 68.4 | 0 | 2.6 | 13.2 | 0 |
| 2026-09-14 | 50 | 2 | 18 | 6 | 4 |
| 2026-09-21 | 20 | 10 | 21.1 | 7.8 | 3.3 |
| 2026-09-28 | 31.9 | 16.5 | 16.5 | 4.4 | 2.2 |
| 2026-10-05 | 29.6 | 19.4 | 13.3 | 7.1 | 9.2 |
| 2026-10-12 | 19.7 | 15.8 | 22.2 | 6.4 | 3 |
| 2026-10-19 | 23 | 14 | 20 | 11 | 5 |
| 2026-10-26 | 21 | 15.9 | 21.7 | 6.5 | 5.1 |
| 2026-11-02 | 24.3 | 11.3 | 24.3 | 1.7 | 10.4 |
| 2026-11-09 | 32.6 | 5.3 | 28.4 | 7.4 | 1.1 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Data Architect.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Data Architect jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 620 |
| Open demand | 620 |
| Observed supply | — not published |
Data Architect — narrow senior niche with growing demand. Drivers 2026: cloud data platform migration (legacy DWH → Snowflake / Databricks), lakehouse adoption (warehouse + lake convergence), data mesh for large organisations, data governance pressure (GDPR / 152-FZ / data contracts), AI/ML drives data quality demand (good models need good data). Russian banks + large product companies + retail + telecom dominate. Russian data vendors (Arenadata) growing on import substitution. Cloud data vendors (Snowflake / Databricks) — premium channel.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Data Architect jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 0 |
| $1–2k | 2 |
| $2–3k | 0 |
| $3–4k | 1 |
| $4–5k | 3 |
| $5–6k | 4 |
| $6–7k | 6 |
| $7–8k | 8 |
| $8–9k | 9 |
| $9–10k | 5 |
| $10–12k | 15 |
| $12–15k | 10 |
| $15–20k | 13 |
| $20k+ | 5 |
- usable for the calculation: 81 (13.1%)
- stated but not converted to USD/month: 91 (14.7%)
- not stated: 448 (72.3%)
One in ten postings offers under $5,692, one in ten over $18,440. Half of the postings offer between $7,333 and $14,200. Sample: 81.
Senior-tier role. Lower grades in histogram — mis-titled positions, not representative.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 0 |
| $1–2k | 1,000 | 2,000 | 2 |
| $2–3k | 2,000 | 3,000 | 0 |
| $3–4k | 3,000 | 4,000 | 1 |
| $4–5k | 4,000 | 5,000 | 3 |
| $5–6k | 5,000 | 6,000 | 4 |
| $6–7k | 6,000 | 7,000 | 6 |
| $7–8k | 7,000 | 8,000 | 8 |
| $8–9k | 8,000 | 9,000 | 9 |
| $9–10k | 9,000 | 10,000 | 5 |
| $10–12k | 10,000 | 12,000 | 15 |
| $12–15k | 12,000 | 15,000 | 10 |
| $15–20k | 15,000 | 20,000 | 13 |
| $20k+ | 20,000 | — | 5 |
Which countries have the most open Data Architect jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| United States | 129 | 25.1% |
| United Kingdom | 94 | 18.3% |
| Poland | 77 | 15% |
| India | 41 | 8% |
| Germany | 26 | 5.1% |
| Canada | 14 | 2.7% |
| France | 12 | 2.3% |
| Brazil | 11 | 2.1% |
| Philippines | 7 | 1.4% |
| Colombia | 7 | 1.4% |
| Other countries | 96 | 18.7% |
The leader by Data Architect job count is the US (129 positions). Russia — banks + large product companies + retail + telecom + outsourcers dominate. Poland — Data Architect-friendly EU hub. Germany — enterprise data. International remote via cloud data vendors (Snowflake / Databricks / Confluent) + EPAM-style outsourcing.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| US | 129 |
| GB | 94 |
| PL | 77 |
| IN | 41 |
| DE | 26 |
| CA | 14 |
| FR | 12 |
| BR | 11 |
| PH | 7 |
| CO | 7 |
Which technologies are most often required in the same job as Data Architect.
Used together with
Share — how many of the 620 jobs in the Data Architect market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Data Architect stack 2026: data modelling (dimensional modelling Kimball + 3NF/Inmon + Data Vault 2.0 + One Big Table; tools erwin / SqlDBM / dbdiagram / dbt), cloud data warehouses (Snowflake leader + BigQuery + Redshift + Azure Synapse + Databricks Lakehouse + ClickHouse Russia-popular + Russian Arenadata), data lakes (S3/ADLS/GCS + open table formats Iceberg/Delta Lake/Hudi), data architecture patterns (warehouse / lake / lakehouse default 2026 / data mesh / data fabric), data integration (ETL vs ELT-dominates + CDC Debezium + Kafka streaming), orchestration (Airflow / Dagster / Prefect), data governance (data catalogs Collibra/Alation/Atlan/DataHub/OpenMetadata + data lineage + data quality Great Expectations/Soda + MDM Informatica/Reltio + data contracts), semantic layer (dbt Semantic Layer / Cube), SQL mastery, modelling notation (ER diagrams + ArchiMate + data flow diagrams).
Common pairs: Snowflake + dbt + Airflow (modern data stack classic), Databricks + Delta Lake + Spark (lakehouse stack), Data Vault 2.0 + Snowflake + dbt (agile enterprise DWH), Kimball dimensional modelling + cloud DWH + BI (analytics-focused), ClickHouse + Kafka (real-time analytics — Russia-popular), Arenadata Greenplum + dbt (Russian import substitution data stack), Iceberg + S3 + Trino (open lakehouse). Learning roadmap: become Senior Data Engineer (5+ years — prerequisite) → data modelling mastery (Kimball + Data Vault) → SQL deep → cloud data platform (Snowflake / Databricks) → modern data stack (dbt + orchestration) → data architecture patterns → data mesh (Dehghani book) → data governance → open table formats → semantic layer → soft skills.
Chart data
| Name | Count |
|---|---|
| cloud | 282 |
| azure | 192 |
| databricks | 180 |
| aws | 170 |
| sql | 155 |
| python | 104 |
| snowflake | 100 |
| gcp | 75 |
| spark | 61 |
| dbt | 55 |
| bigquery | 53 |
| kafka | 52 |
How many Data Architect jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| principal | 212 |
| senior | 185 |
| lead | 45 |
| middle | 14 |
| junior | 4 |
Senior-tier role (lower grades = mis-titled; realistic — Senior / Lead). Path: Senior Data Engineer (5+ years hands-on) → Data Architect (via data modelling + platform design + governance) → Senior / Principal Data Architect → either Chief Data Architect / Head of Data Architecture, Data Platform lead, Enterprise Architect (Data domain), or Chief Data Officer (CDO) track.
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| principal | 212 |
| senior | 185 |
| lead | 45 |
| middle | 14 |
| junior | 4 |
Who hires the most for Data Architect and how concentrated demand is among the largest companies.
Employers
Demand is spread across 468 employers. The largest accounts for 1.7%, the top ten for 10.0%; the remaining 90.0% is long tail.
| share | value |
|---|---|
| top-1 | 1.7% |
| top-3 | 4.5% |
| top-10 | 10.0% |
| long tail | 90.0% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Data Architect jobs from.
Where Zorky sees this market
Observed across 59 sources; the largest accounts for 9.5% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 374 | 0.6032 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 227 | 0.3661 |
| telegram | Telegram | Telegram | 19 | 0.0306 |
The newest Data Architect jobs from company career sites.
Recent openings
- Data Architect · AZ
- Ness Technologies - Data Architect - Azure/Databricks · IN
- Data Architect
- Data Architect · GB
- Data Architect - Snowflake
- Senior Data architect (SC Cleared)
- Senior Data Architect · GB
- Senior Data Architect - Defence Digital Systems & Data Governance · GB
Latest open Data Architect jobs — most recent positions in the sample (narrow senior niche — real market is wider due to overlap with Senior Data Engineer). The full list is in our CRM or via the "see all" link below. For broader view check data-engineer + solutions architect pages.
Adjacent markets
Data Architect overlaps with Data Engineer (~60% — Architect design-focused, Engineer implementation), Enterprise Architect (~50% — Data Architecture one of 4 TOGAF domains), Database Administrator (~30% — DBA single-database ops), Analytics / BI (data consumers), Security (data protection / privacy). Comparison with solutions/software/enterprise/security/integration — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- 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
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Architecture
Related specializations
Inside Data Architect: Data Architect (general — owns data architecture of one system / domain), Senior / Principal Data Architect (enterprise-wide + strategy), Data Warehouse Architect (DWH / analytics-focused), Data Platform Architect (modern data platform / lakehouse design), Data Modeler (focus on data modelling — narrower), Master Data Architect (MDM specialty), Information Architect (data governance + information management). Comparison with solutions/software/enterprise/security/integration architect — in the bar below.
Frequently asked questions
Answers recompute automatically.
What does a Data Architect Junior, Middle, Senior, or Lead earn?
Data Architect — senior-tier role ("Junior Data Architect" rarely exists; lower grades = mis-titled — realistic benchmarks see Senior / Lead). Career flow: Senior Data Engineer (5+ years hands-on data pipelines + warehouse work) → Data Architect (via demonstrated data modelling + platform design + governance experience) → Senior / Principal Data Architect → either Chief Data Architect / Head of Data Architecture, Data Platform lead, Enterprise Architect (Data domain → broader EA), or Chief Data Officer (CDO) track. Alternative entry: Database Administrator Senior + data modelling depth → Data Architect.
What stack / skills are most often required of a Data Architect?
Top stack / skills: cloud, aws, azure, enterprise architect, sql. Data modelling — core: conceptual / logical / physical models, dimensional modelling (Kimball — star / snowflake schemas + facts/dimensions), 3NF / Inmon (normalised enterprise DWH), Data Vault 2.0 (hubs + links + satellites — agile enterprise DWH, popular 2026), One Big Table / wide tables (modern analytics). Tools: erwin Data Modeler (enterprise classic), SqlDBM, dbdiagram.io, dbt (semantic models + lineage — de-facto modelling layer 2026). ClickHouse (real-time analytics — popular in Russia, Yandex origin). Russian: Arenadata (Greenplum-based — DWH leader in Russia after Teradata / Oracle departure). Data lakes: S3 / ADLS / GCS + open table formats (Apache Iceberg — rising 2026 / Delta Lake / Apache Hudi). Data architecture patterns: data warehouse / data lake / lakehouse (recommended default 2026) / data mesh (decentralised domain-owned — Zhamak Dehghani) / data fabric (metadata-driven unified access). Data integration: ETL vs ELT (ELT dominates 2026), CDC (Change Data Capture — Debezium), data streaming (Kafka), batch + streaming unification. Orchestration: Airflow / Dagster / Prefect (architecture-level decisions). Data governance: data catalog (Collibra / Alation / Atlan / DataHub open-source / OpenMetadata), data lineage, data quality (Great Expectations / Soda), master data management MDM (Informatica MDM / Reltio), data classification + privacy (PII / GDPR / 152-FZ), data contracts (rising 2024+). Semantic layer: dbt Semantic Layer / Cube — single source of truth for metrics. SQL mastery — mandatory (Data Architect must understand query patterns + performance). Soft skills: stakeholder management (data — cross-functional), data strategy communication, governance facilitation.
Data Architect vs Data Engineer vs Enterprise Architect vs DBA — what's the difference?
Data Engineer — hands-on builds data pipelines (ingestion + transformation + orchestration), implements what Data Architect designed. See Data Engineer (general). Data Architect (this page) — designs data landscape: data models + storage strategy + data flows + governance. Design-level, not hands-on pipeline coding. Database Administrator (DBA) — operates specific databases (performance tuning + backups + replication + security). Operational. See Database Administrator (DBA) (when the page ships). Enterprise Architect — org-wide technology landscape (Data Architecture — one of 4 TOGAF domains; Data Architect often = Domain Architect within EA). See Enterprise Architect. Career flow: Data Engineer Senior → Data Architect — natural path. Data Architect → Enterprise Architect (Data domain) or Chief Data Officer. Career choice: Data Engineer if you like hands-on pipeline building; Data Architect if you like design + modelling + governance + strategy; DBA if you like database operations deep; Enterprise Architect if you want org-level breadth beyond data.
Data architecture patterns 2026 — data warehouse vs data lake vs lakehouse vs data mesh vs data fabric?
Decision tree for data architecture pattern 2026: 1) Data Warehouse — structured, schema-on-write, optimised for analytics / BI. Cloud DWH: Snowflake / BigQuery / Redshift / Synapse. Pros: fast SQL analytics, mature tooling, data quality enforced. Cons: structured data only, ETL upfront, more expensive for raw / unstructured. Use case: BI / reporting / structured analytics — still core 2026. 2) Data Lake — raw storage, schema-on-read, any formats (structured + unstructured). S3 / ADLS / GCS. Pros: cheap storage, flexible, stores everything. Cons: "data swamp" risk (without governance — chaos), no SQL performance, no ACID. Use case: raw data landing zone, ML training data, archival. Standalone rare 2026. 3) Lakehouse — recommended default 2026. Warehouse + lake convergence: data lake storage (S3 + open table format — Delta Lake / Iceberg / Hudi) + warehouse-like features (ACID transactions + SQL performance + schema enforcement + time travel). Databricks (Delta Lake) / Snowflake (Iceberg support). Pros: one storage layer for BI + ML + streaming, cheaper than pure DWH, no data duplication. Cons: younger ecosystem, need the right table format strategy. Use case: new data platforms 2026 — default choice (avoids warehouse + lake duplication). 4) Data Mesh — organisational / socio-technical pattern, not technology. Zhamak Dehghani concept. 4 principles: domain-oriented ownership (data owned by domain teams, not central data team), data as a product (each dataset — product with SLA / docs / quality), self-serve data platform, federated computational governance. Pros: scales organisationally (central data team — bottleneck in large orgs), domain expertise in data ownership. Cons: requires organisational maturity, expensive to implement, overkill for small organisations. Use case: large organisations (many domains, central data team can't keep up) — NOT for small / medium (organisational overhead will kill it). Often over-applied. 5) Data Fabric — metadata-driven unified data access layer over heterogeneous sources (vs data mesh — org pattern, data fabric — technology / integration approach). Active metadata + knowledge graph + automated data integration. Gartner-pushed concept. Use case: organisations with many legacy data silos, need unified access without migrating everything. Default 2026 recommendations: New data platform → Lakehouse (Databricks or Snowflake + Iceberg). BI / structured analytics → Cloud DWH (if lakehouse is overkill). Raw / ML data → data lake as part of lakehouse (not standalone). Large organisation, central data team is the bottleneck → Data Mesh (organisational shift, not tech). Many legacy silos → Data Fabric (unified access layer). Main principle: pattern follows organisational reality + scale — not cargo-cult "data mesh because it's trendy".
What share of jobs are remote?
Among jobs with a stated work format, 38% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Data Platform Architect different from Data Architect?
Data Architect (general) — focus on data models + data flows + governance + storage strategy (logical / conceptual level — "how data is structured and flows"). Data Platform Architect — focus on the technical platform that hosts data (infrastructure / tooling level — "on what data lives"): cloud data platform design (Databricks / Snowflake setup), compute / storage architecture, data platform tooling (ingestion + orchestration + transformation + catalog stack), platform scalability + cost optimisation, self-serve data platform (for data mesh). More overlap with DevOps / Platform Engineering. Data Warehouse Architect — narrower specialty: focus on DWH design specifically (dimensional modelling deep, ETL/ELT for warehouse, BI enablement). Data Modeler — narrowest role: focus only on data modelling (conceptual / logical / physical models, ER diagrams) — often mid-level, not full architect. Master Data Architect — MDM specialty (master data management — single source of truth for core entities — customer / product / etc.). Information Architect — overlap — data governance + information lifecycle + taxonomy + metadata. Reality 2026: in small / medium organisations one Data Architect does everything. In large ones — specialisation (Data Platform Architect + Data Warehouse Architect + Data Modeler + Master Data Architect — separate roles). Career choice: general Data Architect for breadth; Data Platform Architect if you like infrastructure / tooling deep; Data Warehouse Architect if you like dimensional modelling + analytics; Master Data Architect if you like governance / MDM.
Where to start the path to Data Architect in 2026?
Roadmap (Data Architect — senior-tier, the path goes via Senior Data Engineer): 1) Become a strong Senior Data Engineer — prerequisite. 5+ years hands-on: data pipelines, warehouse work, SQL mastery, understanding of data tooling in practice. 2) Data modelling mastery — this is the core Data Architect skill. Dimensional modelling (Kimball — "The Data Warehouse Toolkit" Ralph Kimball — canonical), Inmon 3NF approach, Data Vault 2.0 ("Building a Scalable Data Warehouse with Data Vault 2.0" Dan Linstedt). Conceptual / logical / physical modelling. 3) SQL deep — Data Architect must deeply understand query patterns + performance + optimisation. 4) Cloud data platforms — choose one deeply: Snowflake (leader — Snowflake certifications) or Databricks (Lakehouse — Databricks certifications) or BigQuery. Hands-on design + build experience. 5) Modern data stack — dbt (de-facto transformation + modelling layer 2026 — dbt certification), data orchestration (Airflow / Dagster), ELT patterns, CDC (Debezium). 6) Data architecture patterns — deeply understand warehouse vs lake vs lakehouse vs data mesh vs data fabric (when which). "Fundamentals of Data Engineering" Joe Reis / Matt Housley (canonical 2026 — must-read, covers architecture). 7) Data mesh — "Data Mesh" Zhamak Dehghani (if you work / will work in a large organisation). 8) Data governance — data catalogs (Collibra / Alation / DataHub / OpenMetadata), data lineage, data quality (Great Expectations / Soda), MDM concepts, data contracts (rising 2024+), data privacy (GDPR / 152-FZ). 9) Open table formats — Apache Iceberg (rising 2026) / Delta Lake / Apache Hudi — critical for lakehouse. 10) Semantic layer — dbt Semantic Layer / Cube — metrics consistency. 11) Soft skills — data — cross-functional (engineers + analysts + business + security), need stakeholder management + data strategy communication + governance facilitation. 12) Practice in current role — as Senior Data Engineer take architecture-level tasks: data model design, platform selection, governance setup. Russian courses: Otus "Data Architect" / "DWH Analyst", Karpov.Courses (Data Engineering — overlap), corporate data schools, Arenadata training. International (EN): "The Data Warehouse Toolkit" Kimball (canonical dimensional modelling), "Fundamentals of Data Engineering" Reis / Housley (must-read 2026), "Data Mesh" Dehghani, Snowflake / Databricks official certifications + training, dbt Learn (free), DataCamp / Coursera data engineering tracks. Senior Data Engineer (5+ years) + data modelling mastery + cloud data platform expertise → Data Architect.
How many open jobs are in this sample?
The published sample contains 620 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Data Architect need?
A Senior Data Architect owns the full data architecture + technical leadership cycle. Data modelling mastery: dimensional modelling (Kimball — star / snowflake schemas + facts/dimensions deep), 3NF / Inmon enterprise DWH, Data Vault 2.0 (hubs / links / satellites — agile DWH), conceptual / logical / physical modelling, ER modelling. SQL deep mastery: complex queries, query optimisation, understanding execution plans — Data Architect must deeply understand how data is queried. Cloud data platform mastery: one of Snowflake / Databricks / BigQuery deeply — architecture design, performance optimisation, cost optimisation (data platforms — expensive, cost-architecture critical). Data architecture patterns: warehouse / lake / lakehouse / data mesh / data fabric — know trade-offs + when to apply (not cargo-cult). Lakehouse design (open table formats — Iceberg / Delta Lake / Hudi). Modern data stack: dbt (transformation + modelling + semantic layer), orchestration (Airflow / Dagster), ELT patterns, CDC (Debezium), streaming (Kafka) architecture-level. Data integration architecture: batch + streaming unification, data ingestion strategy, source-to-target mapping. Data governance mastery: data catalog strategy (Collibra / Alation / DataHub / OpenMetadata), data lineage, data quality frameworks (Great Expectations / Soda), master data management (MDM), data classification + privacy (PII / GDPR / 152-FZ compliance in data architecture), data contracts (formalise producer-consumer agreements — rising 2024+). Semantic layer: metrics consistency (dbt Semantic Layer / Cube — single source of truth). Data strategy: data platform roadmapping, build-vs-buy for data tooling, data team operating model (centralised vs data mesh decentralised). System design for data: design data platform on whiteboard for scale (PB-scale data, 1000s of tables, real-time + batch), capacity planning, performance + cost trade-offs. Cross-domain knowledge: understanding of Data Engineering (implementation reality), Analytics / BI (consumer needs), Security (data protection), Enterprise Architecture (org-level context). Soft skills: stakeholder management (data — cross-functional: engineers + analysts + business + security + compliance), data strategy communication to leadership, data governance facilitation, mentoring Data Engineers. English for Senior+ MUST — cloud data platform docs + data community + international team communication are English-language. Optional bonus: cloud data platform certifications (Snowflake / Databricks), dbt certification, conference speaking (data conferences), data mesh implementation experience — sharply increase market value for Principal / Chief Data Architect roles.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.