Win a copy of Five Lines of Code this week in the OO, Patterns, UML and Refactoring forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

How do u define I.T. positions?

 
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I just would like to know how the ranchers define I.T. positions hierarchy in order?
Programmer > Developer > Software Engineer > Senior Programmer > Senior Developer > System Analyst > Consultant > Senior Consultant > Project Manager

and stuff like that... Who is higher and who is lower in position and their duties?

Thanks...
 
Ranch Hand
Posts: 502
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Sometimes I feel these job titles are completely arbitary. I my previous company it was
Junior Developer(Pure coding) > Senior Developer(Coding and low level design) > Technical lead(Coding, low level design, recommending new technologies, training and guiding junior developers)

Then the thread split into 2
Architect(High level design) > Senior Architect(Product design)

and

Project Manager(Manages one team, detailed requirements) > Software Development Manager(Manages multiple teams, coordinates resources) > Product Manager(Manages a whole line of products, high level requirments)


In my current company it's

Junior Software Engineer(Simple Coding/Maintainence) > Software Engineer(Coding) > Senior Software Engineer(Coding and low level design) > Principal Software Engineer(Coding, low level design, recommending new technologies, training and guiding junior developers)

Then it splits into
Architect(High level design > Principal Architect(Product design)

and

Product Manager(manages multiple teams dedicated to a product, low level requirments)> Software Development Manager(Manages multiple product development teams, coordinates resources) > Client Manager(Interacts with client, high level requirements)



Note that what was called Project Manager in my old company is called Product Manager in my current company, and what is called Product Manager in old is called Client Manager in new

You can look at salary.com to get an idea of what differrent job titles mean
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Jayesh for your great comments... I am also having a loot at salary.com for further positions...
 
Ranch Hand
Posts: 820
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My title changes from day to day. I'm officially a programmer, but I used to be "junior" programmer, and some people have forgotten about the change so still call me that. When my manager talks to a customer he'll refer to me as a developer (as in "sure, I'll get one of my developers to look into your silly pointless problem") and on another project I'm technical lead. At the end of the day a job title makes little or no difference as the work will vary considerably.

Perhaps IT jobs should take a more regulated approach - we could be ordered similarly to martial arts, by belt colour. Then people could go around saying things like "Me black belt in programming. You feeble blue belt. Bow down before me before I mock your ineptitude."
 
Ranch Hand
Posts: 1907
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
During dotcom days,I saw the people who were 'Content Developer'/'Content Manager'
 
Author
Posts: 6049
2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As Jayesh pointed out, it is pretty arbitrary. Different companies have different structures. Many smaller companies don't formally use titles and just call everyone an "engineer." Some use direct reports and others matrix systems. Responsibility means much more than title--although sometime's title is all you have to go on when first meeting someone.

--Mark
 
Ko Ko Naing
Ranch Hand
Posts: 3178
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Originally posted by Mark Herschberg:
As Jayesh pointed out, it is pretty arbitrary. Different companies have different structures. Many smaller companies don't formally use titles and just call everyone an "engineer." Some use direct reports and others matrix systems. Responsibility means much more than title--although sometime's title is all you have to go on when first meeting someone.



Mark, thanks a lot for your explanation...

You are right that different companies have differnet structures. But if we try to move to a new company, how can they figure my previous position and duties out? Do we need to mention about the previous position and duties in detail in our CV?
    Bookmark Topic Watch Topic
  • New Topic