Enterprise Architect: рынок

Вакансия

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

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

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

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

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

Окно

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

Топ-навыки: enterprise architect, cloud, togaf, azure, aws. EA frameworks — core: TOGAF (доминирует — ADM Architecture Development Method, TOGAF 10; TOGAF Foundation + Practitioner certification — de-facto requirement для EA вакансий), Zachman Framework (classic ontology), Gartner EA approach, FEAF (US government), lightweight / agile EA (тренд 2024–2026). Modeling notation: ArchiMate (The Open Group — стандартная EA-нотация, Business / Application / Technology layers), BPMN (process modeling), UML, C4 model. EA Management tools: LeanIX (SAP-owned — leader 2026), Ardoq (data-driven — rising), Bizzdesign Horizzon, MEGA HOPEX, Sparx Enterprise Architect, Avolution ABACUS, Orbus iServer, Software AG Alfabet. 4 TOGAF domains: Business Architecture (capabilities + processes + value streams), Data / Information Architecture, Application Architecture (portfolio + interactions), Technology Architecture (infrastructure + standards). Core practices: application portfolio management (APM — TIME model — Tolerate / Invest / Migrate / Eliminate), capability mapping, technology roadmapping, technology radar / standards, architecture governance (Architecture Review Board — ARB), org-level technical debt portfolio. Strategic concepts: business-IT alignment, digital transformation strategy, M&A IT integration, build-vs-buy, vendor strategy. Technical foundation: broad understanding всех IT-domains (cloud / data / security / integration / software architecture) — breadth over depth, EA не пишет код. Soft skills — критичны (80% роли): executive communication (C-level — CIO / CTO / CFO), stakeholder management across business + IT, influence without authority, facilitation (architecture workshops + ARB), negotiation, business acumen (P&L / business strategy / industry dynamics).

Уровни abstraction (от code к strategy): Software Architect — одна система: компоненты + паттерны + код-level design. См. Software Architect. Solutions Architect — одно решение под business problem: end-to-end design, часто cloud, часто client-facing. См. Solutions Architect. Enterprise Architect (эта страница) — вся организация: сотни систем + business capabilities + technology standards + roadmaps + governance. Strategy-level. Business Architect — sub-domain Enterprise Architecture, focus на business side (business capabilities + processes + operating model + value streams) — bridge между business strategy и IT. Reality 2026 (abstraction ladder): Software Architect (код / система) → Solutions Architect (решение) → Enterprise Architect (организация). Каждый уровень — больше breadth + strategy + communication, меньше code. Overlap heatmap: Enterprise Architect ↔ Solutions Architect: 40% (EA задаёт standards + landscape, SA проектирует solutions внутри). Enterprise Architect ↔ Business Architect: 60% (Business Architecture — один из 4 TOGAF доменов). Career-progression: типичный путь Software Architect → Solutions Architect → Enterprise Architect (каждый шаг — расширение scope). Anti-pattern: «ivory tower Enterprise Architect» — рисует diagrams, оторван от реальности delivery teams. Modern EA — pragmatic, engaged с delivery, lightweight governance. Career-выбор: Software Architect if нравится deep technical + код; Solutions Architect if breadth + cloud + client work; Enterprise Architect if strategy + business alignment + org-level impact + готов отдалиться от code.

Decision tree для EA framework approach 2026: 1) TOGAF (The Open Group Architecture Framework) — доминирует индустрию (~80% EA job postings упоминают TOGAF). Core — ADM (Architecture Development Method — 8-phase cycle: Architecture Vision → Business → Information Systems → Technology → Opportunities & Solutions → Migration Planning → Implementation Governance → Change Management). Pros: industry standard, comprehensive, certification recognized globally (TOGAF Foundation + Practitioner). Cons: heavy / bureaucratic если применять literally, big-design-upfront tendency. Use case: must-know для любого EA (vocabulary + cert требуют вакансии). 2) Zachman Framework — classic (1987) — ontology / taxonomy (6 columns What/How/Where/Who/When/Why × 6 rows). НЕ методология — classification schema. Use case: thinking tool для completeness checking. 3) Gartner EA approach — pragmatic, business-outcome-driven (vs TOGAF process-driven). Focus «EA delivers business value». Use case: value-focused EA без TOGAF bureaucracy. 4) FEAF / DoDAF — government-specific (US Federal / Defense). 5) Lightweight / Agile EA (тренд 2024–2026) — самый важный shift в EA 2026. Реакция на провал heavy TOGAF в agile-организациях. Принципы: incremental architecture (не big-design-upfront), value-driven, minimum viable governance, EA embedded с delivery teams (не ivory tower), «just enough» documentation, fast feedback. Use case 2026: большинство modern organizations движутся к lightweight EA — но всё равно используют TOGAF vocabulary + ArchiMate notation. Default 2026 рекомендации: знать TOGAF (cert + vocabulary — non-negotiable для EA career), применять lightweight / agile EA (pragmatic incremental value-driven), использовать ArchiMate для notation, Gartner mindset (business-outcome focus). Реальность: «TOGAF as a toolbox, not a religion» — берёшь полезное (ADM phases как checklist, building blocks concept), отбрасываешь bureaucracy. Modern EA балансирует governance с agility.

