Job Title Suggestions
-
Maybe they end up with something like "The Super Guru programmer God who does magic things we don't understand" :laugh: :laugh:
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
You're letting her get away with this? May I suggest: Pansy. :-D PRO-TIP: When you get a different job make sure you let her know the whole job title issue is the reason why you left the company. Tell them you're big on flexibility in that area and that your new job doesn't pay more but you get to chose your own title.
-
You're letting her get away with this? May I suggest: Pansy. :-D PRO-TIP: When you get a different job make sure you let her know the whole job title issue is the reason why you left the company. Tell them you're big on flexibility in that area and that your new job doesn't pay more but you get to chose your own title.
MehGerbil wrote:
that your new job doesn't pay more but you get to chose your own title.
:thumbsup::thumbsup:
-
I was a "Research Scientist II", which became a "Research Scientist" the last time they changed the job ladder (which annoyed me no end, because it looks like a demotion), then I got promoted (hooray) to "Senior Research Scientist", then they messed with the ladder again and my title got changed to the utterly stupid "Research Investigator". I told my boss that I hated that title (especially since I lost both "senior" and "scientist") unless it came with a badge and a gun. On the bright side, it gives me some cover to complain about my title without tipping them off that I'm thinking about leaving.
Oh Gosh ! how can some one be designated as Investigator , Heads up for bringing in and sure you deserve a change. I'm sure if you put down the papers they will designate you want ever you wish for, You know crazy managers , management do this very often. Until you raise your voice or heads up these things won't change. Good Luck to you, The best thing is to roll back your designation to Research Scientist II , I love it :) Thanks,
Ranjan.D
-
Maybe they end up with something like "The Super Guru programmer God who does magic things we don't understand" :laugh: :laugh:
Marco Alessandro Bertschi wrote:
The Super Guru programmer God who does magic things we don't understand
What a coincidence, that is my job title! ;)
"State acheived after eating too many chocolate-covered coconut bars - bountiful" Chris C-B
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
I had the official job title of "Senior Geoscience Advisor" once and I never figured out what that meant. I have no idea what your official title is, but I would leave it at that and explain what it is you actually do in the job description part.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
Marco Alessandro Bertschi wrote:
The Super Guru programmer God who does magic things we don't understand
What a coincidence, that is my job title! ;)
"State acheived after eating too many chocolate-covered coconut bars - bountiful" Chris C-B
-
I had the official job title of "Senior Geoscience Advisor" once and I never figured out what that meant. I have no idea what your official title is, but I would leave it at that and explain what it is you actually do in the job description part.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
In an ideal world, that would work, but in reality, I think people are hitting the title first and jumping to conclusions. Even if they read the description, I think they have trouble getting over that first impression.
Well, in an ideal world I wouldn't want to work for a company that doesn't take the time to read what a prospective employee really can do. Of course, I haven't looked for a job since 1973, the jobs come looking for me no matter what my official title may be.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
Aren't you supposed to put more than just what your job title is on your resume? ;) I think Senior Developer does kind of imply that you are in a senior position in your company. Unless they're trying to imply that you are a senior in the geriatric sense. They did the same thing where I work where all the developers, designers and hardware guys were are all titled as Development Engineer starting at associate up to senior principal engineer . But they do allow us to add to our titles (Within reason) to describe what we actually do on the business cards.
It was broke, so I fixed it.
-
Aren't you supposed to put more than just what your job title is on your resume? ;) I think Senior Developer does kind of imply that you are in a senior position in your company. Unless they're trying to imply that you are a senior in the geriatric sense. They did the same thing where I work where all the developers, designers and hardware guys were are all titled as Development Engineer starting at associate up to senior principal engineer . But they do allow us to add to our titles (Within reason) to describe what we actually do on the business cards.
It was broke, so I fixed it.
S Houghtelin wrote:
Aren't you supposed to put more than just what your job title is on your resume? ;)
Indeed, and aren't people supposed to read more than the title before jumping to conclusions? If that was the case, I wouldn't be having this problem.
-
S Houghtelin wrote:
Aren't you supposed to put more than just what your job title is on your resume? ;)
Indeed, and aren't people supposed to read more than the title before jumping to conclusions? If that was the case, I wouldn't be having this problem.
Wjousts wrote:
aren't people supposed to [Insert Proper Behavior Here] before jumping to conclusions?
If only it were so. But I do get your point. Maybe you can add that as your reason for looking for other work... "Seeking better job title" :laugh:
It was broke, so I fixed it.
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
I had an official title of Systems Alchemist several years back - I thought Architect was a bit mainstream and the connotation of producing gold from base metals (aka useful stuff from not much) was apt. Surprisingly they went along with it & put it on my business card :)
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
Maybe I am missing the point here, but if you are applying for another job, just call yourself what you like on your resume - senior developer, software engineer whatever. If you get interviewed etc. and they get references from your current employer, they ain't going to give a toss about the job title, if they even notice. I actually don't put job titles in my resume in the main, as it can lead to confusion - one company's software engineer is another company's junior developer is another company's dogs body - so I just tend to explain the role.
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Maybe I am missing the point here, but if you are applying for another job, just call yourself what you like on your resume - senior developer, software engineer whatever. If you get interviewed etc. and they get references from your current employer, they ain't going to give a toss about the job title, if they even notice. I actually don't put job titles in my resume in the main, as it can lead to confusion - one company's software engineer is another company's junior developer is another company's dogs body - so I just tend to explain the role.
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
_Maxxx_ wrote:
Maybe I am missing the point here, but if you are applying for another job, just call yourself what you like on your resume - senior developer, software engineer whatever.
If you get interviewed etc. and they get references from your current employer, they ain't going to give a toss about the job title, if they even notice.Well, they won't get references from my current employer as that would rather give the game away. But what they might do is make an offer, which I accept, and then check job titles and starting / ending salary with my current (soon to be previous) employer and get mighty annoyed if I said I was "chief guru of all things awesome" and they say "no, he was junior keyboard cleaner". That's the kind of BS that might see an offer immediately withdrawn. Certainly if I was hiring, I'd have some questions about that.
-
_Maxxx_ wrote:
Maybe I am missing the point here, but if you are applying for another job, just call yourself what you like on your resume - senior developer, software engineer whatever.
If you get interviewed etc. and they get references from your current employer, they ain't going to give a toss about the job title, if they even notice.Well, they won't get references from my current employer as that would rather give the game away. But what they might do is make an offer, which I accept, and then check job titles and starting / ending salary with my current (soon to be previous) employer and get mighty annoyed if I said I was "chief guru of all things awesome" and they say "no, he was junior keyboard cleaner". That's the kind of BS that might see an offer immediately withdrawn. Certainly if I was hiring, I'd have some questions about that.
Wjousts wrote:
I was "chief guru of all things awesome" and they say "no, he was junior keyboard cleaner".
Sure, but the op said they had a job title that didn't reflect their position - and was corporate waffle. So, having got to interview it is easy to point out that one's official title is "Corporate DataWrangler, Level 5a" whereas the description you gave reflected more accurately your actual role.
Wjousts wrote:
Well, they won't get references from my current employer as that would rather give the game away.
I'd assume they would once an offer was in the pipeline - that's my point, they won't know your actual job title unless your current employer tells them - at which point they have satisfied themselves you are capable of doing the job (assuming you haven't lied about your abilities, of course)
Wjousts wrote:
hat's the kind of BS
It's not BS though if you do as I suggested. In all honesty, if your job title is bottle washer, but you are writing good code every day, I (as a potential employer) wouldn't give a hoot - but I would probably expect you to have pointed out the official title at interview - and explained why a bottle washer thinks they can do this job.
Wjousts wrote:
Certainly if I was hiring, I'd have some questions about that.
Yeah - you're taking it out of the context of the original question though
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Wjousts wrote:
I was "chief guru of all things awesome" and they say "no, he was junior keyboard cleaner".
Sure, but the op said they had a job title that didn't reflect their position - and was corporate waffle. So, having got to interview it is easy to point out that one's official title is "Corporate DataWrangler, Level 5a" whereas the description you gave reflected more accurately your actual role.
Wjousts wrote:
Well, they won't get references from my current employer as that would rather give the game away.
I'd assume they would once an offer was in the pipeline - that's my point, they won't know your actual job title unless your current employer tells them - at which point they have satisfied themselves you are capable of doing the job (assuming you haven't lied about your abilities, of course)
Wjousts wrote:
hat's the kind of BS
It's not BS though if you do as I suggested. In all honesty, if your job title is bottle washer, but you are writing good code every day, I (as a potential employer) wouldn't give a hoot - but I would probably expect you to have pointed out the official title at interview - and explained why a bottle washer thinks they can do this job.
Wjousts wrote:
Certainly if I was hiring, I'd have some questions about that.
Yeah - you're taking it out of the context of the original question though
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
_Maxxx_ wrote:
Yeah - you're taking it out of the context of the original question though
Since it's my question, I don't think so ;P I'm not just asking a hypothetical here. I've had two job offers already. The first one was fine, they offered me the same as what I'm currently earning, but the health insurance was terrible. To cover my whole family would have cost me somewhere in the region of an extra $8k / yr. So I turned it down. The second one had much better insurance and I was doing just fine, until I got to the CEO who claimed he'd only just be handed my resume, but he was a "quick study". He starts asking me about how I'd handle the learning curve and how he needs people who can "hit the ground running". With hindsight, I'm a little mad at myself for not handling it better because it's BS. I know the technologies they are using, and I should have been a little more forceful on that point. I aced the interview with their technical people and they seemed really excited. I really feel I got at least partially tripped up on my current job title because he didn't read the description. He'd convinced himself that he knew what I was all about (as most CEO types do, once they get an idea in their head, it's hard to dislodge) and nothing I said made a difference. Their HR guy did call be and told me that they were looking at around a salary that would have actually be slightly less than I was earning when I started my current job...8 years ago. It would have been a cut in the region of $25K/yr. Suddenly the crappy insurance at the other one looked great! The second one isn't completely dead. The HR guy said he'd "touch base" with me again in a couple of months time (after my bonus at my current job, which I'd also be giving up) to see if anything has changed. But to be completely honest, I've soured a little on the whole thing. If they'll low ball me that badly right from the start, I wonder how fair they'll be going forward.
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
What you put on your resume doesn't need to be what HR says your title is. I always put "Software Engineer". My official current title is "Web Developer", but I do nothing Webby at all, I do database and backend stuff. Soon I may be something like "Infrastructure Architect VI" (with no change in job duties), but I won't put that on a resume either.
-
I'm seriously thinking about looking for another job, but my current job title is making it annoyingly difficult to explain that yes, I am actually a programmer / developer and yes I've been doing it for the last 8 years. So I asked my current boss (tactfully) if I could change my job title to something that actually reflects what I do. She told me that I can't change my current title (it's part of the corporate job "ladder"), but I can hyphenate is and add whatever I want afterwards. For example: Title that doesn't suggest anything programming related - senior developer. So my question is, what would be a good title to stick on the end that might actually help communicate that I am actually a developer? As it is now, I'm largely a solo developer (hence the lack of suitable job titles) so I do everything and I feel my title should communicate so degree of seniority (hence not just "programmer" or "developer" or "code monkey"). Any suggestions (serious or otherwise)?
Sycophant Emeritus, Programming
Will Rogers never met me.