Java programmer positions

[Khan]

Hi,
can any 1 tell me what are the job designations an IT guy can have

step by step. like first junior programmer than asst. programmer later
on IT manager, how they are sorted from start till end.
currently i'm working as java programmer and my job designation is
'programmer', what could be the next step after programmer , i mean
system analyst or senior programmer or what ...

 

[Oliver Wong]

Hi,
can any 1 tell me what are the job designations an IT guy can have

step by step. like first junior programmer than asst. programmer later
on IT manager, how they are sorted from start till end.
currently i'm working as java programmer and my job designation is
'programmer', what could be the next step after programmer , i mean
system analyst or senior programmer or what ...

There isn't a universally agreed upon standard.

At the company I work at, for example, I don't have an official title; I
just do whatever needs to get done. Sometimes that's programming, sometimes
designing, sometimes documenting existing systems, sometimes it's research
and development, sometimes it's interviewing and conducting tests for other
applicants to the company, and so on.

- Oliver

 

[jlowery05]

A typical career path goes like this:

white box tester
junior programmer
programmer
senior programmer
technical lead
program manager
technical lead
senior programmer
technical writer
fry cook

 

[Roedy Green]

technical writer
fry cook

how about the "architects"?

 

[jlowery05]

oh, yeah: throw that in there somewhere too... on the way up or down,
I'm not sure which.

 

[opalpa]

my job designation is 'programmer', what could be the

next step after programmer

There is no next step. Programmer is the ultimate title.

Opalinski
(e-mail address removed)
http://www.geocities.com/opalpaweb/

 

[Wibble]

There is no next step. Programmer is the ultimate title.

Opalinski
(e-mail address removed)
http://www.geocities.com/opalpaweb/

Actually, ignore the title.
The only score is what they pay you.

 

[Hal Rosser]

Hi,
can any 1 tell me what are the job designations an IT guy can have

step by step. like first junior programmer than asst. programmer later
on IT manager, how they are sorted from start till end.
currently i'm working as java programmer and my job designation is
'programmer', what could be the next step after programmer , i mean
system analyst or senior programmer or what ...

The way it usually works is - your first programming job is low-pay - but
you get experience.
After about 2 to 4 years, you're worth double the money you started at - but
the company that hired you will not pay you that much - so you may need to
go to another job - at double the salary.
Don't look for job titles - look for good work conditions + benefits + pay.
Its a lot better to look forward to a day at work, than dreading it.

 

[Luc The Perverse]

The way it usually works is - your first programming job is low-pay - but
you get experience.
After about 2 to 4 years, you're worth double the money you started at -
but
the company that hired you will not pay you that much - so you may need to
go to another job - at double the salary.
Don't look for job titles - look for good work conditions + benefits +
pay.
Its a lot better to look forward to a day at work, than dreading it.

I could make 30 to 40% more but work a job that I detest.

Instead - I do what I do and it keeps me happier.

 

[Luke Webber]

how about the "architects"?

Oooh I /hates/ them self-appointed "architects"! <g>

Luke

 

[Adam Maass]

Hi,
can any 1 tell me what are the job designations an IT guy can have

step by step. like first junior programmer than asst. programmer later
on IT manager, how they are sorted from start till end.
currently i'm working as java programmer and my job designation is
'programmer', what could be the next step after programmer , i mean
system analyst or senior programmer or what ...

There is no universally defined progression.

At one job I had, the technical ladder looked something like this:

Associate Software Engineer
Software Engineer
Senior Software Engineer
Staff Software Engineer
Director of Engineering
Vice President of Engineering


The allowed pay range at each level was quite broad, and there was a great
deal of overlap in the ranges. That is, the highest allowable salary at the
"Software Engineer" level was just about equal to the lowest allowable
salary at Staff Software Engineer -- two notches up. And this was true of
the entire ladder. Additionally, each level had a job description, but they
were mostly similar. What differed was the "expected amount of experience"
and "scope of work" and "amount of expected supervision" at each level.
(More experience, broader scope, and less supervision at each level.) At
this company, the promotion policy was "the candidate must already be
performing the duties of someone with a title at the next level up.
Promotions are awarded in recognition of this fact at the regularly
scheduled performance review cycle."


-- Adam Maass

 

[Chris Smith]

At one job I had, the technical ladder looked something like this:

Associate Software Engineer
Software Engineer
Senior Software Engineer
Staff Software Engineer
Director of Engineering
Vice President of Engineering

Fortunately, more and more companies are recognizing that the last two
titles should really be on a completely different list. Hopefully,
within the next two decades, we can see a virtually complete end to the
bizarre practice of promoting from software development into management.

--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation

 

[Khan]

thanx for all your replies.

 

[Thomas Weidenfeller]

Fortunately, more and more companies are recognizing that the last two
titles should really be on a completely different list. Hopefully,
within the next two decades, we can see a virtually complete end to the
bizarre practice of promoting from software development into management.

But where else should all the bad programmers go?

/Thomas

 

[Chris Smith]

But where else should all the bad programmers go?

Marketing. The problem is that programmers make everything hard. In
marketing, you only have to think of a feature, and the product already
has it (or at least, so you tell the customer).

--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation