Last week, my boss came to me and said that the title of my job isn't really accurate. I agreed. He wants to try to get my job title changed, and he said there's a chance that it might actually boost me up a pay grade. Part of the reason he wants to change my title is because he's trying to higher a backup for me (I have way too much work for one person) and he's not attracting the right kind of applicants. So I have before me a fairly rare opportunity to have the title of my job changed, which could possibly get me more $$$. Problem is, I'm not really sure what an appropriate title would be for my job, and my boss isn't quite sure yet either. He said that if I thought of any ideas to let him know. Hopefully I can somehow take advantage of this opportunity. Hopefully one of you might have a good idea.

So right now my title is Configuration Analyst. There are about 10 other Config Analysts in my department, but my job is completely different from theirs. So let me explain what it is I do, and how it's different from everyone else. Most config analysts get assigned change requests from other departments to make changes to our core claims processing/customer information system. They analyze the change that is needed and figure out what tables need to be updated. Sometimes they key the changes through the front end, but sometimes the changes are huge and require a change through the back end. They'll send the criteria to me, I write a SQL script to make the update, and then I coordinate with the DBA to get the script loaded. So I'm basically the point person from my department that coordinates all large changes with database administration. Sometimes these changes are in a testing database and sometimes it's for Production.

There are also a number of routine scripts that run daily that I have to maintain. Most of the ones that run daily use MS Access and sometimes I have to change around the VBA code to meet changing demands. I also research new ways to create automated scripts for changes we make on a regular basis.

I'm considered the querying guru in the department and people come to me when they need help running queries. I also sometimes provide people with training on using SQL or Access. As part of my job, I need to be the expert on not only writing SQL, but with knowing how to use the data models. Sometimes management comes to me with a need for random reports that require complex queries that draw information from a number of tables. I need to be able to figure out how to use the data models and data dictionary to pull the right kind of information.

I also do research into improving data integrity for the configuration tables. I maintain a number of scripts that run nightly and inspect the reports for issues related to referential integrity.

Can anyone think of a good job title for this? Preferably, something that sounds more important than Configuration Analyst, so that HR will grade my position higher.

Lead database administrator
Lead information systems manager

I would work with HR on this. In my experience, they usually have tons of job titles and descriptions that loosely correspond with them. If your boss talks to them, you may all be able to work together to come up with a more accurate job title.

This is a pretty unique opportunity especially with your boss's support and if I were you I would obviously push for something that looks better and likely comes with a pay raise.

I'm not very familiar with jobs in your role but I would think this means possibly dropping the "analyst" portion of your title, or maybe changing your title to Senior Configuration Analyst or Senior Database Administrator or Database Engineer. Someone who works in HR either here or at your company should be able to help you a lot more with this.

I would call it "Operations Specialist", or maybe "Operational Database Engineer" or maybe "Operational Request Engineer". I think I like #3 the best.

"They are screwed if they fire me" sounds pretty good.

If your DBA isn't doing what you're doing then what is he doing exactly? To me a DBA would be doing what you're doing in addition to making sure nothing explodes day to day.

Maybe "Database Architect" (Engineer works too but Architect sounds a lot cooler).

Database Engineer is good because that is probably most likely to get you a pay bump. architect sounds cool, but is probably less likely imo

What is the DBA's title? Just Data Base Administrator?

What is the relationship between the DBA's boss and your boss? peers? how far up the chain to their common boss?

What is your bosses title?

Is your department just the 11 of you? all reporting to your boss?

Architect implies he designed the database which he didn't, engineering is generic enough though.

Best job title I ever saw was a guy who I met at an Oracle convention. His job title was 'Data Wrangler'.
You are a data wrangler.

Serious though, you correct data via supplied screens or SQL fixes. Seems to me to be a programmer type position. But, since you are a configuration analyst, and you are "the man", you should be called the senior configuration analyst IMO.


Also, 11 people to fix stuff? How is this junk getting messed up? Sounds like an auditing nightmare.

The rest of us just use Data Analyst. The title conveys a wide range of skills.

Database Administrator doesn't fit unless you perform actual administrative tasks like backups, cleaning up transaction logs, managing table statistics, etc.

Database Developer/Engineer doesn't fit unless you design the actual OLTP systems in the company

Database Warehouse Developer doesn't fit unless design the OLAP systems

Maybe I read your write up incorrectly but the it seems like the extent of your programming is just creating SQL scripts for whenever they need to update existing data, stored procs, etc?

Let me know if I missed something here.

Also, if the title is tied directly to pay then just get a list of titles from HR with their pay brackets then pick the one that corresponds the best with your job functions.

I thought this question was more on what to put on your name tag/resume.

