Role guide and interview toolkit

Project Manager / PMO

What the work looks like, the contexts behind the title, what each level means and the training that helps, then how interviews run and how to prepare for each step.

Planning·Budget·Risks·Reporting·PMP·PRINCE2
The role in practice

What a project manager or PMO actually does

A manager who makes sure IT projects are delivered on scope, on time and on budget, with clear plans, risks and reporting.

The work

A project manager plans and runs IT projects: the scope, the planning, the budget, the risks and the reporting to the people who sponsor the project. They coordinate business teams, technical teams and vendors until the project is delivered.

A PMO, or project management office, supports several projects at once. PMO roles set the standards, follow the budget and the planning across projects and prepare the reporting for leadership.

Depending on the company, the work follows classic methods such as PMP or PRINCE2, Agile methods such as SAFe, or a mix of both.

A typical week
  • Updating the planning and the budget
  • A risk review with the project team
  • A steering committee with the sponsors
  • Following up with vendors or technical teams
  • Preparing the reporting for leadership
Often confused with
Product OwnerOwns the backlog of a product and works with the team sprint after sprint.
ERP Program ManagerRuns large ERP programs with several projects and integrators.
Scrum MasterHelps a team apply Scrum, with less ownership of budget and planning.
Business AnalystTurns business needs into detailed requirements and user stories.
Contexts and tools

The same title, very different ways of working

Most project management searches are defined first by the way the company runs its projects, then by the ground every project manager shares.

Classic projectsMethodsPMP · PRINCE2Typical workPlanning · Budget
Agile programsMethodsSAFe · ScrumTypical workRelease plans · Dependencies
PMOMethodsPortfolio · GovernanceTypical workReporting · Standards
PlanningMS Project, Jira
ReportingPower BI
RisksRisk registers
BudgetCosts, forecasts
StakeholdersSponsors, vendors
Levels

What each level means in practice

Titles vary from one company to the next. What changes from one level to the next is the scope you own and the decisions you take.

01Junior
  • Supports a project manager on planning and reporting
  • Learns the methods, the tools and the teams
  • Prepares documents and meetings with review
02Project Manager
  • Runs a project on their own
  • Owns the planning, the budget and the risks
  • Reports to the sponsors
03Senior
  • Runs large or several projects
  • Manages vendors and difficult stakeholders
  • Coaches other project managers
04Program Director
  • Leads a portfolio or a PMO
  • Sets the standards and the governance
  • Reports to leadership on many projects
Education and certifications

The paths into the role, and what really counts

Project management is a role where certifications are often asked. Companies still look first at projects you delivered on scope, on time and on budget.

Common paths
  • Engineering school or master's in ITA common path in France, often expected by large companies.
  • Business schoolA common path for project managers on business and transformation projects.
  • Business analysis or consulting firstMany project managers start as business analysts or consultants.
  • Technical roles firstDevelopers and engineers who like coordination also move into the role.
Certifications
PMPOften valuedThe project management certification from PMI, often listed in job ads.
PRINCE2Often valuedA project management method and certification, common in Europe.
PMI-ACP or SAFeOften valuedAgile certifications, useful for Agile programs.

Our view: for this role, certifications open doors, and a project you delivered and can walk through counts even more.

Your interview with us

A conversation with a senior tech recruiter

Your first interview is with one of our senior tech recruiters, who knows the role, the methods and the levels in this guide. The conversation covers your own work through real examples, and the case studies come later, with the company. Before the call, we send you the six themes we will cover so you can prepare your examples.

The six themes we share before the call
  1. What you owned yourselfThe projects or programs you were responsible for, and your own part in the team's work.
  2. Your environment and its constraintsScope, budget, deadlines, vendors or the politics of the company: what shaped your technical choices.
  3. The decisions you madeHow you planned, which risks you handled first and how you made trade‑offs, the options you compared and the reasons for your choice.
  4. The impact of your workWhat changed thanks to your work, with numbers when you have them: on time and on budget delivery, savings, adoption or risks avoided.
  5. How you work with other teamsYour work with sponsors, business teams, technical teams and vendors, and how you settle a disagreement.
  6. What you want nextThe kind of projects, size and scope you are looking for in your next role.
What we look at
  • Projects delivered on scope and time
  • Stakeholder management
  • Risk handling

The same ground for every candidate. For a given role, every candidate answers the same final questions, built with the hiring manager around what the role really needs.

Ready for the next steps. After our call, we tell you how the company runs its interviews, who you will meet at each step and what each step is meant to assess.

Interviews with the company

What the company will assess, step by step

Each company runs its own process, and we walk you through its steps before you start. Project management processes often combine the steps below, and the depth expected at each step grows with your level.

The steps you will often meet
  1. A case studyA project in trouble to analyse, with the planning, the risks and the actions you would take.
  2. A deep dive on a past projectOne project you ran, discussed in depth: the scope, the budget, the risks and the result.
  3. A stakeholder role playA difficult meeting to run, such as a delay to announce to a sponsor.
  4. Meeting the manager and the teamHow you work, how you take decisions with others and what the team expects in your first months.
What changes with your level
  • Project ManagerYou structure the plan clearly, list the main risks and explain your actions in simple words.
  • SeniorYou lead the case, make trade‑offs between scope, time and cost, and point out risks before you are asked.
  • Program DirectorYou run most of the interview as a peer, think about the whole portfolio and connect it to the goals of the company.
Your interview toolkit

How to prepare as a project manager

Practical advice for each step of a project management process, from the way you introduce yourself to the questions you ask at the end of each interview.

01Introduce yourself in two minutes

Start with the projects you worked on, their context and your part in them. Mention your main methods and tools in one sentence, then close with what you want next.

02Prepare two projects

For each one, prepare the context, the constraints, your decision, the options you set aside, the result and what you would change today. Say "we" for the team and "I" for your own part.

03Know your numbers

Prepare the budget, the team size, the length and the result of your main projects, with the gaps and how you closed them.

04Prepare a project in trouble

Interviewers often ask about a project that went wrong. Prepare what happened, what you did and what you learned.

05Show how you handle sponsors

Prepare one example of bad news you gave to a sponsor and how you kept their trust.

06Check the rules on AI tools

Rules on AI tools differ from one company to the next, especially for take-home cases. Ask before each step, and when they are allowed, explain what you asked the tool and how you checked its output.

Questions you will often hear
  • Walk us through a project you delivered, from the start to the end.
  • Your project is three months late. What do you do?
  • How do you handle a stakeholder who keeps changing the scope?
  • How do you choose between a classic and an Agile approach?
Questions worth asking them
  • Which projects would I run first?
  • Which methods and tools does the company use?
  • Who are the sponsors, and how often do they meet?
  • How are vendors chosen and managed?
  • How is the success of a project measured?
  • How does the team use AI tools in its daily work?
Where the role leads

Where project managers come from, and where they go

The roles people most often hold before this one, and the ones they most often move to.

Some project managers also become heads of PMO.