Achievements on a IT project manager CV

[BigMonk]

It’s been a while since I've written a CV and all the guides I have read suggest writing numerous achievements under my current and previous job titles.

Unfortunately I keep falling fowl of writing my job role and not my achievements, but the problem is I don’t think I have any.

I do my job to the best of my ability and I deliver projects on time and under budget, but you would expect this by default so it seems pointless bothering.

At best I can think of a few things but they would only be understandable/relevant to my current employer.

I’m a bit of a loss really! Any advice would be welcome, thank you.

[davepoth]

As a project manager you're lucky since you have projects. Write down how you implemented x system under budget and ahead of schedule. Rinse and repeat.

[Podie]

Any prospective employer wants to know you can deliver on time and budget. Show that you can...

Have you delivered any particularly complex, large or expensive projects? Run a programme of work?

[BigMonk]

That sounds simple enough however a lot of it is just hard work, common sense, and good use of PMO material.

Also I can’t get too specific and anything too successful would require proof which for obvious reasons would not be forthcoming.

Just to clarify I work with software and not hardware.

[Podie]

Management of stakeholders? Internal or externally facing customers?

A good CV is hard work, but depends on whether you want the job or not.

[rog007]

All good advice there. Your reaction to this issue is not unusual so you can take some solace from that.

Do exactly as you say, and whilst you think it is unremarkable doing your job well, you have to present evidence as such to convince a hiring manager to sift you in to interview. Maybe thinking of it as outcomes rather than achievements may help you to frame it better. And include metrics where you can as suggested above. Happy to look over your CV if that helps to see if you're on the right track. Good luck!

[davepoth]

BigMonk said:

That sounds simple enough however a lot of it is just hard work, common sense, and good use of PMO material.

Also I can’t get too specific and anything too successful would require proof which for obvious reasons would not be forthcoming.

Just to clarify I work with software and not hardware.

Unless you have signed an NDA (or the Official Secrets Act, conceivably) everything is on the table. The more information you put down the better - don't worry about proof, it's rarely asked for. If you can't do what you said you could they'll fire you quickly enough, that's the evidential test.