How to Hire Enterprise Architects: Signals and Tests

Enterprise architecture earns its keep by making portfolio-level decisions that stick: what exists where, what gets retired, and which standards apply. It fails when it becomes a review checkpoint. This guide covers hiring for the first version, drawing on FISTA Solutions' forward deployed engineers work.

How is this different from solution architecture?

Dimension	Solution architect	Enterprise architect
Scope	One system	Portfolio of systems
Key decisions	How to build this	What should exist at all
Primary skill	Technical trade-offs	Trade-offs plus influence
Output	A buildable design	A simpler, cheaper estate
Failure mode	Unbuildable design	Governance theatre

See hire solution architects for the other role.

What should you test in an interview?

Ask what they retired. Portfolio simplification is the hardest and most valuable thing the role does, and it requires authority, evidence, and persistence.

Candidates who have never decommissioned a system have not exercised the part of the job that produces measurable savings.

Why does architecture-as-checkpoint fail?

Because a review gate without engagement slows delivery while changing little. Teams learn to present designs that will pass rather than designs that are good.

Ask how they engaged with delivery teams. Architects who arrive at the end of a design process have limited influence and generate resentment; those who arrive early have both influence and better information.

Do standards need exception paths?

Yes. Standards without a workable exception process get ignored, and the exceptions become invisible rather than documented.

Ask how they handled a team that needed to deviate. Good answers involve a fast approved path and a record; poor answers involve enforcement.

How do you evaluate portfolio thinking?

Ask how they identified overlapping capability across the estate. Most large organisations have several systems doing similar things, purchased by different departments at different times.

Finding that requires talking to people rather than reading a catalogue, and candidates who describe interviews and usage data have done the work.

What about cost?

Enterprise architecture should produce cost evidence: licences retired, duplicated capability consolidated, integration complexity reduced.

Ask what their work saved. Candidates who cannot answer have been measured on artefacts, which is how the function loses credibility with finance.

How do you handle vendor relationships?

Portfolio decisions involve large vendor commitments, and architects are frequently the technical voice in those negotiations.

Ask about a vendor decision they influenced and what evidence they brought. The useful skill is translating technical constraints into commercial terms.

How does modelling tooling fit in?

It is a means, not the job. Organisations sometimes buy a modelling platform and hire someone to populate it, which produces a detailed model of an estate that nobody changes.

Ask what they did with the model. If the answer is that it informed a decision, good; if it is that it was complete, less so.

How does AI change enterprise architecture?

It adds a fast-moving capability that departments adopt independently, which is precisely the pattern that produces portfolio duplication. Establishing where AI capability lives, what data it may reach, and which decisions require oversight is now a core portfolio question. See what is an ai inventory.

Contract, staff augmentation, or permanent hire?

Permanent, usually, because the role depends on relationships and accumulated context. Augmentation can help with a specific rationalisation programme or a target-state design with a defined endpoint.

What are the common hiring mistakes?

Appointing the role without authority. Measuring on models produced. Hiring a framework specialist rather than someone who has simplified an estate. And positioning the function as a gate.

How do you onboard them well?

Give them the application inventory, the licence spend, and the list of projects that stalled on cross-system dependencies. Those three describe the portfolio's actual problems.

What does good look like after 12 months?

Systems retired, duplicated capability consolidated, standards with a functioning exception path, and delivery teams engaging earlier rather than avoiding review.

When do you not need this role?

When the estate is small enough for engineering leadership to hold in mind.

What should be measured?

Systems retired, duplicated capability reduced, licence and integration cost avoided, and whether delivery teams seek architectural input voluntarily.

What should you do first?

Count how many systems in your estate do broadly the same thing. That number is the business case.

How do you evaluate target-state thinking?

Ask what their target state looked like and how far the organisation got. The informative part is the gap: target states that were never approached suggest a design produced without reference to funding, delivery capacity, or organisational appetite.

Strong candidates describe a target state that moved, with sequencing tied to business events — a contract renewal, a migration already funded, a regulatory deadline — rather than to an ideal end point nobody scheduled.

What about mergers and divestitures?

Portfolio work is at its most demanding when two estates combine or one splits, and those events force decisions that had been deferred for years. Ask whether they have worked through one and what they decided first.

Candidates with that experience tend to have sharper instincts about which duplication genuinely costs money and which is tolerable.

How FISTA Solutions helps

FISTA Solutions supports portfolio and delivery architecture through forward deployed engineers and staff augmentation: rationalisation driven by usage evidence rather than inventory completeness, standards issued with workable exception paths, cost evidence produced alongside technical recommendations, and AI capability governed as a portfolio question rather than accumulating department by department, through AI enablement and AI agents. The record is 150+ projects for 50+ companies across 12+ countries.

To add architecture capacity, message FISTA on WhatsApp, or read hire solution architects.