When hiring an Enterprise Architect (EA), what is most important for them to have on their CV?
An EA certification18%
Several years of general EA experience72%
Experience with a business similar to yours9%
Sort by:
Content you might like
Which key pentesting capability do current AI-driven vendor solutions most fail to cover?
Very inclined: I believe in constantly pushing for innovation and improvement, even if the current systems are effective46%
Moderately inclined: I'm open to innovation and change, but only if it clearly enhances or adds value to the existing systems48%
Not inclined: If the current systems are working effectively, I prefer to maintain stability and avoid unnecessary changes5%
Which role-based access is most important? (Select all that apply)
Read only19%
Limited admin (eg. Backup, infrastructure, cloud, storage, helpdesk, general)44%
Super admin45%
Security and governance29%
Manager access22%
Application owner26%
Department admin (eg. Finance, HR, operations)13%
Developer admin12%
QA admin9%
Service/support admin9%
Other/custom2%
Depends on which kind of role in my EA organization I am filling, but in some cases, industry knowledge is very important (if in a "true" Enterprise Architect / Strategic Architect or business aligned architect role). In other cases, such as solving for a more technical / Solution Architect-type role, general EA knowledge can be more important. A good Enterprise Architect should be able to operate in nearly any kind of technology:business alignment need or opportunity, and quickly sort out what is important and required for it, bringing the right people together and "framing the debate" for the options to move forward. In many cases, this is where an EA adds value, at a minimum putting an objective, strategic process into place to help drive a desired outcome, balancing the tactical and the strategic needs of an organization.