A PMO job description sets out what a role inside the project management office owns, what it decides on its own, and what it reports on. A good one covers five things: the purpose of the role in one sentence, the duties it performs week to week, the decisions it can make without escalating, the experience and certifications that actually matter, and who it reports to. The most common mistake is listing every task the office does at every level, which produces a pile of applications from people who fit none of it.
Key takeaways
- Write the JD around decision rights, not task lists. "Owns the intake queue and can reject a request" tells a candidate more than fifteen bullets of duties.
- The level is the whole document. A PMO analyst gathers and checks data, a PMO manager runs the process and the team, a PMO director sets the mandate and answers to the executive who funds it.
- Requirements inflation is the reason good candidates skip your ad. Asking for a PMP, an MBA, and ten years for a coordinator role reads as a job nobody has scoped.
- Name the tools you actually use. "Experience with our PPM tooling" is filler; "we run intake and capacity in Smartsheet and report in Power BI" filters for real fit.
- A job description is not a responsibilities matrix. The JD is what you post to hire one person; the matrix is how the whole office divides work.
- Say what the first ninety days look like. It is the single highest-response element in a PMO ad and it forces you to be honest about the state of the office.
Last updated July 2026.
What is a PMO job description?
A PMO job description is the hiring document for a specific seat inside the project management office. It translates the office's remit into one person's accountability: the work they do, the calls they make, the people they influence, and the evidence they will be judged on. It is written to be posted, so it has to be readable by someone outside your company who does not know your governance model.
That is a different document from a PMO roles and responsibilities matrix, which maps how work is divided across the whole office. You need the matrix first, because the JD is a slice of it. If you cannot say which cells of the matrix this hire owns, the job description will end up as a generic list, and generic lists attract generic candidates.
The duties every PMO job description covers
Across almost every PMO, the same six duty areas show up. What changes between roles is not which areas appear but how much authority sits with the role in each one. The table below is the fastest way to build a first draft: pick the level you are hiring, then write two or three bullets per row.
| Duty area | What the JD should say | Level that usually owns it |
|---|---|---|
| Portfolio reporting | Produce the portfolio pack, chase and validate status, flag variances before the meeting rather than in it | Analyst produces, manager owns the format, director owns the message |
| Intake and prioritization | Run new requests through the intake process, score them against agreed criteria, prepare the funding recommendation | Analyst screens, manager recommends, director decides or takes it to the board |
| Resource and capacity | Maintain the demand and supply view, surface conflicts, model the effect of adding or delaying work | Analyst maintains, manager arbitrates, director negotiates with function heads |
| Governance and assurance | Run gate reviews, keep the RAID and decision records current, check that projects meet the standard before they pass | Manager runs, director sets the standard |
| Method and tooling | Maintain templates, train delivery teams, administer the PPM tool and keep its data trustworthy | Analyst administers, manager owns adoption |
| Benefits and value | Track committed benefits after go live and report what actually landed | Manager tracks, director defends the number |
If the office is new and none of this exists yet, the job description should say so plainly. Hiring an analyst into a PMO that has no process is a very different job from hiring one into a running function, and candidates who want the build will self select. The build sequence itself is covered in how to set up a PMO.
PMO job description by level
Titles vary wildly between companies, which is exactly why the JD has to describe scope rather than rely on the title to do it. This is the ladder most US organizations use, with the scope that distinguishes each rung.
| Role | Typical experience | Scope | Reports to |
|---|---|---|---|
| PMO coordinator or administrator | 0 to 3 years | Meeting logistics, document control, keeping trackers and the tool current | PMO manager |
| PMO analyst | 2 to 5 years | Reporting, data quality, capacity views, intake screening, template support | PMO manager |
| PMO lead or senior analyst | 4 to 8 years | A portfolio slice or a program, running its governance end to end | PMO manager or director |
| PMO manager | 6 to 10 years | The process, the team, the tooling, and the quality of what leaves the office | PMO director or a delivery executive |
| PMO director or head of PMO | 10 years and up | The mandate, the operating model, the budget, and the relationship with the executive team | COO, CIO, or transformation lead |
PMO analyst job description
The analyst is the role most often written badly, because it is easy to describe as "supports the PMO" and leave it there. The useful framing is data ownership. An analyst is accountable for the portfolio being true: that the status in the tool matches reality, that the capacity view reflects who is actually available, and that the numbers in the board pack can survive a question.
Write the purpose line as something like: "Own the accuracy and timeliness of portfolio data, and turn it into reporting the leadership team can act on." Then list the duties: collect and validate weekly status, maintain the portfolio dashboard, run first-pass intake screening against the scoring criteria, keep the resource view current, administer the PPM tool, and support gate reviews with prepared packs. Requirements should be light on certification and heavy on evidence of working with messy data. The full picture of the role sits in the PMO analyst guide.
PMO manager job description
The manager runs the office as a service. The purpose line should say that: "Run the portfolio governance process and the PMO team so that leadership can make funding and prioritization decisions on time and on evidence." The duties then split into three groups that a candidate can recognize.
First, process: own intake, the prioritization cycle, gate reviews, and the reporting calendar. Second, people: line manage the analysts and coordinators, set standards, and develop the team. Third, relationships: work with delivery leads, finance, and function heads to resolve capacity conflicts before they reach the board. Add the decisions the role can make alone, because that is the question every experienced candidate has. Can this person reject an intake request? Hold a gate? Reallocate a shared resource? Say so. The role in wider context is covered in the PMO manager guide.
PMO director job description
A PMO director, or head of PMO, is a leadership hire and the job description should read like one. The duties are not "oversee the PMO manager". They are: define and defend the office's mandate, own the portfolio governance model, run the relationship with the executives who fund the work, decide the operating model as the organization changes, and be accountable for whether the portfolio delivers what it promised.
Three things belong in a director JD that rarely appear. State who the role reports to and which forum it chairs, because seniority in a PMO is defined by the room you are in. State the mandate you expect it to hold, whether that is advisory, standard setting, or a directive office with stop authority. And state the current maturity honestly. A director joining a reporting function that wants to become an enterprise PMO is doing a change job, not a run job, and hiding that produces an expensive early exit. Where the office reports and how it is structured is covered in PMO structure.
The requirements section: what to ask for and what to drop
Requirements are where good PMO ads go wrong. Every extra "must have" narrows the field, and in practice most of them are not used at shortlist. Keep the list to what you would genuinely reject someone for.
- Worth asking for: experience running portfolio reporting or governance at comparable scale, evidence of working across functions without authority, comfort with the specific tools you use, and the ability to write for an executive audience. Ask for a work sample rather than a claim.
- Ask for at senior levels only: budget ownership, experience setting up or turning around an office, and board-level exposure.
- Usually optional: the PMP. It signals method literacy and is common in the US market, so it is fair as "preferred" for manager and above, but making it mandatory for an analyst screens out strong data people for no benefit. The PfMP certification is the portfolio-level equivalent and is genuinely relevant for director roles.
- Drop: degree requirements that have nothing to do with the work, arbitrary year counts, and long lists of methodologies. "Agile, Waterfall, PRINCE2, SAFe, Six Sigma" in one ad tells a candidate the role is undefined.
One practical note on volume. PMO ads attract a lot of loosely qualified applicants because the title is used so inconsistently across companies. If you expect a heavy inbox, decide the screening questions before you post, and if you use software to run a structured first round screen, keep the questions tied to the duties in the JD rather than to generic competencies. Otherwise you end up ranking people on interview polish instead of on whether they can hold a portfolio together.
How to write a PMO job description in six steps
- Start from the gap, not the title. Write down the three things that are not happening well enough today. That is the job.
- Pick the level. Use the ladder above. If the three gaps span analyst and director work, you have two jobs, not one.
- Write the purpose line. One sentence, outcome first. If you cannot write it, the role is not scoped.
- List six to nine duties. Grouped, not a flat list of twenty. Each one should be something you could review at a performance conversation.
- State the decision rights. What this person can approve, reject, hold, or escalate. This is the section experienced PMO candidates read first.
- Describe the first ninety days. Three concrete outcomes. It sets expectations, and it tells you whether the role is real.
Once the hire is in, the same duties should show up in how the office measures itself. The link between what you asked for and what you track is covered in PMO KPIs, and the mandate the whole thing traces back to belongs in your PMO charter.
Frequently asked questions
What are PMO job responsibilities?
PMO job responsibilities cluster into six areas: portfolio reporting, intake and prioritization, resource and capacity management, governance and assurance, method and tooling, and benefits tracking. Every PMO role touches most of these, but the level determines the authority. An analyst produces and validates, a manager runs the process and the team, and a director owns the mandate and the executive relationship.
What is a PMO job spec?
A job spec is the same document as a job description, and the terms are used interchangeably in most US hiring processes. Some organizations distinguish them: the job description covers duties and accountabilities, while the person specification covers the experience, skills, and attributes required. If your process separates them, keep the duties in one and the requirements in the other so neither becomes a wall of text.
What does a PMO director do?
A PMO director owns the office's mandate and its relationship with the executive team. Day to day that means chairing or preparing the portfolio governance forum, deciding the operating model and standards, owning the PMO budget and headcount, arbitrating capacity conflicts between function heads, and answering for whether the portfolio delivered the outcomes it was funded to deliver. The role is judged on decision quality, not on report volume.
What qualifications do you need for a PMO role?
Most US PMO roles ask for a bachelor's degree and relevant project or portfolio experience, with the PMP commonly listed as preferred rather than required. For analyst roles, demonstrable skill with reporting tools and data validation matters more than a certification. For director roles, evidence of running governance at scale and of holding executive relationships outweighs any credential, though PMP or PfMP is common at that level.
Is a PMO job description the same as a roles and responsibilities matrix?
No. A job description is written for one seat and is intended to be posted externally, so it covers purpose, duties, decision rights, requirements, and reporting line. A responsibilities matrix is an internal design artifact that shows how work is divided across the whole office and prevents two people owning the same thing. Build the matrix first, then cut the job description out of it.
What should an IT PMO job description include?
An IT PMO job description includes everything a general PMO role covers plus the technology-specific work: managing dependencies between systems and releases, coordinating with change and release management, tracking application and infrastructure spend, and reporting on a portfolio where much of the demand is run-the-business rather than change. Name the platforms and the delivery model, because IT PMO candidates screen hard on both.
Who does a PMO job description report to?
It depends on the office's mandate. Analyst and coordinator roles report to the PMO manager. A PMO manager typically reports to a PMO director or a delivery executive. A PMO director reports to whoever owns delivery across the organization, most often the COO, CIO, or a transformation lead. A PMO reporting into a single function will inevitably be treated as that function's PMO, so the reporting line belongs in the ad.
Before you post it
Read the draft as a candidate who is currently employed and reasonably happy. Does it say what they would own, what they could change, and who they would work with? If it reads as a list of things that need doing rather than a job somebody would want, rewrite the purpose line and cut half the duties. And check the JD against what the office actually does, described in PMO functions, so you are not hiring for a version of the PMO that does not exist yet. If the role is portfolio-facing rather than office-facing, the distinction is worth reading in project portfolio manager, and the wider definition sits in what is a PMO.