it's probably different from company to company but it might be something like: jr. developer ---> developer ---> sr. developer ---> systems analyst ---> sr. systems analyst ---> arthitect(tech lead) ---> sr. arthitect ---> project manager ---> sr. project manager---> manager --->CIO ---> CEO
Originally posted by Srikanth Raghavan: I would like to know the hierarchical designations that is commonly implemented in the IT industry(both technical and functional) from a programmer or a tester to CEO.
For eg:- Programmer --> Team Lead --> Project Manager --> ???
Thank you, Srikanth
It depends on organisation structure...mostly this is how they do it: You will have three main streams: 1. Delivery: Responsible for project delivery 2. Sales: Sales and Marketing 3. Technology: Grow as a technical architect/funtional consultant
Any of the three will lead you up till the middle managers role...From there starts the leadership team (note: there is a difference between leadership team and management team) like Unit head, country head, VP, COO, CEO...
We start like this Trainee --> Programmer --> Team Lead...From her we need to decide.. The path can go like this based on the above three
Team Lead-->project manager-->account manager/Group lead-->Leadership team Team Lead-->Pre-sales team(a part of Project management team)-->sales team-->Leadership team Team Lead-->Busniess analyst/Sr.BA-->funtional expert/Technical architect-->Leadership team
Note: there is no hard and fast rule in any of the above. To be a part of leadership team, you need to expereince all the three streams
if you start out as a programmer for company A, if your good, if you play the politics well, and if a company likes you enough and you stay around long enough, it can lead up to roles as team leads, managers, and so on.
But CIO and CEO are many times business people who played the politics to a tee. There are not many computer programmers who wind up as CEOs or even CIOs. At that point, it's more about politics, management, business than computing.