Too Old For The Job
Sep. 28th, 2006 09:23 amThat sounds worrying, doesn't it? Luckily it's the job title that may be too old, not me.
Because of the impending change to the law that will outlaw ageism, it's been suggested that my job title of Senior Software Developer might no longer be appropriate, as Senior could be taken to suggest that you have to be an old dude to hold such a post. At 39, I guess I'm an old dude in some people's eyes and a whippersnapper in others, so personally I don't feel too pigeon-holed.
Senior can of course be interpreted in ways that have nothing to do with age, but it's the ambiguity that could be a problem.
Apparently we're not dead set on changing people's existing job titles, but we definitely wouldn't want to advertise such roles with the same name, so I've been asked whether I can think of any preferable alternative descriptions of what I do, and it's quite difficult to come up with something satisfactory. It would also be nice, though probably not essential, if the suggested alternative could be used in other disciplines, as we have other "senior" staff who aren't in software development.
To give you a rough idea of what I do, I am responsible for designing our project architectures and for advising and encouraging best practices, but I don't have a lot of say in directing what we do when, and I don't have anyone reporting to me.
Although I'm in favour of development becoming more regarded as being an engineering discipline, I'm also in favour of Engineer meaning something in terms of formal qualifications and/or professional memberships, so sadly Engineer might not be a good word to include.
Because of the impending change to the law that will outlaw ageism, it's been suggested that my job title of Senior Software Developer might no longer be appropriate, as Senior could be taken to suggest that you have to be an old dude to hold such a post. At 39, I guess I'm an old dude in some people's eyes and a whippersnapper in others, so personally I don't feel too pigeon-holed.
Senior can of course be interpreted in ways that have nothing to do with age, but it's the ambiguity that could be a problem.
Apparently we're not dead set on changing people's existing job titles, but we definitely wouldn't want to advertise such roles with the same name, so I've been asked whether I can think of any preferable alternative descriptions of what I do, and it's quite difficult to come up with something satisfactory. It would also be nice, though probably not essential, if the suggested alternative could be used in other disciplines, as we have other "senior" staff who aren't in software development.
To give you a rough idea of what I do, I am responsible for designing our project architectures and for advising and encouraging best practices, but I don't have a lot of say in directing what we do when, and I don't have anyone reporting to me.
Although I'm in favour of development becoming more regarded as being an engineering discipline, I'm also in favour of Engineer meaning something in terms of formal qualifications and/or professional memberships, so sadly Engineer might not be a good word to include.
no subject
Date: 2006-09-28 09:37 am (UTC)How about Principal Software Developer? I know it sounds a bit civil service, but it might work. Or possibly Executive Software Developer
no subject
Date: 2006-09-28 10:04 am (UTC)no subject
Date: 2006-09-28 10:01 am (UTC)no subject
Date: 2006-09-28 10:11 am (UTC)no subject
Date: 2006-09-28 02:04 pm (UTC)I agree with your thoughts on using engineer in a job title, especially as one can work towards being a real engineer with the BCS. Likewise, architect is an inappropriate title.
What about:
Class 1 Developer
Superior Developer
Programmer of High Rank
Or like American generals, you could be a one-, two- or three-star developer?
no subject
Date: 2006-09-28 02:37 pm (UTC)I rather like your other two suggestions, but as with
I should investigate BCS recognition as an engineer, but there's a certain amount of personal inertia to overcome first.
no subject
Date: 2006-09-28 04:14 pm (UTC)I too need to get rid of some of that personal inertia - I really ought to join the BCS. I really, really, really ought to join the BCS. I really, really... :)
no subject
Date: 2006-09-28 04:18 pm (UTC)Programmer
Programmer Sapiens
Programmer Sapiens Sapiens
You could naturally extend this downwards for new graduates to Programmer Neanderthalensis...
no subject
Date: 2006-09-28 05:20 pm (UTC)Software Developer
Software Development Specialist
Software Development Manager
...with Senior Software Developer being replaced by Software Development Specialist.
no subject
Date: 2006-10-03 08:30 am (UTC)Developer
Developer++
Developer#
no subject
Date: 2006-10-03 08:08 am (UTC)no subject
Date: 2006-10-03 08:28 am (UTC)no subject
Date: 2006-09-28 06:13 pm (UTC)What about "Senior Lecturers"? Are they to be renamed?
And... 39? You're still a boy!
no subject
Date: 2006-10-02 07:29 pm (UTC)At my work the HR department has been pondering this issue for some time. All the senior economists and so on are now 'lead' economists or whatever.
Which isn't really right as there are other levels above that. Speaking as a Principal Economist I'm not sure I'd appreciate people who were only 'senior' now being 'principal' as Toby suggested...
It's thrown a large metaphorical rock into that pool of job titles that some organisations have to use to create many impressive sounding but subtly different grades. I'm sure that the HR departments and philologists of the world will crack the problem in time. Maybe 'junior vice president' is still available?
no subject
Date: 2006-10-02 09:00 pm (UTC)I guess it's over to the HR departments and philologists then...