I started my programming in 2008 and have worked on many big as well as small projects. I work on .NET platform mostly. I've worked in big companies and have done freelancing for 2 years leaving my job. This year I moved to a different country and started job as developer (I took whatever I got). I'm quite sure I'm not a bad developer. I have good feedbacks. I've completed projects and earned appreciation. Last week a new guy was hired in my company as Project Manager and he has only 1 year experience and that too not in programming. In networking and stuff and has done some PM stuff for couple of months.
Now I think I'm not in the position that I should be. I can constantly see things that are going wrong in the company. For example, what the new PM does is constantly come to developer and ask a lot of things rather than documenting it. He hasn't been even able to choose right tool to log issues in 2 months. Uses 2-3 different stuffs. Doesn't communicate the progress to the team. Rather chooses specific developer and goes on with it. In other words, isn't connecting to the team.
If the company decided to hire inexperienced PM, why didn't they promote me or even my fellow developer to do so?
Is this happening because I've got brown skin? Or am I doing something wrong? I'm not so interested to do PM job but I'm concerned I'm not being a good developer, or something lacks in me.
I agree with the other commenters. PM is not a promotion. PM is a very hard, thankless job that is hard to get right. Trust me --- you don't want it. The PM clearly needs help and it seems like you can fill some gaps he has. I do not know the org structure in your company, but I would lobby for you to become the "Lead" developer -- and you can work hand in hand with the PM to make sure the project is organized correctly, that the requirements are being gathered and met, that the tools the developers need are in place. The PM should be able to take the brunt of the "external" networking for the team, and you can take the brunt of the "internal" networking to the team. You can help and learn from each other, as I am sure he has some skills that you do not (they may be soft skills).
What's wrong with being good developer, especially good developer? I have been doing this for 23 years and still love it. Moving from DOS/UNIX->Win32->8051->Embedded OS->vxWorks->Networking->Storaging->Video/Media/Embedded Linux->Android ASOP. Learning new things every months.<p>BTW, if you checkout the salary level at glassdoor.com, a good engineer/developer salary level is higher than most of the "PM", Director. A lot well run company knew this and respect this.<p>Personally, I was moved to Marketing/PM type of roles for a while, hated it. Too Much politic, a lot depending who you know, party with, etc.<p>Good engineers/developers got respect from what you know and how well you code, understanding of issues and formulate/architect a solution. Ok, I am a geek.
It would not ever occur to me to try to 'promote' a developer to PM; it's not a promotion, it's not a normal career path, and most people wouldn't even want to do it. If it appeals to you, let your manager know.
It happens that if you are good at what you are doing you won't be promoted, because it will be hard to find someone to replace you. So you have to clearly signal that you want to move, because for your manager it might be more comfortable to know that you are here, reliable and productive.
What you're doing wrong is not being in the job that you want.<p>Find a position that you want in the company where you are now, or find a position that you want somewhere else. It doesn't have to be a full-on 100% PM job. After all, the guy you mention apparently only has a year experience himself. Everyone starts somewhere and somehow. <i>Everyone</i>.<p>It won't be easy, but it will never happen if you don't try.<p>As for the specific issues you have with that other guy, those are merely details and they will instantly be irrelevant once you move up or out. Forget about that immediately (I literally mean right this second), and put all your energy into finding your next position, internally or externally.<p>Get to work. :)
Sometimes you have to seek what you want. It won't always come to you. If you know they are hiring for PM, go into your manager's office and ask to be considered for the position. Outline the many reasons why you would be qualified. Just bear in mind that knowing a bad PM when you see one does not make you a good PM.<p>A while back, a really senior co-worker left the company I was working at. I knew he worked on things that interested me so I went to the head of the department and asked to take over his work. If I had not stepped up, his work would have been distributed out over the team and I wouldn't have had the opportunities I've had since.
One idea I tend to agree with is the idea that "you are in the position you deserve to be in". If you are in a junior position when you feel like a senior developer, you deserve to be in that position. You might have the skills, but since you've not done anything to put yourself in that position you are where you are.<p>If you want to be a PM, ask to be considered for a PM role. If you don't get it then apply for PM roles elsewhere. You are rarely given help in this world, so take every opportunity you can possibly get.
* Did you talk to your employer about your desire to work as a Project Manager?<p>* Did they provide you with reasons why they don't want you in that role? Since they set the rules, you need to know what they want.<p>* Project Management is more about social rather than technical skills. Are you a good communicator? Does your employer know that?<p>* I don't know anything about your skills, but you've just written 260 words in one wall-of-text paragraph. It wasn't that hard to read, but that's not proper style.
Suggest reading up on Self-Development, ultimately you're responsible for driving your career growth > <a href="http://www.goodreads.com/book/show/847538.FYI" rel="nofollow">http://www.goodreads.com/book/show/847538.FYI</a>