Why pre-screen enterprise architects before the leadership interview
The distance between an architecture decision and a running system is where this role is judged, and it is easy to spend years on the wrong side of it. Reference models, capability maps and target-state diagrams accumulate while delivery teams route around them. Architects worth hiring can point at systems that exist because of a decision they made, and describe the concession that got it approved. A short screen asks for that before you interview for fluency.
What actually matters when screening Enterprise Architect candidates
- 01
Technical proficiency
Check depth across the domains they claim: TOGAF or Zachman framework use, ArchiMate or C4 modelling, API and event patterns, identity, and cloud landing zones on Azure or AWS.
- 02
Systems and trade-offs
Probe how they weighed build versus buy, monolith decomposition, SAP or Salesforce core versus custom, and technical debt retirement against licence and run costs.
- 03
Evidence and rigour
Test whether their target state was measured: capability heat maps, application portfolio rationalisation counts, LeanIX or Ardoq inventories, and post-migration cost or latency figures.
- 04
Collaboration and communication
Assess how they governed without blocking: architecture review boards, standards exceptions, working with delivery teams, and selling a roadmap to CIOs and finance.
Pre-screening questions to ask Enterprise Architect candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Architecture that was built
3 questions01Can you discuss a time when your understanding of the current state architecture changed the future state?
Listen forCurrent state established through real investigation, with a specific finding that changed the plan and what got built.
Current state assembled from documentation alone, or a target state produced with no discovery behind it.
02Can you provide an example of an IT project you shaped from conception to completion?
Listen forA system that shipped with their architectural decisions named, plus what changed during build and why.
Involvement that ends at design approval, or no project they followed through to production.
03Could you describe a time you shaped a project that considerably improved business operations?
Listen forA measured operational change with the baseline, and their own contribution separated from the delivery team's.
Business benefit claimed with no measure, or credit taken for a team's delivery work.
Trade-offs and cost
3 questions04Can you describe a time when you had to manage architectural trade-offs?
Listen forA specific decision with what was given up, and an honest account of what that cost once the system was running.
Trade-offs described with no downside, or decisions justified only by a principle.
05What is your approach to risk management in architectural decision-making?
Listen forRisks named with the ones they accepted deliberately, and a case where an accepted risk later materialised.
Every risk mitigated, or risk registers maintained with no decision attached to them.
06Can you describe your experience with data architecture and information systems?
Listen forOwnership of data across systems addressed concretely, including how they handled duplicated master data.
Data treated as an application concern, or integration solved by copying data between systems repeatedly.
Governance that helped
3 questions07Have you ever established governance processes in a previous role?
Listen forGovernance proportioned to risk, with fast paths for low-risk change and a specific decision it stopped.
Every change reviewed at the same depth, or governance that teams routinely bypassed.
08What steps would you take to conduct an architecture assessment?
Listen forAssessment grounded in what teams actually run, with findings prioritised by business impact rather than tidiness.
Assessment against a reference model only, or recommendations that amount to standardising everything.
09How do you ensure compliance with information privacy and security standards in your architecture?
Listen forRequirements built into designs early, with an example of an architecture changed because of a privacy constraint.
Compliance handled as a review at the end, or privacy treated as the legal team's problem.
Trusted by the business
3 questions10What experience do you have aligning technology strategy with business goals?
Listen forBusiness objectives named specifically, with a technology decision that was changed because of a commercial constraint.
Alignment described in the abstract, or technology strategy set without business input.
11How do you communicate complex technical information to non-technical stakeholders?
Listen forExplanation framed around the decision and its cost, with a case where a leader changed course because of it.
Diagrams presented to executives, or complexity simplified to the point of hiding the real trade-off.
12What types of enterprise architecture frameworks are you familiar with?
Listen forFrameworks used selectively with a view on which parts they discard, tied to an organisation they applied them in.
A framework followed completely regardless of context, or frameworks named with no application.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Technical proficiency
35%5Names frameworks and notations they personally modelled in, and explains integration, identity and data patterns without retreating to slideware abstractions.
Systems and trade-offs
25%5Walks through a documented decision record with options, costs, risks and the constraint that decided it, including trade-offs they later regretted.
Evidence and rigour
25%5Quotes portfolio numbers before and after (applications retired, integrations consolidated, run cost saved) and cites where the roadmap slipped and why.
Collaboration and communication
15%5Describes review boards they chaired, dissent they absorbed, and cases where they approved a deviation from standard with clear conditions.
Target-state diagrams accumulate while delivery routes around them, and both look the same in an interview. A one-way video screen asks what was actually built.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for an enterprise architect take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish which of their decisions were implemented, hear one real trade-off, and check whether their governance helped or hindered delivery.
How much should framework knowledge count?
Less than it appears on a resume. Frameworks are learnable and widely certified. What is scarce is an architect whose decisions delivery teams accepted, which no certification demonstrates.
Evaluating answers
What is the strongest signal when screening an enterprise architect?
Systems that exist because of their decision. Ask what was built, by whom, and what they conceded to get agreement. Architects who cannot answer have been documenting a future state rather than shaping one.
How do I judge their governance approach?
Ask what their review process rejected and what it approved quickly. Good governance is mostly fast lanes with a few real gates. A board that reviews everything at the same depth is a queue with a committee attached.
























