Discussion Locked

Programmer vs. Analyst

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am a .NET programmer with over 7 years of experience in development.

I recently changed jobs and was hired to be what I thought was a .NET programmer.

However, I am being pushed more into an analyst role. Management wants me to be a "subject matter" expert regarding the functionality and business rules/features of the application we are developing.

It turns out that the programmers on the project are mostly subcontractors and the analysts and management staff are from my company. The attitude I am hearing is that they can hire "anyone" to do the programming, but the analysts require a combination of tech skills as well as other skills (business knowledge, good communication, the ability to conduct client meetings, etc.)

The problem is that I prefer to be a developer (and that's what I thought I was being hired to do).

I am not sure what to do here. They want me to take on the analyst role for this project -- but I am afraid of becoming rusty in my programming abilities and I am afraid I won't enjoy it. I just started with the company -- I really don't want to have to start looking for another job already.

Any thoughts/opinions/similar situations?

8 replies

by mlayton

In our company, analysts are a different pay scale then programmers and developers, so keep that in mind if its a corporate structure thing. What I would do is talk to anyone you can to find out what this means - are you going to program special projects and functions? What about quick turnaround kind of situations? Who is getting the calls late at night for the customer who needs help NOW? Generally thats not the subcontractor. What about maintenance of the applications delivered by the subcontractor? Consistency over time? All questions you need to find out the answers to because I have a feeling those answers will define your role more than what management has to say.

by amcol

You may have been hired under somewhat false pretenses, which only you can determine if so and take action accordingly. If they told you your job was straight programming and they actually wanted you to be a SME/analyst you may want to move on strictly on the basis of a lack of trust in your employer.

However...I would advise against that, and against shutting yourself off from a career opportunity. That's what you've been presented with, and yet you're eager to stay within your comfort zone. No matter what you want you cannot remain a programmer forever. That job and that career path no longer exists, and hasn't for quite some time. Somewhere along the line you are going to have to reconcile yourself to getting out of day to day coding. Here's a great way to do so.

You may not yet be ready. Fine. In that case, and for the issue of lack of trust, you may want to move on. IMHO that would be a major career mistake, because opportunities don't come along every day and you owe it to yourself to open up the door when one comes a-knockin'.

Don't be afraid to get rust all over your programming skill set. That competence is not what's going to put the groceries on your table in the years to come. Getting away from pure programming is a golden opportunity to develop new skills and broaden horizons. Don't cheat yourself, and don't for a second fool yourself into thinking you can spend your whole career doing what you're doing right now.

Your employer is exactly correct...skills like yours are a dime a dozen, and if you don't work out or they need some new technical skill set you don't have you are bye-bye in favor of the new flavor of the month. All the skills you mention they want you to have as an analyst are marketable and transferable, and all the skills you already possess aren't.

Why are you even thinking about this? You say you're afraid you won't enjoy being an analyst. Aren't you more afraid you might be missing out on something more enjoyable, something that allows you to provide a greater value to your organization? And to yourself and your family?

Fear is always the wrong reason to do anything. It's even more wrong as an excuse to NOT do something. Have faith in yourself.

by dr dij

I started out at current job with a specific skill set. I branched out and learned all I could about biz operations relating to computers. The guy who was with me to support that product was laid off, as that was all he knew. Now I've got my fingers in a bunch of pies, it is more interesting. I'm not getting rusty program wise, in fact the variety is increasing tho I don't sit and code all day. People respect me as someone who knows quite a bit about various aspects of the biz. (And I still have a job).

Straight programming can be outsourced or offshored.

Here's computerworld article stating you need biz skills for IT jobs:
http://www.computerworld.com/careertopics/careers/story/0,10801,110085,00.html

by vncoder

Realisticly, anyone can program. If you meet alot of the teenagers nowaday, they can do scriptings, building PC, set up a LAN, etc. With programming, you can pretty much can work anywhere. At the same time, there are so many others that can program as well.
I started my career only 8 years ago as a programmer. That was what I wanted to do then. However, I was given the opportunity to be a analyst, then to lead and now be a software development manager. Now, I am working on to improve my project management skill.

One of my ex-staff and also ex-colleague programmed for more than 15 years of his life. The constant update of languages, software, tools, etc require him to study all the time. Also, he has to compete with more younger programmers for work. Eventually, he quit programming and got himself a newsagency (not sure that's what you called it in the states).

As the others have said, broaden your skillset and experience give you better/more options in your career.

by tony hopkinson

This is your path to management, to project manager, to team leader, to senior architect. Grasp it with both hands. It's a change but a good one. If you are still knocking out spangly buttons on a UI in five years time you'll curse the day you passed this up.

You will have to go 'client facing' and be the interface between those horrible nasty coders and the business, but at least you'll have the clout to kick in to touch some of the dumber ideas we get saddled with by people in charge who couldn't program a VCR.

by whiteknight_

Kipplummer,

I'm going to give you a contrarian answer to these others.

IF you are very good in development and that is what you really enjoy then don't let yourself be pushed out of it long-term. Sometimes we need to recognize where our strengths are and what makes us happy.

In my career I've gone all the way down the road from hot programmer to analyst to development team manager to project manager. At the end I realized that I was proving the Peter Principle (had risen to my level of incompetence) and moved back to what I really enjoyed - developing solutions to problems that made life easier for people and business organizations.

This doesn't mean you should only be a propeller-head that only understands programming - thats the way to the unemployment line. Rather try to achieve balance - just like in real life ;). You will be much more valuable as a developer when you understand the business concepts/issues etc. So even if you only spend 10 - 20% of your time coding while the rest is spent on interviews, client meetings, and application design you'll still be producing better applications.

As far as your current situation ... I think you are right to be concerned if they have no role that lets you be the analyst while still keeping your technical skills current. Don't jump ship yet, this is an opportunity to expand your skills, but towards the end of the current project plan on re-evaluating whether or not there is a place for you at this company and determine if its time to jump ship while your technical skills are still current.

My 2 cents,

by jwhite1202

Even if your long term plan is development, management and analytical skills will help you become a better Sr. Developer, Development Manager, or even IT Architect. Knowing how to interact with people and having technical knowledge is pure gold. Use this as a resume builder if nothing else, that way when you do get that next tech job you can have a little more leverage and job security because your employer will know that you are more than a code monkey.

by ramagovindaraja

Hi,
So atlast what happened these days? U took the analyst role?
If so how do feel now? Me too in same situation to define my role. If u ve taken d role u got comfortable with use cases?

Finally, suggest if analyst is better to take from as a developer...

Thanks

This discussion is closed to new replies.