April 17, 2007 at 7:18 am
I am not sure if this is the right forum for this or not so for those who can please feel free to move it to where it should be if this is not a good place for it.
I have worked at the same place for almost 7 years now and my job title has stayed the same during this time period. Will that be viewed as a detriment on a resume? The description of what I have done while in this position will show that I have done more than just what my job title describes.
My job title is SQL Programmer. However I often perform tasks that seem to me to be more of the ones a DBA would do.
Also I am considering asking for a title change and the best one I can think of is ETL Specialist. This is because I always do a lot of DTS and SSIS work and have specialized in this. Or would that title be too limiting for future jobs?
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
April 17, 2007 at 8:04 am
Are you planning on changing job soon??
Anyhow I think that the skillset you posses is far more important than the job title (to a degree). Also if you feel you are an ETL specialist then by all means, put it on your resume. When the interviewer asks you about the job and the skills he will clearly see that you were erally doing that job and that the old title (to which you never refference) was "unjustified".
April 17, 2007 at 9:01 am
I agree with Ninja's RGR'us about the skillset being far more important than the title, especially since many shops will gladly let you pick your own title.
"Want to name yourself the 'Big Kahuna of All Things SQL', go for it!"
I'm not sure that I've ever personally paid much attention to whether someone was "SQL Programmer", "Sub-Senior SQL Trainer of Junior SQL Developers", or anything else. With that said, while I'd definitely highlight the ETL experience in a resume, I don't know if I'd put that down as my title, unless you really want to stay in that niche, because not everyone ignores them as I do. I also should note that most of the resumes I've seen only have a single title per job, which I always assume is the last title they held, so not having it change in 7 years isn't that big of a deal.
April 17, 2007 at 2:21 pm
Thank you both. I haven't worried much about my title because I didn't think it would matter but since I never spoke with anyone else I just didn't know how important it really was.
Robert W. Marda
Billing and OSS Specialist - SQL Programmer
MCL Systems
April 21, 2007 at 2:29 pm
In my SQL Server experience (same length as yours, wide variety of environments, but little/no non-prod work), the factors that govern marketability are, in descending order of significance:
Skillset/frequency of use;
Size/variety of systems administered;
Yes, a short list indeed, but as long as you have those two neatly wrapped up, you really don't have to worry. I could add a host of other things like monitoring tools used, variety of work undertaken, but they're pretty peripheral; if you can't show the tech, you won't BE the tech.
Depending on how bullish your job market is over there, you won't need to worry at all about crap like personability, just smile at the Personnel lady and indulge her dumb questions like, "See that database server over there? Sell it to me".
(Yes, I actually had that asked - needless to say I took another offer!)
To which you reply,
"It's got lots of flashing lights and it makes your database go realllllllllllly fast!!
On a more serious note, be ready for some culture shock after 7 years in the same place. Personally I go nuts after just 6 months in the same environment, no matter how well-paid or fun the assignment is. I have a hard time understanding how someone can stay in a job for more than 2 years and retain his sanity, but that's just my mercenary nature - clearly some people can.
Jaybee.
April 22, 2007 at 9:09 pm
Robert,
I don't think it's a big deal if your title is the same if you're staying in the same or a similar field. If you want to move to management or something else, then it would be nice to see you in a few roles, but I think the tide is turning with more employers appreciating longevity in employees.
April 23, 2007 at 3:17 am
Just bear in mind that recruitment consultants aren't actually equipped to read between the lines, so if you apply for a DBA role and your title isn't DBA then you might have trouble getting your CV put forward for the job.
I've had to tailor my CV mercilessly to get past this problem - essentially you need to work out what you could be and then bullet point it on your CV, so :
Job Title : SQL Programmer
Responsibilities :
Extensive Database Admin Work
ETL
Blah blah blah. Just think pigeonholes and buzzword compliance and you should be OK...
I cannot stress enough just how pointless a lot of recruitment consultants are.
Some are good, but mostly they're pointless.
April 23, 2007 at 6:02 am
Amen to that. The only good Recruitment Consultants have body temperatures hovering slightly above zero.
That said, my last agent was an exception, an absolute diamond top notch fella, went out for lunch, drinks etc every few weeks on his tab. I'd rather work with him next time for a few pennies less, though it was the best paid contract I'd ever done.
Jaybee.
April 23, 2007 at 7:16 am
I usually give a job title of "SQL Developer / DBA" regardless as what my official title was. I once described myself only as a "SQL Developer" and was turned down for a role because they were after "more of a DBA". Infuriating!
.
April 26, 2007 at 8:59 am
I have seen people coming up with all kinds of different job titles. Look at your job description and what you do day in day out. then create/post your resume and search for a job. since you have 7 years of experiance you can hunt for a job that you like and fits your skills/career development.
Good day,
Bulent
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply