Typically, in a software development company, there are 2 growth path that a person starting as a Software Engineer can take. Either they can choose to continue being more technical (Software Architect) or focus more on the managerial activities (Project Manager). There is something in between also - Technical Manager - and this role depends on the size of the project / company to a great extent.

I don’t understand why we Indians have a fascination with the title of Project Manager over a title of Software Architect. I think it stems from ignorance of people and the inability of companies to articulate the clear difference between the 2 roles. Let me say this, if it is not clear, both these positions are equivalent positions. By that, I mean that there is no difference between the amount of responsibilities, salary, bonuses, stocks or any other finanical variables between the two. If at all somebody wants to differentiate, Software Architects are the ones who are paid more - just because of the fact that they are more difficult to find. And this is made clearer by the fact that a lot of companies have higher referral bonuses for Software Architects than Project Managers. What is different is the kind of responsibilities they both have.

A Project Manager is almost always focused on one project and is the person responsible for the successful delivery of the project and, quite often, tracks it on a daily or weekly basis. He is responsible for gathering requirements, directly or indirectly, from the customers / clients and making sure that those are incorporated in the product. A Software Architect is the one who may or may not interact regularly with the clients, depending upon the technology used but is responsible for the high level architecture of the products. He works with the clients / Project Managers and helps make the selection of technology, gives early feedback on the product architecture. Typically, a Software Architect is not associated with a project but is the one helping multiple projects but is not responsible for the delivery of any.

