Type A

Type B

I’m mostly concerned with structural problems of building software.

I’m concerned both with the structure and intent of software, aligning business needs with choices in technology.

I am experienced at depth in a narrow set of technologies, within which I typically code for inclusion in production systems.

I am experienced across a broader spectrum of current technologies, however I typically only use code to demonstrate concepts.

My key audience are developers; I help them design and build better software through the implementation of key patterns and best practices.

I have to communicate up (towards stakeholders), across (towards other architects) and down (towards developers) with equal proficiency, linking and bridging all three audiences.

I have to be up-to-date with emerging technologies so I can make informed technical decisions when building new solutions.

My key concern is understanding various business and industry trends, as well as technology mappings, so I can translate business intent into the right solutions.

Majority of my role’s responsibilities are tactical – I figure out how something has to be built, focusing on the design and construction of its internal structure.

Majority of my role’s responsibilities is strategic – I figure out what is going to be built, focusing on the approach and overall design of the external structure and its environment.

Concerning security, all architects should know what TLS, PKI and XSS are.

Concerning security, all architects should know what CIA, STRIDE and DREAD are.

I use my company’s or my client’s development methodologies for implementation, with little or no change.

I am responsible for tailoring the correct development process for my company or client, based on project size, project team skills, etc.

I mentor individuals on development and design techniques.

I mentor individuals on design and architectural principles.

I work with a focus on my team and my team’s deliverables and escalate cross-team issues to my manager or other affected party.

I have a mandate to negotiate with other teams, with the goal of finding win-win outcome in conflicting situations.

I am (or will be) MCT, MCAD, MCSD or MCDBA certified.

I am (or will be) MCA or ITAC certified.

Definition of Architect according to IASA and Opengroup does not describe me or my architectural work; they focus too much on enterprise-level architects.

IASA and Opengroup nailed the profession of IT architects; skills and proficiencies as described by them are good reflection of my day-to-day work.

Microsoft Certified Architect program and ITAC certification, their requirements and expectations are not aligning well with my view of what architects should be measured upon.

MCA and ITAC are good quality bar for my understanding of what architect is; I’m either already certified or I plan to go through MCA or ITAC certification in the near future.