Data Architect: рынок

Вакансия

открытая вакансия, прошедшая гейт качества и содержащая не менее двух технологий

Наблюдаемый кандидат

кандидат, чей стек содержит эту технологию; агрегат, без единой записи наружу

Подходящий кандидат

пока не считается

Окно

открытые вакансии на момент сборки снимка

Топ-стек / навыки: cloud, aws, devops, finops, agile. Data modeling — core: conceptual / logical / physical models, dimensional modeling (Kimball — star / snowflake schemas + facts/dimensions), 3NF / Inmon (нормализованный enterprise DWH), Data Vault 2.0 (hubs + links + satellites — agile enterprise DWH, популярен 2026), One Big Table / wide tables (modern analytics). Tools: erwin Data Modeler (enterprise classic), SqlDBM, dbdiagram.io, dbt (semantic models + lineage — de-facto modeling layer 2026). ClickHouse (real-time analytics — РФ-популярен, Яндекс origin). Russian: Arenadata (Greenplum-based — DWH leader РФ после ухода Teradata / Oracle). Data lakes: S3 / ADLS / GCS + open table formats (Apache Iceberg — rising 2026 / Delta Lake / Apache Hudi). Data architecture patterns: data warehouse / data lake / lakehouse (рекомендуемый default 2026) / data mesh (decentralized domain-owned — Zhamak Dehghani) / data fabric (metadata-driven unified access). Data integration: ETL vs ELT (ELT доминирует 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-ФЗ), data contracts (rising 2024+). Semantic layer: dbt Semantic Layer / Cube — single source of truth для метрик. SQL mastery — обязательно (Data Architect должен понимать query patterns + performance). Soft skills: stakeholder management (data — cross-functional), data strategy communication, governance facilitation.

Data Engineer — hands-on строит data pipelines (ingestion + transformation + orchestration), implements то, что Data Architect спроектировал. См. Data Engineer (general). Data Architect (эта страница) — проектирует data landscape: data models + storage strategy + data flows + governance. Design-level, не hands-on pipeline coding. Database Administrator (DBA) — operates конкретные databases (performance tuning + backups + replication + security). Operational. См. Database Administrator (DBA) (когда страница ship'нется). Enterprise Architect — org-wide technology landscape (Data Architecture — один из 4 TOGAF доменов; Data Architect часто = Domain Architect внутри EA). См. Enterprise Architect. Reality 2026 (overlap): Data Architect ↔ Data Engineer: 60% (Senior Data Engineers часто делают architecture work; разница — Architect design-focused, Engineer implementation-focused). Data Architect ↔ Enterprise Architect: 50% (Data Architecture — TOGAF domain; large orgs имеют отдельного Data Architect внутри EA function). Data Architect ↔ DBA: 30% (DBA — single-database operations, Architect — landscape design). Career-flow: Data Engineer Senior → Data Architect — естественный путь. Data Architect → Enterprise Architect (Data domain) или Chief Data Officer. Career-выбор: Data Engineer if нравится hands-on pipeline building; Data Architect if нравится design + modeling + governance + strategy; DBA if нравится database operations deep; Enterprise Architect if хочешь org-level breadth beyond data.

Decision tree для data architecture pattern 2026: 1) Data Warehouse — structured, schema-on-write, optimized для analytics / BI. Cloud DWH: Snowflake / BigQuery / Redshift / Synapse. Pros: fast SQL analytics, mature tooling, data quality enforced. Cons: structured data only, ETL upfront, дороже для raw / unstructured. Use case: BI / reporting / structured analytics — всё ещё core 2026. 2) Data Lake — raw storage, schema-on-read, любые форматы (structured + unstructured). S3 / ADLS / GCS. Pros: cheap storage, flexible, хранит всё. Cons: «data swamp» risk (без governance — хаос), нет SQL performance, нет ACID. Use case: raw data landing zone, ML training data, archival. Standalone редко 2026. 3) Lakehouse — рекомендуемый default 2026. Convergence warehouse + lake: 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). Pros: один storage layer для BI + ML + streaming, cheaper чем pure DWH, no data duplication. Cons: younger ecosystem, нужна правильная table format strategy. Use case: новые data platforms 2026 — default choice (избегает warehouse + lake duplication). 4) Data Mesh — organizational / socio-technical pattern, не technology. Zhamak Dehghani concept. 4 принципа: domain-oriented ownership (data owned by domain teams, не central data team), data as a product (каждый dataset — product с SLA / docs / quality), self-serve data platform, federated computational governance. Pros: scales organizationally (central data team — bottleneck в больших orgs), domain expertise в data ownership. Cons: требует organizational maturity, дорого внедрять, overkill для малых организаций. Use case: large organizations (множество domains, central data team не справляется) — НЕ для малых / средних (организационный overhead убьёт). Часто over-applied. 5) Data Fabric — metadata-driven unified data access layer поверх heterogeneous sources (vs data mesh — org pattern, data fabric — technology / integration approach). Active metadata + knowledge graph + automated data integration. Gartner-pushed concept. Use case: организации с множеством legacy data silos, нужен unified access без миграции всего. Default 2026 рекомендации: Новая data platform → Lakehouse (Databricks или Snowflake + Iceberg). BI / structured analytics → Cloud DWH (если lakehouse overkill). Raw / ML data → data lake как часть lakehouse (не standalone). Большая организация, central data team — bottleneck → Data Mesh (organizational shift, не tech). Множество legacy silos → Data Fabric (unified access layer). Главный принцип: pattern follows organizational reality + scale — не cargo-cult «data mesh потому что модно».

