Slashdot Mirror
Are IT Job Titles Getting Out of Control?
grudgelord asks: "Information technology jobs have always been difficult for those from non-technical disciplines to understand. However, in recent years it has become difficult for even IT professionals to divine the actual responsibilities of a given position's role as job titles become increasingly more nebulous and the descriptions more buzz-wordy. At one time, we all had a reasonable grasp of the role of a 'System Administrator' or 'Helpdesk Technician' but now such roles may actually have significant DBA or developer responsibilities bundled into a lesser job title (such as the recent trend of 'Desktop Support Techs' with SQL DBA responsibilities), often robbing the holder of a fair position (and traditionally better paid) title on the résumé. Are these trends a contrivance by corporations to get more 'value' from IT professionals by bundling responsibilities of higher paid jobs into lesser roles and to evade competitive salary by creating titles that have no analogue on pay-scale indexes? Has there ever been a proposed standard for information technology position titles (or at least some form of translation guide)? How do Slashdot job searchers contend with these wildly varying, and increasingly vague titles that seem to have saturated the industry, or worse, when they've been festooned with an inaccurate or absurd job title?"
Yeah, that's pretty descriptive, it's all I put on my resume and they know EXACTLY what my career was about.
I'd love to know the man-hour charges racked up scratching our collective heads about what the titles and job descriptions needed to be.
I especially loved being an architect -- I had as difficult time defining it to people as they had grasping it.
I also get (got) a kick out of people and their "I LOVE ME" walls in their offices and cubicles, pasting and taping up all of their certificates for classes they'd taken, certifications achieved, etc. In the final analysis, I don't ever see a consistent and understandable title/job description semantic, especially in IT where the landscape changes dramatically sometimes in months. (Other professions seem not much better defined, btw.) If your management is good, they're more tuned into and cognizant of what each employee does well and how to balance work loads accordingly. If they're not, they'll obsess about job titles (sometimes employees do the same, and drive management crazy).
I'm a DHCP and DNS Dominatrix. I'm not even a woman. Craziness. Pays well, though. Get to wear jeans. And a ball gag.
For non-managerial positions:
Sled Dog
Lead sled dog (same work, better view)
My (nontechnical) boss once told me he thought of me as "Mr. Go To".
I said, "fine, just don't mention it to anybody else."
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
Chief Technical Dude.
It's fitting & I liked it, so that's what my title is.
Though a friend of mind (in IT) had on his business card Director, Piratical Affairs. Which is better.
--Pete
Need we say more?
How we know is more important than what we know.
What gets me is that the pointy-haired types attach so much baggage to the title, like it's a cattle brand or something. Especially with the current corporate environment (thank you, Sarbanes-Oxley), the same exact job can mean two different things, depending on the title...
For example, I work for a fairly big Fortune 500 as a developer-slash-DBA-slash-webmaster (you know the drill, many hats, one paycheck). Last month, I was "Systems Development Specialist". Until they decided that anyone with "developer" in the title was an offshored cubicle dweller with all intention of getting their hands on some identities and credit cards (hey, I didn't make this generalization, don't blame me). I was already busted down from having domain admin privileges to local admin on just a few boxes (SQL server, webserver, development server, and my own PC). After the new title policy change, I was going to lose everything but the developer login, and I would even lose local privileges on my own PC. That was pretty much the last straw for me, since I figured after 7 years of pre-SOX full access, where if I'd had the will (and total lack of morals) to do so, I could have made it out of there with thousands of credit card numbers. What do they reward my loyalty with? Shackles. "Here, wear these boxing gloves when you code, it'll be harder for you to do it, but our data will be safe from your evil wicked ways!"
Anyway, as I was about to hand in my notice, my immediate supervisor, a down-in-the-trenches network guy who ended up Site IT Manager, told me he managed to get my title switched to "Senior Information Management Specialist". Guess what my job description is? Exactly the same as System Development Specialist, although couched in more generic terms to prevent any instances of "developer" or "programmer" to show up. And now I have my access back, and I don't have to have someone hold my hand and wipe my ass when I implement change controls from my dev environment to production. All because of a few words in the title, I went from criminal suspect to a functional member of the IT staff.
Every jumbled pile of person has a thinking part that wonders what the part that isn't thinking isn't thinking of.
It happens everywhere (and has been for a good 5+ years now).
Basically, low-end/crap jobs are being given fancier (and fancier still) job titles because:
* They attract poseurs who can handle the low pay that goes with them as long as their job sounds impressive to their peers.
* They look impressive in a Resume (thus being an acceptable stepping-stone job - used to attract people to low-skill, high-turnover positions)
* It's easier to get people to work a bad job if it sounds important
* The cotton-wool generation just starting to get into the workforce, who have been brought up being told they can never lose and never having had their feelings hurt, don't get all depressed about "only" being a "Secretary" or something similarly mundane.