Prepend
2006-10-12
  Defining Architect roles
A few weeks ago, I read a serverside post that referenced marty andrews' post about defining software architecture roles. These posts happened just in time, as in the past two weeks I've been asked this question over and over.

My employer has been trying to define what exactly an architect is so they can create a career path for other engineers and architects. Currently we have:


This is what the titles are supposed to mean, but in my company (and perhaps yours) they really just mean how much you get paid. So they could just as well be "Architect 0" through "Architect 4".

But there does seem to be a large set of high paid consultants out there who practice "Enterprise Architecture". Sort of big picture guys who are able to go into non-tech huge companies and help with the 25k feet picture. This seems like the only real definition that really fits the term "architect" as far as technical systems are concerned.
 
Comments:
Based on your description, I wouldn't call either of the first 2 levels (assoc. architect & architect) architects. Developer & Senior developer more likely. Until you're desiging major parts of a system or application, you're not an architect in my book. My .02.
 
Post a Comment



<< Home
Technical and personal notes from Brian Lee, technologist/enterprise architect/software developer/soa guy.

ARCHIVES
February 2005 / March 2005 / April 2005 / May 2005 / June 2005 / July 2005 / August 2005 / September 2005 / October 2005 / November 2005 / December 2005 / January 2006 / February 2006 / March 2006 / April 2006 / May 2006 / June 2006 / August 2006 / September 2006 / October 2006 / November 2006 / December 2006 / January 2007 / May 2007 / June 2007 / August 2007 / September 2007 / October 2007 / April 2008 / July 2008 / January 2009 / May 2009 / June 2009 /
My Photo
Name: Brian Lee
Location: Atlanta, Georgia, United States

 
Web prepend.com






Powered by Blogger