In these econmomic times call yourselves fortunateI and fortunate II and don't worry about meaningless things.

Just make sure you get paid more then he.
:) ;)


>We are in the process of redoing our job titles, and I need a little help. There are only two of us developers in this small company. With recent changes, I am now the senior developer/analyst having been here 1.5 years while the other guy (who reports to me) has been here about 5 months (for most of which, he was a temp). He's full-time now. We both do design/development while I handle most of the day-to-day support as well as some managerial/supervisory duties (although I'm not a manager, technically). I head the development aspect, but I report to the Network Admin. It's strange, I know.
>
>Originally, I was thinking of being the Systems Analyst and him being the Software Engineer. The problem with that is that the Systems Analyst typically isn't involved in much development (at least from what I've read). Also, the Systems Analyst/Software Engineer relationship seems disjoint. What I mean is that the two don't seem to fit in the hierarchy that we have (where he reports to me). Then we were thinking Systems Analyst II and Systems Analyst. That solves the problem of the hierarchy, but the other remains. Also, it seems odd for a company so small (less than 20 employees) to have two Systems Analysts.
>
>I know job titles are almost technicalities, but I just wanted to get as much info on this as possible before deciding. Does Programmer/Analyst and/or System Architect fit in with these others? Previously, I was the "Applications Programmer Analyst" and he was an "Assistant Programmer", but we have long outgrown those titles, especially considering our recent promotions.
>
>Thanks
>
>-Nirav