If there's one term next to agile
that's so overloaded nobody knows what to expect, then it must be architect
. Yes, you can specialize it by prefixing it with software
, as in software architect
. And with that, you would be able to determine that he or she is probably designing some kind software system. But you still wouldn't be able to understand what that means exactly
. You have solution architects, system architects and enterprise architects, and to make matters worse, you even have agile
architects. And within that realm, you can also designate a seniority level. So, you could start as a junior software architect, then move on to become senior software architect, then become the lead architect and eventually end up being the chief architect. But nothing means less then somebody introducing himself as "I am the chief architect" without explaining what that means.