35

Possible Duplicate:
What does the suffix after software engineer/developer job titles mean? (i.e. Software Developer III)
work advancement titles

I've been struggling to understand job hierarchy in software engineering.

The system is further complicated because of the lack of consistent naming conventions when assigning roles: for example, some companies just have a "senior software developer" position while others have Software Engineer I, Software Engineer II, Software Engineer III, and so on.

Even in the top level positions, we have things like "Principal Software Engineer" vs. "Staff Software Engineer".

What is the standard hierarchy for software engineers? Is there a generally accepted pecking order?

5 Answers5

40

Wikipedia gives a good overview of corporate titles and under the hierarchy for Information Technology companies you have the following:

  • Chief Executive Officer
    • Vice President
      • Senior Project Manager / Senior Product Manager / Senior Software Architect
        • Project Manager / Product Manager / Software Architect
          • Project Lead / Senior Team Lead / Senior Technical Lead
            • Module Lead / Team Lead / Technical Lead
              • Senior Software Engineer / Senior QA Engineer
                • Software Engineer / QA Engineer

While each company will have it's own naming convention and resposibilities for a role, they do seem to fall within this basic hierarchy.

Hope this helps you out some.

ChrisF
  • 38,948
  • 11
  • 127
  • 168
Chris
  • 2,013
29

There is no standard hierarchy of software job titles. Titles are peculiar to each company. If you have a question about a job title there's no point in asking anybody except that company.

9

At Microsoft, the titles are:

  • Software Development Engineer (two internal levels, 59 and 60)
  • SDE II (61 and 62)
  • Senior SDE (63 and 64)
  • Principal SDE (65 and 66)

At Google, there are senior titles like Staff Software Engineer and Sr. Staff Software Engineer.

At Apple, there are titles like Software Engineer I to Software Engineer V.

See also: What is the difference between these senior software engineer titles?

3

Job titles only have meaning within a specific organization sometimes only within a small section of that organization. In general they are only useful in assessing the "Dilbert Co-efficient" of your current employer.

Also be careful with the title "Engineer" in some countries its illegal to use the title unless you are an accredited member of the local Civil/Electrical/Electronic professional body. "Software Engineer" doesn't count for much with "real" engineers.

0

There is no global standard for designations or i assume no one has made one till now. Its good to have guidelines for design, naming convention but the code has nothing much to do with the designation of the person writing it.

The one you have mentioned would be company specific and you can think of them as levels in a game where in you play at one level, gain experience and points/life and then qualify for the next level. This part pretty much is same all over, so the more you play the better you get and higher the chances of going up the levels but then as its is for all games the rules are different and so in this case its the company.