Enterprise Architect
Stakeholder meetings, capability maps, multi-year roadmaps, vendor reviews.
Either a genuinely senior strategic seat or a polite retirement title. Which one depends entirely on the org and the reporting line.
- Domain
- Foundations
- Entry
- £24–36k
- Senior
- £55–78k
- You've already been a credible solutions or domain architect for years
- You're comfortable with politics, governance and long horizons
- You can write strategy that engineering teams will actually implement
- You enjoy translating between technology and business at board level
- You want hands-on work or short feedback loops
- You've never owned delivery, the seat will eat you
- You'd find drawing target-state diagrams forever genuinely fine, that's a warning sign
What "doing well" looks like in the seat
- Your roadmaps survive a CIO change
- Engineering teams pull from your patterns voluntarily
- You can hold your own with finance and procurement
- You're the person leadership asks before signing the contract, not after
The seat is only as good as the executive cover behind it. Without a CIO or CTO who treats EA as a real function, you'll spend years producing documents that influence nothing. With one, you're one of the most leveraged people in the org. Interview the executive sponsor as much as the role. If you can't get a clear answer on what last year's EA work actually changed, the seat is decoration.
Tradeoffs at a glance
Hover any chip for the calibrated meaning. Ratings are directional, not absolute.
Promotion ceiling
Very high, director / chief architect is a clear lane.
Who actually gets in
- +Senior solutions architect
- +Senior infra lead
- +Consulting partner
Common misconceptions
- −That it's hands-on architecture, it's mostly strategy and politics.
Where this leads
- CTO office
- Consulting
- Pre-sales
Certifications people pair with this
Listed because the graph connects them to this role, not because you need all of them. Most practitioners pick one or two.
Pathways that pass through here
What this is based on
Practitioner judgement. External evidence review pending.
Last reviewed: not yet reviewed · UK market
The next step
You've read about the role. The harder question is whether it's the right one for you.
A Career Verdict is the written, practitioner-authored call on your specific route into and out of this role. Six primitives, same format every time.
A route shows what is possible. A Career Verdict makes the call.
Career Verdict
Helpdesk → Security Architect
- 01The callA clear judgement on whether your route is realistic, and under what conditions.
- 02Where the route breaksThe most likely point to stall, and why it happens in practice.
- 03What to do nextSpecific priorities for the next 6–24 months, and what to drop.
Career Verdict
- The callA single written judgement on whether the route is realistic for you.
- Plateaus and failure modesThe flat years and the specific ways this route tends to stall.
- Where you standThe strongest and weakest parts of your current position, named.
- Salary realityWhat this route actually pays, set against what you've been told it pays.
Usually within minutes of payment. Kept 24 months, then deleted. Deletion on request at any time.
Built on POST's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.