Enterprise Architect career path: from domain architect to chief enterprise architect
Each step up the enterprise architecture ladder, from domain architect through enterprise architect, senior and lead enterprise architect to head of enterprise architecture and chief enterprise architect: what changes in the job, the gap to close, how to show it on your CV and in interviews, and a plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Domain architect to enterprise architect | Decisions across several domains and business units | 2 to 4 years |
| Enterprise architect to senior enterprise architect | The largest programmes and the board's trust | 3 to 5 years |
| Senior enterprise architect to lead enterprise architect | The practice's method, standards and repository | Several years |
| Lead enterprise architect to head of enterprise architecture | A team of architects and its budget | Several years |
| Head of enterprise architecture to chief enterprise architect | The architecture of a whole group, at the leadership table | When a company asks |
A domain architect looks after one area, such as business, application, data or technology architecture, for one part of the company; it is the usual first step into this ladder for solution, software and data architects.
Two roads run beside this one. Software architects reach enterprise architecture by their own steps, and their road to chief architect and CTO is on the software architect career paths. The people road of technology, from tech lead to VP of engineering and CTO, is on the engineering manager career paths; the two meet in the technology strategy.
Single solutions are designed by solutions architects, whose own ladder is on the solutions architect career paths.
From domain architect to senior enterprise architect
Domain architect to enterprise architect
What changes: you look across domains: the capabilities of a business unit, the applications and data behind them, and the roadmap for all of it.
The gap: enterprise architecturePlan the whole landscape of systems, data and processes against the strategy of the business. as a practice, modellingModel capabilities, applications and technology in ArchiMate so that others can read and reuse it. that business readers follow, and work with business leadersWin executives, business owners and IT leads for one roadmap that they fund and follow..
On the CV and in interviews: a capability map you built, a roadmap you set and the decisions it led to. Expect a case with too many systems.
Plan (12 to 24 months): map one business unit with its leaders; present a roadmap to them; sit on the architecture board.
Enterprise architect to senior enterprise architect
What changes: you take the largest programmes, such as a new ERP, a merger or a cloud strategy, and the board asks for your view first.
The gap: business cases in money, changePlan the change for people and processes that every new landscape brings. across units, and technology riskWeigh technology risk, from ageing systems to suppliers, in the roadmap's choices. that supervisors read.
On the CV and in interviews: the programme, the business case and what it saved or made possible. Expect a merger case.
Plan (2 to 3 years): lead the architecture of one large programme; write its business case with finance; brief the executive board.
Lead, head and chief enterprise architect
Senior enterprise architect to lead enterprise architect
What changes: you own how the practice works: its method, its principles and standards, its repository and its board.
The gap: a methodUse TOGAF's method and vocabulary where they help, and leave out what the company does not need. adapted to the company, a repositoryKeep an architecture repository current enough that people trust what it shows. people trust, and influence over other architects.
On the CV and in interviews: the method you set, the board you run and how fast it answers. Expect questions on governance that does not block.
Plan (several years): rework the principles and standards; make the repository current; coach two architects.
Lead enterprise architect to head of enterprise architecture
What changes: you lead the team of architects: hiring, budget, priorities, and the practice's standing with the CIO and the business.
The gap: running a team and a budget, and reporting the practice's value in figures.
On the CV and in interviews: the team, the value it delivered and the architects you developed.
Plan (several years): lead a group of domain architects; report the practice's results each year; build a hiring plan.
Head of enterprise architecture to chief enterprise architect
What changes: you set the architecture of a whole group of companies and sit at the technology leadership table for mergers, platforms and the strategy.
The gap: group-wide decisions, deals, supervisors and a team of heads.
On the CV and in interviews: the group strategy, the deals and the practice across countries.
Plan (when a company asks): lead the architecture side of an acquisition; align the units' roadmaps; develop the next heads.
Titles differ: some companies say chief architect, director of architecture or head of IT strategy for parts of these steps. Read the scope in the ad, not only the title.
Your CV for the next step
Moving up in enterprise architecture shows on a CV as wider landscapes, larger programmes, then a practice and its people. Three rules:
- Name the landscape and the decision. Units, countries, systems retired, platforms chosen.
- Speak the next level's language. Domain ads say "model", "document", "domain"; senior ads say "roadmap", "programme", "business case"; lead and head ads say "practice", "governance", "team".
- Tie an outcome to every line. Money saved, risk removed, a programme delivered.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| PracticePlan the whole landscape of systems, data and processes against the strategy of the business. | Improved the EA practice. | Reworked the architecture board and principles; projects now come in early, unasked. |
| RepositoryKeep an architecture repository current enough that people trust what it shows. | Owned the EA tool. | Made the repository the single source for application owners and costs across the group. |
| Team | Led architects. | Led six domain architects and grew two of them into enterprise architects. |
| Group strategyPlan the change for people and processes that every new landscape brings. | Shaped strategy. | Set the platform strategy for a group of five companies after two acquisitions. |
Key takeaways
- The ladder runs domain architect, enterprise architect, senior and lead enterprise architect, head of enterprise architecture, then chief enterprise architect.
- Each step widens what you answer for: a domain, a landscape, the largest programmes, the practice, a group.
- The software architect and engineering manager ladders run beside this one; their pages are linked above.
- Business results, such as systems retired and money saved, move you up more than framework knowledge.
- From lead upward, the practice and its people are the job.
Frequently asked questions
- What comes after senior enterprise architect?
- Lead enterprise architect, who owns the practice's method, or a move into heading the architecture team.
- Do I need a framework certificate to move up?
- Many architects hold one and many ads name one; the step itself is decided by the programmes you led and the trust you earned.
- Do I have to manage people to move up?
- Not at first; senior and lead enterprise architects are experts. The head step brings a team.
- Where do enterprise architects come from?
- Mostly from solution, software or data architecture, from domain roles, or from senior IT consulting.
- What should my CV show for a head of enterprise architecture role?
- The practice you built, the team you led and the value the business saw from it.