People have different preferences based on their career aspirations but something that I will want to point out is that it’s easier to move to Project Management from the Technical side but things are not the same the other way. Of course, being a Technical Manager is just another thing.


  1. Amit Goyal

    I would like to become Software Architect :)

  2. Manish Jethani

    >just because of the fact that they are more difficult to find

    So true - here in Adobe India we’ve been looking for an architect to work with us on the Flex UI framework, but not a single candidate…. In the end, I think it’s much better to groom someone from within the organisation than hire someone new.

  3. Nibha

    Very good article to define differences between Software Architects and Project manager. Before I was unaware of these things. I knew that in software industry the most significant position is Project Manger and thats the Indian mindset in reality.

  4. Ankur Agrawal

    I think one of the reasons is based on simply how the Indian market differs from the American one.

    First, services organisation need a lower number of architects as compared to a product organisation, just based on the kind of work they do.

    Second,
    It is more difficult to create a ladder for the technical track, specially in a services organisation. In the management track, you have PM, then GPM, then perhaps SBU head and so on. What are the corresponding levels in technology ?

    Mid-sized services firms will anyway find it more challenging to provide a technical ladder, as the average project wouldn’t be large or complex enough to require senior architects.

    I think this will start changing only as we move up the value chain: the more R&D based work that takes place, the easier it is to find value in an architect role.

    Right now, going to an architect role reduces your exit options, hence increasing risk. ( Not too many organisations need an architect, and where they do, the architects/PM ratio is always way less than 1.)

    BTW, In services organisations in India, typically the PM and EM roles are combined into one. Some, like Sapient, have Program Managers and Technical Managers as different roles, but they are the exceptions.

  5. Ankur Motreja

    Well, its not that surprising :-)
    Lets say our guy or gal meets someone a generation older at a party.
    The obvious question: “What do you do ?”. Answer: “I’m a Software Architect”. The questioner has a puzzled look but smiles anyway and asks the next person “And what do you do ?”. Answer: “I’m a project manager”. “That’s fantastic !!”.

    Now consider why our guy or gal became a software engineer in the first place. Was it because they enjoyed programming ? Maybe loved to see their thoughts translated into actual working software ? Enjoy watching other engineers find it easy to maintain their software and customers find it sufficiently flexible to meet their changing requirements ? Well, not really. They found it to be the most prestigious title among the ones available to them as career options.

    So, given the choice, why shouldn’t one find “Project Manager” more likeable than “Software Architect” ? :-)
    Ankur

  6. Jatinder Kapur

    If your assessment that more Indians want to become Project Managers is correct, this is great news for India and also for the world. I think this news is much bigger news than the earlier news that most young Indians want to choose engineering or computer science profession.

    Why this is a great news for India?

    Although, considered good technically, there is a perception in the west that Indians are not good communicators and hence poor managers. Most companies hesitate to outsource projects to India fearing Indian managers don’t communicate full truth about the project progress. Also Indian managers are sometimes overly optimistic about project timelines and costs. And when there is a cost overrun, Indian managers have hard time explaining the cause of the variance. I believe Indian IT industry will hit a ceiling soon (if it’s not already hit) unless Indian IT industry does something to produce world class project managers at a much faster rate. India has to realize that technology is not a competitive advantage in itself. We are already witnessing that IT projects are outsourced to cheaper labor countries like Vietnam, Pakistan etc. And this trend will continue unless India develops its competency in managing quality software projects.

    Why this is a great news for the world?

    Indians have definitely proven worldwide that they are quite capable of writing good software. Corporations in USA and Europe are quite knowledgeable of this fact and that’s why they are opening more and more Software development centers in Bangalore. However, for the same reason, Indians in US and Europe are now labeled techies. It is hard for companies to shed its stereotypical mentality to promote deserving Indian candidates into management positions. It is a well know fact that only handful of Indians have reached to the ranks of CEO in fortune 500 companies. If this stereotype is ever broken, it will be a great thing for the Indian who are working in US. Ultimately this will be a good thing for corporations, and ultimately good for World Economy.

    To manage continuous IT growth, I wish India produces more Project Managers than it produces today.

    Again, wanting to become project managers and actually capable of managing projects is another discussion topic.

  7. Ashish

    The Software architects are difficult to find cuz, most of them are taking the PM route. And yeah.. I am not the same Ashish.

  8. Deepak Shenoy

    There’s a snob value to the number of people that report to you, in India. People parade these numbers around, in a way that indicates they rate themselves higher if more people report to them. And this snobbery manifests itself in job interviews - “How many people will I be leading?” is a common question at a mid level.

    Architects tend to not have direct reports - they control project or product architecture and design, and will at best be a lateral team lead or mentor, but never reported to. Their role is very important of course, and at this point is a richer post, both salary and responsibility wise, than a project manager.

    PMs tend to become glorified typists whose main work is scheduling (which takes less than 5% of one’s time), resource management (another 5%) and documentation (email, status reporting etc. - another 10%) I think unless a PM controls 10 or more projects there is no need for the project manager to be paid more than, say, a developer on a project.

    Furthermore, all developers should be controlled by Tech architects. I’m talking about skill management and assessment, project resourcing, and eventually, the decision to fire (or hire). This means PMs are only laterally reported to, and only inthe context of a project. The big boss then, is the architect (or in large projects, the Development lead or practice head).

    Also I’ve noted that the vast majority of project managers in India are simply techies who have reached their pinnacle of incompetence. Incapable of being architects and unable, from lack of knowledge or skill, to contribute further as developers, they snuggle down in the PM position which offers them job security without a pressing need to perform. Glib talk and email prowess gets them through today, but will it tomorrow? I have my doubts.

    Note: This doesn’t happen in my company, as we don’t look at technical skills for PM roles, and reporting and structure is altogether different.

  9. hari

    I am currently working for one of top Indian based MNC since 2 years as Sr. Software Engineer.I’m more interested to be a business man. Can you help me, I want to build business, I want be an investor. Please ref. some sites or person who can help me(specific guidelines), to reach my goal. Please……

  10. Rangarajan R

    Wonder if it has anything to do with the possibility that being a project manager provides more mobility (moving to a diverse firm with ease) than if you were a software architect. Also in India, where there is significant middle management layer (and will continue to be for some time to come), managing people will be rewarding (at least financially). The way I see it, certain people tend not be great project managers as they lack people skills. Chances are, if you have always been technically skilled and become a technical manager, you may look down upon somebody less skilled instead of inspiring them to do their best. And yes, a variety of life experiences are likely to make a better project manager of you compared to if you were living in isolation all your life.

  11. Garry Oldman

    Nice site I found … Plan on coming back later to spend a little time there.

Leave a Comment