EDIT: I just wanted to add an edit and say I really appreciate how active this post got. I was kind of expecting to get no responses, but instead I'm getting an incredibly detailed discussion with a wide range of viewpoints and considerations that I wouldn't have otherwise thought of. You guys rock! Lemmy rocks!
Hey, all
I need help identifying a job title that would best match my current job responsibilities. For reference, I work at a smaller org that just had a compensation study done and my position was marked as needing no change. My supervisor was angry with that outcome and found out that it is because my actual Job Title is not an industry standard, so the company that did the study had trouble matching it up. My supervisor believes I should be making a fair chunk more than I make, as I am the sole person in my position and the work I do keeps the org running in all ways.
So, my supervisor is starting the process to reclassify me into new position and wants to make sure the title and responsibilities match up in a way that are recognizable on a resume to other potential employers. I've done some initial research and I believe that "Senior DevOps Engineer" or a flat "Senior Software Engineer" would probably be the best match.
A list of my responsibilities are:
- I investigate, troubleshoot, code, schedule, and deploy new custom programming releases to our ERP software. It's a delivered ERP software that has the ability to create, package, and deploy custom coding in order to add functionality that the org needs but the delivered solution does not support. Our org is especially heavily customized - we have well over 200 different customization's that I support
- I code, deploy, and support data integrations with third party vendors via SFTP, HTTP API, or other options (although most of the integrations come down to either pulling data from our system to push to an SFTP server or an API).
- I build and deploy custom applications on an ad hoc basis to fill needs by our org. An example of this would be that earlier this year we found out that the budget entry portion of our ERP software wasn't available as it used a user interface that had reached end-of-life and we needed a way for departments to enter their budgets for the upcoming FY to buy time until we could get the proper user interface up and running. I was able to build a web application that could fulfill the requirements and coordinated with our systems administration team to get a server set up with certs, a proper domain name, and the like.
- I act as a general administrator for our ERP software, providing support and guidance on specific functions that members of our Org use as well as backing up our actual ERP Technical Administrator in maintenance tasks if he is sick or out.
- I support the deployment of data from our transactional ERP system to a reporting database and our reporting software. This is largely automated and works without interference. If new data is needed, I go in and make the necessary changes to include the new data in the reporting database.
- We don't currently have any other developers, but my boss and I have started pushing to expand our slate as other members of our team retire. If we ever do get more developers, it will be my responsibility to train them and coordinate their tasks.
In general, I feel like I identify more as a Senior Software Engineer. I like the programming work more and, if I ever left this current org, it's the job I would go for. However, for the sake of actually matching the position, I feel like the wide range of development, administrative, and automation duties, that I am more doing the job of a DevOps Engineer.
I've done a fair amount of reading, but I wanted to get the opinions of some peers and see if you all had any insights or opinions
Yes, that pretty much my point :)
Thank you!
I will see about sticking with the Software Engineer line of titles (I'm discussing whether or not calling myself a 'Senior' would be a good choice with some other commenters). It makes more sense and my supervisor had mentioned that she wants the best title that could represent my skills, responsibilities, and desired future jobs on a resume.
Well, I do have an opinion on that as well.
Senior is a nontransferable honorific, as in: it does not translate between organizations. I have had people who were senior in their old organization demoted to junior (aka. they mostly quit) because they could not write a line of code without internet or IDE to save their life, and I have had people come in as junior even though their started programming when they were 12 and could programm circles around most seniors, buy HR decided they had "no experience" after collage (which, in my opinion, boils down to exploitation of cheap labor). I also met a guy who was an good developer but at his company it was a formal requirement to give a talk to advance to senior. Even though he had 15 years of experience at that company non the less, he could never advance because he was afraid of public speaking.
So seniority is at least as much politics as it is skill or responsibility. In my experience, it boils down to whether or not you feel you deserve it. If the answer is yes, then you should see that you get it and that you are treated (paid) accordingly.
I see! I definitely feel that Senior would be applicable for this given position. All of my hang ups were in thinking there was a more defined requirement to be a "Senior". Between you and my discussions with others, I've learned to not worry about that and instead focus more on my knowledge-level and my direct contribution to the Org - both of which I would say are appropriate in this environment.
Yeah, I tend to agree, the responsibility should definitely warent it.
Good luck with the whole thing, I hope you get a decent bump out of it :)
Thank you! I appreciate your help