SysAdmin -> Jr Project Manager

Hey PMs

I've been studying project management in my spare time for around 6 months and I've concluded that its the direction I want to take my career. I think I've got the hard and soft skills necessary to make it as a very talented PM and I was wondering if some of you vets wouldn't mind taking a glance at my resume and giving me some constructive criticism.

http://imgur.com/gallery/LIZ1zFo/new

Ideally I'd like to work as an international PM for an IT company... but you got to walk before you can run. Looking for a Junior Position at the moment. Also apologies if the quality is a bit poor... I can upload another one if need be.

Thanks

Posted Nov 11, 2015, 12:26 AM UTC · edited

85
AFDIT•

I came from :

Sysadmin (Jr DB / server admin) ->

Web consulting (Wordpress, bespoke PHP builds managing 1 or 2 devs to build the product I sold to the client) ->

Bits of sysadmin stuff thrown in at the same time as well as hardware fixes ->

Jr Project Manager in a small, sophisticated web dev outfit ->

Promoted to Director of Operations in the company and left to run it within 3yrs.

It can be as useful to have decent industry knowledge as having the PM know how. If you can talk to both technical and non-technical people and get everyone on the same page you are valuable to a company.

Your CV looks strong already. I'd suggest you just choose to take some interviews for jobs you like the sound of. No need to alter the CV before the interview - just talk about your change in career as something that's already happened / begun and stress where you have already taken on management duties.

In my case the company I moved into as a junior PM was starting to change and that helped me get in and move forward quickly. Also they had the right company culture and I could learn by example from the start.

As your background is IT it sounds right that you stay in that industry to aim to get your first PM position.

One thing I found was a need to step back from some technical decision making (we do Scrum / Agile, so the dev team make those decisions, they do not come from the top down). As you are technically minded it would be a case of introducing questions to let other people make the right decisions (if you do Agile style management).

Hope this helps.

3
InostranetzOP•

The advice was much appreciated.

2
sm1rks•
  1. Structure:

One page, small margins; strong start.

Use 10 point font and cram the resume full of information, Times New Roman is a good font. You want space for everything relevant.

Rename Experience to Job History. Reverse chronological order is good.

The job details should be in bold and underlined, beginning with the dates then: a colon, formal job title, hyphen, the company (and division if relevant), comma, location. I.e.

Jan 2012-Present: Project Coordinator - IT Company, Flyover, Kansas

After the details header, put 2-3 sentences about your major responsibilities in the role. After that, put as many bulleted items as possible relevant to the position and ideally relevant to the responsibilities. Should for on one line to save space. Should roughly follow the form: Verb, quantified result, method. E.g. Maintained 99.999% uptime for service X by performing Y. Completed all projects on time, on budget, in scope

  1. Content:

There is a date gap between your present employer and when, presumably, you graduated college. As a hiring manager, I assume you were in prison if you can't account for that much time.

Remove the certifications and expertise sections. Put each item as an achievement in the context of a job.

Looking at what you have presently I can't make any safe assumptions about your work. Tell me what you did and how well you did it.

Do you cook code at home? Find another way to express that than homecooked. Provided value-driven healthcare IT management doesn't tell me what you did. I can't close my eyes and imagine you "providing value driven IT management. 99.99% doesn't lead the industries of healthcare or IT, so that just seems disingenuous without more context. ...by diminishing overall server footprints: tell me how many physical servers you got rid of, and how you did it. In all the above, I get the gist of what you're saying, but the way yore expressing it is unclear. Just revise those to actions taken versus vague concepts.

What you have is a good start, but it comes across like a rough draft.

2
InostranetzOP•

wow thank you for the advice. In regards to the homecooked code thing I actually placed that in there in order to not identify what our company uses on our systems... it would be a bit of a giveaway if I did.

As to the experience gap I was traveling in Africa working on a nature reservation... not sure how I can include that on my resume though

1
sm1rks•

If you were working on a nature reserve, it goes on your resume. Maybe you don't have many responsibilities and accomplishments, and maybe the role isn't easy to make applicable to the position for which you're hiring, but if you leave it as a gap and I find out you were employed, I'll assume left it off because you were fired. It's a six month position, it won't make or break your resume, but leaving it blank means I need to ask you in the interview. Putting it in tells me you did something I wouldn't otherwise know you had done.

1