The Chief Architect should know the business and well as the technology. I have been directly opposite CIOs and CTOs of vendors on many occasions.
The Chief Architect is often called on to face off with the senior-level technical people at vendors and partners. Often times, the Chief Architect is called on to explain technology to the CxO-level people.
#CHIEF ARCHITECT JOB CODE#
The Chief Architect has to be comfortable in executive-level meetings, and must be equally comfortable sitting next to a developer and doing pair-programming or code reviews. I always like to say that a Chief Architect has to be able to interact at the CxO level, and be able to talk to the lowest-level coder. The role of Chief Architect is an extremely “vertical” one. Each company has their own idea of what a Chief Architect’s role is, and some companies don’t even know why they need a Chief Architect. I may be slightly biased in my thinking, but in my opinion, the role of Chief Architect is one of the hardest roles out there, both in terms of defining the role and in terms of what is expected of you.
#CHIEF ARCHITECT JOB SOFTWARE#
In addition, I owned my own small software business for roughly ten years, and that experience has also shaped my thinking. I have a mixture of large company and small company experience that has shaped my perceptions. I have been Chief Architect of the Equities Division of Citigroup (350,000 in the company, 30,000 people in Equities), of MetLife (65,000 employees), ADP (65,000 employees), and of a small software vendor named Quantifi (roughly 50 employees).
The following observations about the role of Chief Architect come from my four previous positions as Chief Architect.
0 kommentar(er)
