CV Development for PMO Professionals
Module Four – Your Career History
Hi, welcome back to the fourth module.
In this session, we start to look at the more detailed parts of your career – the career history.
Up until now, we’ve not really covered any formatting of the CV – or how to present what you have on paper.
With the career history, we will cover not only what to write but also how to lay that out in the CV.
We will be concentrating on your most recent job – this is the one that the hirer looks at first, it’s the most recent and relevant to them so it makes sense that we will spend most of our time perfecting this one.

As a rule, you’ll be looking to give more details in your career history that span the last five to ten years. Experience after that date is still recorded on the CV, just with less detail. We’re aiming for a CV that is no more than three pages in length.
This is longest module in the series so let’s get started on the career history part of your CV.
Career History
Introduce the Role
Let’s start with the basics.
You need to include the date of your role – so that’s Month and Year.
Next is your job title whilst in that role – that’s the actual title you had.
And then the company name.
If you think your job title is misleading or you think it wouldn’t make sense to anyone outside the organisation, you are able to add a more employment market-friendly title in brackets, for example:
04/2018 – Present – Client Engagement Co-ordinator (Project Co-ordinator) – IT Sytems Ltd.

Many CVs fail to introduce the organisation you’re working within. Some organisations may be well known names, others less so.
It’s good practice to add a line so the hirer can understand a little about what kind of organisation and in which part you were working within.
Here’s an example:
Thames Valley Probation is a governmental organisation working with people who have committed unlawful offenses. Working within the probation services division, the role of project co-ordinator supports multiple projects across the lifecycle.
And another:
Strawdog Studios are an established game studio with a blue-chip client base; reporting to the Head of Projects, the project co-ordination role supported all game development projects of varying months in length with budgets in excess of £100k and teams of up to 10 people.
And finally:
Saint-Gobain Glass is a worldwide manufacturing group with £43 billion revenue and 220,000 employees. Hired to create and maintain a programme office function which supported a portfolio of 100+ projects.
Write Your Own Introduction
Start to create your own introduction to the organisation and your role based on the examples given.
If you are able, get family or friends to check that for you – do they understand what the company does based on what you’ve written?
Think about who you are writing this CV for; put yourself in the hirer’s shoes, do they have the right level of information to understand the type of organisation where your experience has been gained?
Presenting the Information
There are three different ways you can present your experience within your career history.
We’re going to look at each one in turn and you can make a choice about which one you prefer.
Later in this session there is further guidance on how to write about your experiences and common pitfalls to avoid.

Simple Bullet List
The first example is a simple bullet list.
With this format we’re taking a look back over our notes generated in Module Two when we looked at the personal stocktaking and thinking about the tasks and activities we performed in the role.
There are several ways to think about the ordering:
- Think about your daily, weekly and monthly role and create the list in chronological order.
- Reorder the list each time you apply for a specific role so the ordering is in line with the job advertisement.
- Think about the services offered by the PMO in line with the programme/project delivery lifecycle.

Tasks with Details
The second example is great for combining several different tasks and activities which produce a certain outcome.
This layout is easy for a hirer to understand what your role consisted of and the types of skills that were combined to carry out the work.
You’ll notice with both these examples so far that the language is project management / PMO focused and not that of the organisation – there are no acronyms or any other company-specific details that a hirer wouldn’t understand.
This particular example works well for project / programme support roles which are not within a PMO – our next example is most more PMO aligned.

Services with Tasks
This final layout shows how you can present your information in relation to PMO services.
You might opt for this layout if the role you’re applying for details the types of services offered by the PMO.
It makes sense that if a job advertisement is clearly laying out the roles and responsibilities in line with PMO services that your CV should also make these clear.
With this layout you can also tailor your CV each time – adding in and removing services depending on what the advertisement is asking for.
For all three of these examples, the career history focuses more on the types of tasks and activities that you’ve carried out rather than the benefit of having carried them out.
Let me explain that in the next section.

PMO Management
So far the examples cover the roles working within a PMO or supporting a programme/project.
If you’re managing a PMO there is a slight change in how you present your information.
With PMO Management it is imperative that the hirer gets a quick sense of the type of PMO you are managing.
This has a big impact on seniority and salaries/rates of roles too. If the hirer can’t quickly see that you have the experience to operate at a senior leadership level, they will quickly move on to the next CV in the pile.
With these roles, it is a good idea to include details like the number of people in the PMO (being managed by you); the span of control; the budget size; and where the PMO sits within the organisation (the level of seniority and accountability)
Further examples are available here:


