Generally accepted Developer Job Descriptions and hiarchy.

[jc]

Good Evening fellow .NET Developers,

Sorry about off post..

Does anybody know where I might find a good (free) list of IT
Developer job descriptions.

HR is saying that job title Sr. Programmer and Sr. Systems Analyst
should be on the same pay scale and level and they are not
neccessarily on the same career path.

As far as I've always knows, a Sr. Programmer is on his way to
becoming a Programmer/Analyst and eventually a Systems Analyst.

A poll..

Is it generally accepted as an IT standard that most Sr. Systems
Analyst are coding in addition to Analysis and Design?

But that in many shops, many Sr. Programmers might not be doing much
Design and Analysis (especially at the Applciation level)? Leading
projects? Meeting with users and collecting requirements? Designing a
full solution with a higher complexity of components than a Sr.
Programmer?

If you are handed a raw problem that requires that you call meetings
with users. Collect requirements. Design and build databases. Design
and code Middleware. Design and code reports. Design and code Web
front End forms. Configure Servers and IIS....then run through the
full SDLC is Sr. Programmer a fair title?

Thanks for any help or information!

[rowe_newsgroups]

On Jul 11, 6:28*pm, jc <[e-mail]:

Good Evening fellow .NET Developers,

Sorry about off post..

Does anybody know where I might find a good (free) list of IT
Developer job descriptions.

HR is saying that job title Sr. Programmer and Sr. Systems Analyst
should be on the same pay scale *and level and they *are not
neccessarily on the same career path.

As far as I've always knows, a Sr. Programmer is on his way to
becoming a Programmer/Analyst and eventually a Systems Analyst.

A poll..

Is it generally accepted as an IT standard that most Sr. Systems
Analyst are coding in addition to Analysis and Design?

But that in many shops, many Sr. Programmers might not be doing much
Design and Analysis (especially at the Applciation level)? Leading
projects? Meeting with users and collecting requirements? Designing a
full solution with a higher complexity of components than a Sr.
Programmer?

If you are handed a raw problem that requires that you *call meetings
with users. Collect requirements. Design and build databases. *Design
and code Middleware. Design and code reports. Design and code *Web
front End forms. Configure Servers and IIS....then run through the
full SDLC *is Sr. Programmer a fair title?

Thanks for any help or information!

Of course if you subscribe to the Agile principles job titles
shouldn't matter....

Thanks,

Seth Rowe [MVP]
http://sethrowe.blogspot.com/

[Steve Gerrard]

jc wrote:

>
As far as I've always knows, a Sr. Programmer is on his way to
becoming a Programmer/Analyst and eventually a Systems Analyst.

If you are handed a raw problem that requires that you call meetings
with users. Collect requirements. Design and build databases. Design
and code Middleware. Design and code reports. Design and code Web
front End forms. Configure Servers and IIS....then run through the
full SDLC is Sr. Programmer a fair title?

Being in that boat, with many others I suspect, I would rather be called a Sr.
Programmer than a Systems Analyst. The latter sounds like I'd be doing new SAP
rollouts, or some such massive and tedious configuration task. Those titles
really date back to the time of mainframe computing, lost now in the dark misty
past of the 1970's.

My personal preference is Lead Application Developer, which I saw in some
article somewhere. Just vague enough to cover all the hats we seem to wear these
days. Or you could go for Bill G.'s old title - Chief Software Architect. :)