Да, 16% Enterprise Architect-вакансий — full-remote или гибрид. EA work — strategy + modeling + documentation + meetings = технически remote-friendly. Caveat — EA это самая stakeholder-heavy роль: Enterprise Architect проводит огромное количество времени в meetings с C-level + business + IT leadership + architecture boards. Executive relationship-building, политическая навигация, workshop facilitation — легче face-to-face. Поэтому EA-роли чаще гибрид (vs full-remote) — особенно in-house EA в крупных организациях (банки / госкорпорации хотят EA физически присутствующим на executive meetings). Аутсорсеры — больше remote. Management consulting EA (Accenture / Deloitte) — традиционно travel-heavy, но post-2020 больше remote. Российские банки + госкорпорации — гибрид/офис (EA — часть управленческого контура). Международный enterprise — гибрид-standard. Релокант-хабы: Германия (Enterprise Architecture очень сильна — SAP + industrial) / Польша / Канада / ОАЭ. Английский для international EA-remote — абсолютно критичен — EA это executive-facing + strategy-communication роль.

Enterprise Architect (individual contributor) — owns часть EA landscape (обычно один domain — Application / Technology / Data — или один business unit). Делает hands-on EA work: capability mapping, portfolio analysis, roadmaps, architecture reviews для своего scope. Chief Enterprise Architect / Head of Architecture / Chief Architect — leads всю EA function организации: 1) Manages team Enterprise Architects + Solutions Architects (people leadership), 2) Owns Architecture Review Board (ARB) / architecture governance process, 3) Sets EA strategy + operating model, 4) C-level partnership (работает напрямую с CIO / CTO как technology strategy advisor — часто reports to CIO/CTO), 5) Owns enterprise technology roadmap + standards, 6) Budget influence (technology investment decisions), 7) Vendor strategy at org-level. Меньше hands-on modeling, больше leadership + strategy + politics. Career path: Enterprise Architect (5+ лет) → Lead / Principal Enterprise Architect → Chief Enterprise Architect / Head of Architecture → либо CTO (особенно в средних компаниях — EA-to-CTO путь распространён), либо CIO advisory / Chief Technology Strategist, либо management consulting partner. Reality: в небольших организациях нет отдельного «Chief EA» — один EA + CTO. В крупных enterprises (банки / телеком / госкорпорации) — formal EA function с Head of Architecture + команда 5-20+ архитекторов + ARB. Career-выбор: оставаться EA IC if нравится hands-on architecture work; идти в Chief EA / Head of Architecture if нравится leadership + org-level strategy + executive partnership.

Roadmap (Enterprise Architect — carrier-capstone роль, путь долгий — через architect-уровень): 1) Стать Solutions / Software Architect — prerequisite. EA не делается из engineer напрямую — нужно сначала 8+ лет накопленного опыта включая architect-роль (понимание как системы строятся даёт technical credibility). 2) TOGAF certification — TOGAF Foundation → TOGAF Practitioner (The Open Group — de-facto requirement для EA вакансий — vocabulary + framework знание обязательны). Resources: official TOGAF documentation + Open Group training partners. 3) ArchiMate certification — стандартная EA modeling notation (часто parallel с TOGAF). 4) Business acumen development — критично для EA (роль про business-IT alignment). Изучить: business strategy fundamentals, P&L understanding, operating models, value streams, industry dynamics. Книги: «Good Strategy Bad Strategy» Rumelt. 5) EA frameworks breadth — Zachman (ontology thinking), Gartner EA approach, lightweight / agile EA (современный тренд — must понимать). 6) Capability mapping + APM — business capability modeling + application portfolio management (TIME model). 7) EA management tools — LeanIX (leader — есть free trial / academy) или Ardoq. 8) Modeling — ArchiMate в инструменте (Archi — free open-source ArchiMate tool — для практики; LeanIX / Sparx для enterprise). 9) Domain breadth — EA должен понимать все IT-домены на достаточном уровне (cloud / data / security / integration / software architecture). 10) Soft skills — критичны (80% роли) — executive communication, stakeholder management, facilitation, influence without authority, political navigation. Книги: «The Software Architect Elevator» Gregor Hohpe (must — связь penthouse strategy с engine room — core EA skill), «Enterprise Architecture as Strategy» Ross / Weill / Robertson (MIT — canonical EA book). 11) Practice в текущей роли — как Solutions Architect proactively брать org-level задачи: technology standards proposals, application portfolio analysis, participate в Architecture Review Board, technology roadmapping. Курсы РФ: TOGAF training через Open Group accredited partners, Otus «Enterprise Architect», корпоративные EA-школы (Сбер / крупные банки растят EA внутри — лучший путь). International (eng): The Open Group TOGAF / ArchiMate official training, «TOGAF 10 Foundation Study Guide», LeanIX Academy (free EA courses), «Enterprise Architecture as Strategy» Ross / Weill / Robertson, «The Software Architect Elevator» Gregor Hohpe. Solutions / Software Architect (8+ лет общего опыта) + TOGAF cert + business acumen → Enterprise Architect.