Да, 14% Data Architect-вакансий — full-remote или гибрид. Data architecture work — modeling + design + documentation + cloud platforms — remote-friendly. Аутсорсеры — почти всегда remote на US / EU data-platform projects. Российские продуктовые / банки — гибрид или remote после probation. Российские банки — гибрид (data governance — часть управленческого контура). Международные tech-companies + cloud data vendors (Snowflake / Databricks / Confluent) — full-remote standard. Caveat: Data Architect — cross-functional роль (работа с data engineers + analysts + business + security), требует communication — гибрид часто optimal. Релокант-хабы: Польша / Германия (enterprise data) / Канада / Сербия. Английский для international Data Architect-remote — must (cloud data platform docs + community + cross-team communication на английском).

Data Architect (general) — focus на data models + data flows + governance + storage strategy (логический / концептуальный уровень — «как данные структурированы и текут»). Data Platform Architect — focus на technical platform который hosts data (infrastructure / tooling уровень — «на чём данные живут»): cloud data platform design (Databricks / Snowflake setup), compute / storage architecture, data platform tooling (ingestion + orchestration + transformation + catalog stack), platform scalability + cost optimization, self-serve data platform (для data mesh). Больше overlap с DevOps / Platform Engineering. Data Warehouse Architect — narrower specialty: focus на DWH design specifically (dimensional modeling deep, ETL/ELT для warehouse, BI enablement). Data Modeler — самая narrow роль: focus только на data modeling (conceptual / logical / physical models, ER diagrams) — часто mid-level, не full architect. Master Data Architect — MDM specialty (master data management — single source of truth для core entities — customer / product / etc). Information Architect — overlap — data governance + information lifecycle + taxonomy + metadata. Reality 2026: в малых / средних организациях один Data Architect делает всё. В крупных — specialization (Data Platform Architect + Data Warehouse Architect + Data Modeler + Master Data Architect — отдельные роли). Career-выбор: general Data Architect для breadth; Data Platform Architect if нравится infrastructure / tooling deep; Data Warehouse Architect if нравится dimensional modeling + analytics; Master Data Architect if нравится governance / MDM.

