Data Architect: 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

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.

Top stack / skills: cloud, aws, devops, finops, agile. 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 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. Reality 2026 (overlap): Data Architect ↔ Data Engineer: 60% (Senior Data Engineers often do architecture work; difference — Architect design-focused, Engineer implementation-focused). Data Architect ↔ Enterprise Architect: 50% (Data Architecture — TOGAF domain; large orgs have a separate Data Architect within EA function). Data Architect ↔ DBA: 30% (DBA — single-database operations, Architect — landscape design). 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.

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".

Yes, 14% of Data Architect jobs are full-remote or hybrid. Data architecture work — modelling + design + documentation + cloud platforms — remote-friendly. Outsourcers — almost always remote on US / EU data platform projects. Russian product companies / banks — hybrid or remote after probation. Russian banks — hybrid (data governance — part of management contour). International tech companies + cloud data vendors (Snowflake / Databricks / Confluent) — full-remote standard. Caveat: Data Architect — cross-functional role (work with data engineers + analysts + business + security), requires communication — hybrid often optimal. Relocant hubs: Poland / Germany (enterprise data) / Canada / Serbia. English for international Data Architect remote — must (cloud data platform docs + community + cross-team communication in English).

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.

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.

7 active open Data Architect positions with explicit data-architect scope — narrow senior niche. The real market is wider — many data-architecture roles classified as Senior Data Engineer / Data Platform Engineer / Lead Data Engineer (titles overlap). Geography: Russia / Poland / remote. The real market is wider thanks to the international remote segment (cloud data vendors + EPAM-style outsourcing data platform projects — full-remote-friendly). Time to close a Senior Data Architect — 8-14 weeks (seniority + data modelling depth assessment + cloud platform expertise verification).

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.