390 активных открытых Enterprise Architect-вакансий — узкая senior-ниша. Enterprise Architect — роль только для крупных организаций (нужен масштаб сотен систем), поэтому абсолютное число вакансий небольшое (vs Solutions Architect или Software Engineer), но каждая — senior-tier high-comp. География: 🇷🇺 Россия / 🇵🇱 Польша / remote. Важно: значительная часть EA-вакансий заполняется через executive search (headhunters) + internal promotion (организации растят EA из своих Solutions Architects) — не все позиции публичны. Время закрытия Senior Enterprise Architect — 10-20 недель (longest среди architect-ролей — seniority + extensive interview process + cultural / political fit + executive interviews). German market — больше всего EA-вакансий в Европе.

Senior Enterprise Architect владеет полным циклом enterprise architecture + strategic leadership. EA frameworks mastery: TOGAF deep (ADM methodology — применять как toolbox, не bureaucracy), ArchiMate notation fluency, Zachman ontology thinking, Gartner business-outcome approach, lightweight / agile EA principles (балансировать governance с agility). Business architecture: business capability modeling, value stream mapping, operating model design, business-IT alignment — translate business strategy в technology implications. Application portfolio management (APM): application inventory + rationalization (TIME model), technical debt portfolio на org-level, build-vs-buy decision frameworks, vendor consolidation strategy. Technology strategy: technology roadmapping, technology radar / standards governance, emerging technology assessment (как AI / cloud-native вписываются в landscape), digital transformation strategy. Architecture governance: Architecture Review Board (ARB) facilitation, design authority, lightweight governance (enable, не gatekeep), architecture principles definition. Domain breadth: достаточное понимание всех IT-доменов (cloud / data / security / integration / software / infrastructure architecture) для org-level decisions — breadth over depth. EA tooling: LeanIX / Ardoq / Sparx EA — application portfolio management, dependency mapping, roadmap visualization. M&A IT integration: technology due diligence, post-merger system integration strategy, IT landscape harmonization. Financial acumen: technology investment business cases, TCO / ROI analysis на portfolio level, IT budget influence, cost optimization at scale. Strategic concepts: business strategy understanding, industry dynamics, competitive technology positioning, P&L impact of technology decisions. Executive communication — критично (ядро роли): present technology strategy к C-level (CIO / CTO / CFO / CEO), translate technical complexity в business language, build executive trust, «architect elevator» (Gregor Hohpe — связывать penthouse business strategy с engine room technical reality). Stakeholder management: navigate organizational politics, manage competing interests business units, influence без formal authority, build coalitions. Facilitation: lead architecture workshops, ARB sessions, strategy sessions. Soft skills: negotiation, conflict resolution, mentoring Solutions Architects, change management. Technical credibility: несмотря на strategy-focus — EA нужен enough technical depth чтобы Solutions Architects + engineering teams его уважали (anti-pattern «ivory tower architect» без technical credibility — провальный). Английский для Senior+ ABSOLUTE MUST — EA — executive-facing strategy роль, free-level английский обязателен в international context. Optional bonus: TOGAF Practitioner + ArchiMate certifications, MBA или strong business education, industry domain expertise depth, conference speaking (Gartner EA / Open Group) — резко повышают market value для Chief Enterprise Architect / management consulting partner roles.