What defines a 'software architect' and can I put it on my CV?

Question

Bear with me with this question....

I lead a team of 4 developers and am largely responsible for making all the design decisions (design documents, UML modelling, integration with existing systems etc) for all our projects as well as initiating some of the projects in the first place. I also do a lot of development and testing and all the usual developer tasks.

Can I claim the role of 'architect' if not the title? What kind of things would I have to have on my CV to justify this? If not what makes an 'architect'?

I guess that's three questions :)

Answer 1

Wouldn't you usually put your actual job title on there, and then just explain what you did? It's up to the reader to determine that you did a lot of architecting.... IMO it would be misleading to list a title on there if you have a different official title. Even if that title doesn't define what you actually do.

If you have a job where you get to define your own title, then you can basically call yourself whatever you want and it doesn't really matter.

Answer 2

Good question. I've been doing more and more of this over the last two years or so, and have been wondering the same thing. Perhaps it's just a symptom of reaching a certain level of seniority? I think I'd claim it in the "body" of a job I'd done, rather than in the job title - unless your title is actually "Architect". Be careful, lots of people have negative experiences with software "architects" - lots of nit-picking, arguing the toss over the smallest thing, never actually releasing any software. I'm not suggesting that either you or I suffer from any of those, or if we are we're definitely working on getting better :-)

Answer 3

I would argue that from a business point of view, you've got experience in fulfilling the duties of an architect and you would now want to apply for a position that formally recognises those duties.

I think it would be a mistake to put yourself forward already as being a solution / software architect because an employer would want to see that you have actually achieved recognition of that role.

Answer 4

The word architect is in itself pretty dangerous, because many people are wary of those 'pure architect' positions where people sit and just draw UML all day long instead of actual coding, thus losing touch with reality. You can say that you *architect**ed*** something - that's better. But saying 'I'm an architect' sounds a bit like 'I'm a software theoretician' to me.

Answer 5

As an aside: You can become certified by Microsoft: http://www.microsoft.com/learning/mcp/architect/default.mspx

Their definition might help with getting a good context for 'architect'

These MCA professionals typically have five or more years of advanced IT architecture experience, possess expert technical and leadership skills, and become part of an exclusive, world-class community of experts who continually collaborate on best practices within the IT industry. MCA candidates must definitively showcase seven competencies of business acumen and technological proficiency to a panel of industry experts in a Review Board interview in order to achieve the MCA credential. MCA certification was built by and for industry architects.