Roadmap (Data Architect — senior-tier, путь через Senior Data Engineer): 1) Стать сильным Senior Data Engineer — prerequisite. 5+ лет hands-on: data pipelines, warehouse work, SQL mastery, понимание data tooling на практике. 2) Data modeling mastery — это core Data Architect skill. Dimensional modeling (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 modeling. 3) SQL deep — Data Architect должен глубоко понимать query patterns + performance + optimization. 4) Cloud data platforms — выбрать один deeply: Snowflake (leader — Snowflake certifications) или Databricks (Lakehouse — Databricks certifications) или BigQuery. Hands-on опыт design + build. 5) Modern data stack — dbt (de-facto transformation + modeling layer 2026 — dbt certification), data orchestration (Airflow / Dagster), ELT patterns, CDC (Debezium). 6) Data architecture patterns — глубоко понять warehouse vs lake vs lakehouse vs data mesh vs data fabric (когда что). «Fundamentals of Data Engineering» Joe Reis / Matt Housley (canonical 2026 — must-read, covers architecture). 7) Data mesh — «Data Mesh» Zhamak Dehghani (если работаешь / будешь работать в крупной организации). 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-ФЗ). 9) Open table formats — Apache Iceberg (rising 2026) / Delta Lake / Apache Hudi — критично для lakehouse. 10) Semantic layer — dbt Semantic Layer / Cube — metrics consistency. 11) Soft skills — data — cross-functional (engineers + analysts + business + security), нужны stakeholder management + data strategy communication + governance facilitation. 12) Practice в текущей роли — как Senior Data Engineer брать architecture-level задачи: data model design, platform selection, governance setup. Курсы РФ: Otus «Data Architect» / «DWH Analyst», Karpov.Courses (Data Engineering — overlap), корпоративные data-школы, Arenadata training. International (eng): «The Data Warehouse Toolkit» Kimball (canonical dimensional modeling), «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+ лет) + data modeling mastery + cloud data platform expertise → Data Architect.

7 активных открытых Data Architect-вакансий с явной data-architect-спецификой — узкая senior-ниша. Реальный рынок шире — many data-architecture roles classified как Senior Data Engineer / Data Platform Engineer / Lead Data Engineer (titles overlap). География: 🇷🇺 Россия / 🇵🇱 Польша / remote. Реальный рынок шире за счёт международного remote-сегмента (cloud data vendors + EPAM-style outsourcing data-platform projects — full-remote-friendly). Время закрытия Senior Data Architect — 8-14 недель (seniority + data modeling depth assessment + cloud platform expertise verification).

Senior Data Architect владеет полным циклом data architecture + technical leadership. Data modeling mastery: dimensional modeling (Kimball — star / snowflake schemas + facts/dimensions deep), 3NF / Inmon enterprise DWH, Data Vault 2.0 (hubs / links / satellites — agile DWH), conceptual / logical / physical modeling, ER modeling. SQL deep mastery: complex queries, query optimization, understanding execution plans — Data Architect должен глубоко понимать как данные queried. Cloud data platform mastery: один из Snowflake / Databricks / BigQuery deeply — architecture design, performance optimization, cost optimization (data platforms — expensive, cost-architecture критичен). Data architecture patterns: warehouse / lake / lakehouse / data mesh / data fabric — знать trade-offs + когда что применять (не cargo-cult). Lakehouse design (open table formats — Iceberg / Delta Lake / Hudi). Modern data stack: dbt (transformation + modeling + 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-ФЗ compliance в data architecture), data contracts (formalize 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 для data tooling, data team operating model (centralized vs data mesh decentralized). System design для data: design data platform на whiteboard под scale (PB-scale data, 1000s of tables, real-time + batch), capacity planning, performance + cost trade-offs. Cross-domain knowledge: понимание 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 к leadership, data governance facilitation, mentoring Data Engineers. Английский для Senior+ MUST — cloud data platform docs + data community + international team communication англоязычные. Optional bonus: cloud data platform certifications (Snowflake / Databricks), dbt certification, conference speaking (data conferences), data mesh implementation experience — резко повышают market value для Principal / Chief Data Architect roles.