Hi everyone!
I'm Sharee, a senior Jira Admin with the USSF.
So, I have a question.
I've been in the Atlassian world for about 7 years now. And as many of you know, I rarely ever just do true Jira Admin-ing. This may be in part because people don't know what I do, or because I'm nosey and like to use my full range of skill set when at a company.
But either way, it seems most Jira admins tend to do more than our job description.
For example, my big thing is process improvement using Jira as a tool. This year alone I've wiggled my way through the building and have saved our help desk over $600k a year, and improved their process and efficiency by over 30%.
Another instance I introduced Jira, and a massively improved process, and essentially un-did a $3.5m service now hole they were digging.
I realize this isn't typical, but it's what I gravitate towards and what I'm good at.
How do you best represent something like that on your resume or to future employers? Would I still be considered a Jira admin, even if my actual Admin-ing makes up less than 25% of what I do?
What do you guys put for the many hats you wear?
Hey Sharee,
When I started I was mainly doing actual admin work, user management and the technical solutions in Jira and JSM mainly.
Later on I did what you're doing and it's more than just the "simple" admin work. The team grew and I called ourselves the IT Solutions team. We're working internally for the company and to show that we're belonging to IT we added that little prefix.
Our job roles grew into engineers, I would see myself as a solutions engineer or something similar. I struggle with naming conventions and don't know exactly what people would know me by. It's definitely right that we are Atlassian admins but that doesn't tell the whole story.
I hope you can find something that makes sense for you. Definitely you're more than an Atlassian admin.
Best,
Jousef
@Sharee Khaldi I think what you've described falls under the heading of "and other related duties".
All joking aside, I think this is more common than you realize. I have built mini-ERP systems to support manufacturing and purchasing operations out of need. I find it to be a challenge to learn how to do this without buying marketplace add-on tools due to budgetary constraints.
I would recommend you get whatever certifications Atlassian offers to list on your resume and use your project experience as examples of your proficiency. If you plan to use big numbers like $3.5M I suggest you be able to back that up. Be able to explain how the process was before hand to show the cost increases and how you changed/improved it to show the savings. Cutting out unnecessary process steps can also show the potential employer how you think "outside the box" as they say.
Good luck.
Sounds like you can make up something that has words such as Process, Engineer, Support, and maybe Atlassian Administrator. It's not a clearly defined role so I wouldn't expect there to be a clear title for the position
I use the words Software, Toolsmith and then get to explain whatever it is I'm doing currently. Good luck!