Enterprise Architect

The roles differ in scope and time horizon. Solutions Architects design specific systems to solve specific business problems — typically working at the project or product level over weeks or months. Enterprise Architects design the patterns, principles, and standards that govern how all systems are built across the organization — typically working at portfolio or business-unit level over years. Solutions Architects spend more time on technical depth and design choices for individual workloads. Enterprise Architects spend more time on standards, governance, business-IT alignment, and the political work of getting many teams to follow common patterns. Most Enterprise Architects spent 5–10 years as Solutions Architects first, and the credential mix reflects that progression.

For Enterprise Architect roles specifically, yes — far more than for Solutions Architect roles. TOGAF is the dominant enterprise architecture framework certification globally, and at the EA level it shows up in job postings at financial services firms, government agencies, healthcare organizations, large traditional enterprises, and major consulting firms (Accenture, Deloitte, PwC, IBM Consulting, Capgemini). The certification itself is structured in two parts — TOGAF 10 Foundation and TOGAF 10 Certified — which together take 4 to 8 weeks of focused prep. Enterprise Architects who hold TOGAF plus a cloud architect cert plus a security or AI governance credential are the profile most consistently associated with $250K+ EA roles at large organizations.

It has rapidly become a core EA responsibility. NIST AI Risk Management Framework (AI RMF) and ISO 42001 (AI Management System) are now the two most-referenced governance frameworks for enterprise AI deployment, and both are squarely the Enterprise Architect's territory — they govern how AI is adopted, how risks are assessed, how models are documented, and how compliance is demonstrated. Enterprise Architects who can speak fluently about NIST AI RMF profiles, ISO 42001 certification, and the EU AI Act are increasingly differentiated in the market. Practitioners targeting heavily regulated industries (financial services, healthcare, government) are especially well-served by adding ISO 42001 Lead Auditor or NIST AI RMF certifications to a traditional EA credential stack.

Possible but unusual. Most successful transitions happen after a Solutions Architect has spent 3 to 5 years operating at senior or principal level — long enough to have led complex projects, established cross-team patterns, and built credibility with executives. The skills required at the EA level shift considerably: less hands-on technical depth, more political fluency, more business literacy, and significantly more written and verbal communication. The most common stumbling block is communication scope. Solutions Architects who can run a design review for engineers often struggle to brief a board on architecture strategy. The credential most associated with smoothing the transition is TOGAF, because it teaches the structured language that EAs use to communicate with non-technical executives.

Rarely, and not as a primary responsibility. Most Enterprise Architects produce reference architectures, decision documents, governance policies, and presentation material — not production code. That said, the EAs who maintain enough technical fluency to read code, prototype designs in cloud consoles, and validate architectural assumptions hands-on tend to be more credible with engineering teams and produce more grounded architecture decisions. The risk for EAs who fully step away from technical work is becoming too abstract — designing patterns that look good in PowerPoint but fail in practice. The best practitioners spend perhaps 10–20% of their time on hands-on technical activity, deliberately, to keep that grounding.

The repetitive parts — drafting initial reference architectures, generating boilerplate governance documentation, summarizing portfolio inventories, comparing vendor offerings — are increasingly automated by AI-augmented tools. The judgment-heavy parts — choosing which standards to enforce versus which to leave flexible, navigating organizational politics that determine whether architecture decisions actually stick, communicating tradeoffs to executives whose incentives may conflict, and defending years-old decisions when business conditions change — are getting more valuable. Enterprise Architecture has always been less about producing options and more about making committed choices on behalf of an entire organization, with the political capital to make them stick. Those skills are extremely difficult to automate. EAs who treat AI as a productivity multiplier — using it to draft, compare, and summarize — while focusing their human time on stakeholder leadership and decision defense are seeing compensation rise.