How to Write About Your Experiences
For PMO CVs it doesn’t matter as much which industry or types of projects you’ve been supporting and where those experiences have been gained (unlike Project Managers where hirers tend to prefer their PMs to have specific experience in delivering certain types of projects)
But is it important to set the scene and let the hirer know what type of PMO or project supporting role you’re doing – hence the need for that introduction to your career history.
With PMO focused CVs, the career history part of your CV should emphasise your practical experiences and skills.
The hirer is interested in what experiences you have PLUS the skills you’ve used.
What is important that you’re able to demonstrate what we refer to as competencies.
“Competencies include all the related knowledge, skills, abilities, and attributes that form a person’s job”
For example; when writing about your resource management experience – resource management is both a service within PMO and a competency area which includes associated knowledge, skills, abilities and so on.
Here’s an example on how we might write about our resource management experience:
Responsible for providing a resource-tracking and capacity planning service across the programme of work – includes weekly reporting and forecasting service to senior executives.
With a CV we’re limited to focusing on knowledge and skills – the factual elements of our roles. The abilities and attributes are the parts that are picked up and covered during the interview. For now, we’re focused on writing to get on the shortlist and gain that interview.
A Sample CV – PMO Manager
Let’s take a look at a few real-life examples. First the PMO Manager role.
This example is OK, I would give it about 5 out of 10 – so pretty average.
Here’s why it doesn’t get 10 out of 10:
- There’s a lot of words and the smaller font is difficult to read (remember, the hirer will be looking at hundreds).
- It’s a UK CV so Americanisation of words like organization needs to be changed.
- I have no idea who Lyons Boss are or what they do – not even what sector.
- A Group PMO means nothing to me – does it mean there are other PMOs in the organisation?
- What’s the size of the PMO and the accountability levels for this PMO Manager?
- “Projects delivered on time, within budget and to specification” lots of words to pad it out and are unnecessary.
- First two paragraphs seem to have been lifted from a job specification and it shows.
- Management speak – first bullet point – needs to be in Plain English
- What is Workstack? internal stuff the hirer doesn’t have a clue about.
- How much of this role is managing projects? The lines seem to be blurring.

A Sample CV – PMO Support
With this example, it’s a Project Support role and believe it or not, this is pretty typical of the type of CVs I’ll see.
This example gets about 2 out of 10 in terms of presentation and here’s why it doesn’t get 10 out of 10:
- No introduction to the organisation or the role they’re performing – it’s difficult to understand what the Project Support Officer is supporting.
- Much of it is just a list of project artefacts like logs and registers – so what? Tell me what you’ve done with these!
- No details on the type of tools used – for example, what was used for the plans? Details on tools and techniques matters.
- No sense of what this person has achieved – or how some of the tasks carried out. Business continuity planning? How did that go?
- Overuse of project keywords with no context – it could imply that these have been copied from a textbook.

The Rest of the Career History
Throughout this session, we have concentrated on the most important part of your career history – the most recent!
This is the one that gets the hirer’s attention first so we spend more time crafting that one.
For the rest of your career history, you’re using the same techniques but you will start to write less and less.
We mentioned before that it is generally the last five years that are the most important to a hirer so we make sure there are enough details covering that period.
Over time, and being mindful that the CV needs to, ideally, fit within 2 to 3 pages, we can reduce our career history to line items.

Listen to the Video
In this 25 minute video you can get more detail on creating your career history using the documents we’ve covered today:
Bits and Pieces on Grammar
Finally, in this module here are a few pointers about writing your career history.
1. Make sure you use a range of different adjectives; adverbs and action words in your career history.
Starting every bullet point with ‘managed’; ‘co-ordinated’ or ‘liaised’ obviously gets repetitive after a while so why not take a look at the document to get some inspiration on other words you could be choosing.
[Useful Words for a CV can be downloaded here]
2. Check your spellings
A good tip after using the PC to spell check it is to read the CV backwards! It really does help you spot other typos when you’ve been staring at the same document for a while.
A lot of our work involves communication by the written word so don’t fall into the simple trap of not being shortlisted due to typos.
Your next session will be with you in two days time
3. Same goes for grammar
If you’re finding it tough to write a particular bullet point and it seems too long- scrap it and start again. Keep it simple and in plain English.
Check to see if there are too many filler words that are adding length – remember the saying – ‘why use ten words when one will do’
If you’re thinking of adding any ACRONYMS – don’t. The only one that is allowed is PRINCE2.
4. Be consistent
If you’re writing about projects and programmes – these should be in the lower case. If you’re writing about job titles, like Project Manager, make sure you use the capital case.
5. Write in the third person
You should be writing in the third person throughout your CV – so no “I did this”. It’s considered to be more professional. When you’re tempted to write “I carried out x, y or z”, just drop the ‘I’ and see if it still makes sense without it. If not, try constructing that sentence again, perhaps using one another word from the list.
