Resume Question
 

Brushing up my resume and am trying to figure out how to handle a unique situation. I work in IT for a large government agency that has 40 autonomous departments/budget units. Each budget unit has specific job codes assigned to it and each budget unit had their own IT department/infrastructure.

In 2013 I was selected to work on a common directory migration in which all the IT resources/infrastructure would be merged under one group. So in 2013 my old boss recruited me and I went back to his department under a job titled ADSM because it was what was available that fit my compensation needs but doesn't reflect my job at all. Then as I got merged in with the main IS group my title changed to ISM2 which came with a small bump in pay but also doesn't reflect my job and my duties remained the same. Then I got changed to Sr. Systems Engineer which came with another bump in pay but accurately reflects my job. This spans 2013 to 2017. The entire time my role/duties have remained the same.

This will all be changing again soon and I will be getting another fairly large bump in pay with a different title but same duties as a new management group is standardizing all of the job codes/positions and realigning salaries. How should I reflect these changes on my resume?

Make up your own titles that accurately describe your activies. You could put a note on if you want to be completely transparent.

People should understand that sort of thing. Titles are pretty worthless IMO.

Put the title that you ended up with at the end - if you need to explain - you can. A resume is more of a recap - not a play by play

Why is that green? From my limited exposure to hiring and going through 100's of resumes for an entry level job, I'd say that's true for 99.999% of the ones I saw.:eek:

Wow that was fast! Thanks for the responses. If I kept only the current title, wouldn't this get flagged when a perspective employer does an HR check? Where would I enter an explanation, on the resume or cover letter?

On the resume. I put something like "Contracts Director (formerly Contracts Manager)" for each job listing. It shows what you were hired as and what you ended up as.

This.

Got it. Thanks for the advice!

With IT or any computer field related resume I would say to not worry about the job or position title at all. Enter thing such as how long you did it, what hardware platform(s) you worked on and in detail what you did with them. Do the same with software, usually keeping applications/databases separate from the operating systems. Try to remember the size of any databases I.E. 10TB with 1200 users 24/7 with nightly hot backups. This database system was upgraded from Oracle 10.x to 11.x over the space of 9 months. Hiring managers (I was one) and those wanting a new job (I did that) want the details. Be careful of acronyms or abbreviations as they can become obsolete in a year of the job you did two years ago now has a nice catchy name that did not exist?


As example in 1999 I installed the first Windows server at a shipyard where I worked and installed an early version of the SAP monster application with nightly hot backups to an off line server. This systems supported 24 financial users and produced reports for US Federal Government contract administrators. The tot time from unpacking the server to coming on line was 3 months including a new data load.


Hope this helps.

cant offer any real advice or help.

but just wanted to wish you great luck!!

Are these promotions merit based, or does a resume need to be submitted for consideration ?

It seems that the middle paragraph of your original post described everything you have done up to this point, could something similar be used on your resume ?

I look at a lot of resumes (IT service provider) and I can say the titles don’t matter as they can all be different for the same job. Just make sure to highlight your work and successes under each title.