This wouldn't work because I'm definitely not a database administrator. I write SQL scripts, but I don't really do any other DBA type maintenance or functions.

Yes they are screwed if I left, which is why they're desperately trying to find another guy. I don't know exactly what our DBAs do, but I'm assuming it's maintenance, repair, and security type stuff for the Oracle databases. I can write SQL queries, but I don't know anything about configuring an Oracle database.

I like these titles and I'm sure they'd come with a pay bump, but when I google for architect and engineering type positions in the technical field, they don't really sound like what I do. So I'm not sure if I could get this to fly.

Right now we're in this weird position where we're all reporting to the Vice President. There is an open manager position, which I think has actually just been filled, but he hasn't started yet. So it's my vice president that I've been talking with about this.

I think 11 was actually a little too low. Now that I think about it, there were a couple people I forgot about. Probably more like 13-14 people, and we still need a little more help. I work for a health insurance carrier in NY, and the amount of configuration required to keep a health insurance company's core systems up-to-date is huge. Think about the thousands of doctors, hospitals, provider groups, members, products, procedure codes, diagnosis codes, etc. And then there's all the health care legislation. And thousands of claims being processed on a daily basis. It goes on and on and on. And this information is constantly changing. Constantly being updated. It requires a dedicated team to really maintain the system.

You pretty much have it right and I probably have to agree with you. My programming is basically SQL scripts, VBA scripts, and writing macros. People can learn SQL, but my strength in the company lies in the fact that I know both the front end and back end really well. I can speak the language of the configuration analysts and the database people. Most people only know one or the other. I'm also good at just "figuring stuff out". There's no manuals or step-by-step instructions for many of my job functions.

I was toying around with titles like Configuration Architect or Configuration Data Architect, but as others mentioned above, the Architect title is probably not an accurate representation of what I do either. Damn.

So then I was thinking maybe something like Data Management Coordinator, or Configuration Data Coordinator, or Configuration Data Management Coordinator. Not sure if that sounds too supervisor-ish though. I feel like it kind of fits though.

Maybe my best move is to just stick with analyst, but try to get senior or lead in the title. Like maybe Lead/Senior Data Analyst, Lead/Senior Configuration Data Analyst, Senior Configuration Analyst (as someone mentioned above). We already have Lead Configuration Analysts, so I'm not sure if I could get that.

MLMIC?

(Senior) Database (Integrity) Analyst?

Try to get it changed to "Carpal \'Tunnel"

That's actually pretty good. The reason I asked is that depending how political the environment is, some of the suggestions might have been stepping on the toes of the DBA group.

Sounds like you should have a fair bit of flexibility.

Can you possibly become the manager / team lead of your group? Seems like your VP has way too many direct reports, and that you are already helping to manage the work they do.

Perhaps a team lead type role where you don't hire and fire or manage the budget, but do oversee the work done, and then gradually get up to speed on the administrative side of management?

This is kind of along the lines of what I might push for. Except, I can't push to be manager of the whole config group because we just hired a configuration manager. Plus, I've only been with this company a few months, I don't have supervisor experience, and I don't know the business well enough to be manager of the whole department yet. But I do think I'm knowledgeable enough to lead the technical operations of my department.

So what I'm considering doing is trying to push to be like a team lead of the database/technical/back end aspect of configuration. As the team lead, I could help train analysts we already have on SQL and the back end. The skill set we're looking for in a backup for me is pretty rare (knowing SQL, VBA, AND the front and back end of this particular health management system we use), so this would solve that problem. And it would take some pressure off me because I'm drowning in assignments. Since I'd be training people with no SQL experience, it might be rough at first, but as long as they're bright enough, willing to put some time in to learn, and have me there to ask questions, I think it could work. Plus this would be a step toward becoming a supervisor (I'd ultimately like to be in management someday). Even though I wouldn't have true direct reports, I'd be a titled leader of the department and would be overseeing work. So maybe something like Lead Configuration Data Analyst/Lead Database Analyst/Lead Data Analyst. Maybe I should stay away from Database in my title though, because like you said, I don't want to be stepping on the toes of the DBA group.

This discussion is really helping me out with this. Thanks to everyone who's contributing. I'm still in my 20s and I've only got about 5 years of business experience, so it helps to get the thoughts of people who have been in the corporate world for longer.

I probably read too fast, but I thought before you mentioned that you were working directly with the VP and reported to him, probably lazy reading by me and not too relevant i suppose.

Something like Configuration Team Lead would be typical in some places, referring to a technical specialist who oversees work done but doesn't have hire/fire.

I've seen Scrum Masters who held the official title of "Engineering Team Lead", for example. A Manager or Director had the reports, but the team lead title recognized the scrum master's contributions to organizing the work.