Project Manager: Role Profile, KPIs and Interview Questions
Find project manager responsibilities, key performance indicators (KPIs) and practical hiring materials here. Use them to hire someone who turns agreed plans into accepted results.
Job profiles, hiring, onboarding and reviews are in PapaHR. Free for up to 25 employees.
- Take the profile below or build your own with the builder.
- In PapaHR the profile turns into a job ad, an onboarding plan and probation goals.
- After 90 days, review the person against the same KPIs and competencies.
Job profile
Why the role exists
Deliver agreed project outcomes within approved timelines and budgets.
Result in a year
Completed projects have formal acceptance and an owner for ongoing support; managers see schedule, cost and scope changes early.
Place in the structure
- Reports toBusiness owner or Head of Operations.
- Direct reportsMay have no direct reports; coordinates the project team.
- Works withProject sponsor or client: agrees outcomes, budget and priorities, Department managers: allocate people and confirm availability, Team members: estimate tasks and deliver the work, Suppliers: deliver agreed outputs, Accountant: confirms costs and upcoming payments, Operational owner: accepts deliverables and takes over ongoing support
Key result areas
- Project milestones are accepted on schedule — On-time milestone acceptanceSample target: at least 90% of milestones accepted by their planned dates.
- Project costs stay within the approved budget — Cost against budgetSample target: no more than 100% of budgeted costs for completed work.
- Deliverables meet acceptance criteria — First-time acceptanceSample target: at least 90% of deliverables accepted on first submission.
- Additional work starts after changes are approved — Changes approved before work startsSample target: 100% of changes approved before additional work starts.
- Closed projects have a complete operational handover — Complete project handoversSample target: 100% of closed projects handed over against the agreed checklist.
Requirements
Experience: Experience managing a project from initial agreement through acceptance.
Formal: Willingness to share an anonymised project plan and explain decisions.
Should know
- Project stages and scope definition
- Time estimates, task dependencies and schedule contingency
- Budget components, commitments and cost forecasting
- Project risk and change management
- Acceptance criteria and handover procedures
Should be able to
- Build plans with dates, deliverables and owners
- Review team estimates and account for availability
- Update completion forecasts using actual progress
- Explain the impact of requirement changes to the sponsor
- Run short meetings with decisions and action owners
- Use budget spreadsheets and task management tools
Competencies at three levels
Project planning
Makes deadlines realistic and shows which delays affect the whole project.
- Breaks clear tasks into steps and agrees dates with the team.basic
- Connects milestones, capacity and dependencies; updates timelines when progress changes.solid
- Compares delivery options and justifies contingency for uncertain work.strong
Team coordination
Secures specialist time when people also have ongoing operational responsibilities.
- Assigns task owners and checks they understand the work.basic
- Agrees availability and resolves conflicting priorities with team members' managers.solid
- Redistributes work across teams while protecting key project commitments.strong
Risk management
Prepares responses before problems delay delivery or increase costs.
- Records obvious risks and reports emerging blockers.basic
- Assesses risk impact, assigns owners and checks mitigation actions.solid
- Prepares fallback plans and activates them at agreed warning signs.strong
Budget control
Reveals likely overspending before the final invoice arrives.
- Checks invoices against the budget and flags variances.basic
- Tracks commitments and regularly updates the total cost forecast.solid
- Compares solution costs alongside effects on timelines and quality.strong
Stakeholder communication
Secures timely decisions and a shared understanding of the outcome.
- Records meeting decisions and sends clear project updates.basic
- Raises difficult issues early, offers options and requests specific decisions.solid
- Resolves conflicting expectations and secures decisions when interests clash.strong
Scope and acceptance management
Prevents endless additions and disputes about whether work is complete.
- Records scope and checks deliverables against an existing requirements list.basic
- Agrees acceptance criteria and the impact of new requirements before work starts.solid
- Helps the sponsor reduce scope while preserving the required business outcome.strong
Build the profile for your company
Tick what this person does at your company. On the right is the ready profile: copy it or open it in PapaHR.
Deliver agreed project outcomes within approved timelines and budgets.
Duties- Agree project objectives, scope and acceptance criteria
- Break projects into milestones, tasks and verifiable deliverables
- Estimate timelines and costs with team members
- Agree team availability with department managers
- Track task dependencies and deviations from the plan
- Maintain a risk register with owners and mitigation actions
- Monitor costs, commitments and budget forecasts
- Agree changes to scope, timelines and costs
- Report progress, blockers and required decisions to the sponsor
- Organise acceptance, handover and a review of the completed project
- Compare supplier proposals by price, timeline and scope
- Plan office moves, implementations or new process launches
- Coordinate projects involving several external suppliers
- Arrange employee training before launch
- Build plan and report templates for recurring projects
- Track time spent on project tasks
- Check business outcomes after project handover
Project Manager KPIs
- On-time milestone acceptance — Milestones accepted on time / milestones due this period × 100%. Mistake: Moving planned dates after deadlines pass to hide delays.weight 30% · month
- Cost against budget — Actual costs / budgeted costs for completed work × 100%. Mistake: Excluding completed work because its invoices remain unpaid.weight 25% · month
- First-time acceptance — Deliverables accepted first time / deliverables first submitted × 100%. Mistake: Recording acceptance without confirmation from the sponsor or client.weight 20% · month
- Changes approved before work starts — Changes approved beforehand / all changes started × 100%. Mistake: Seeking retrospective approval after additional work is complete.weight 15% · month
- Complete project handovers — Projects fully handed over / all closed projects × 100%. Mistake: Closing projects without a support owner or transfer of access.weight 10% · quarter
Work out the KPI bonus
Enter how much of each target was met, in percent, and the bonus at 100%. You can change the weights.
The weights are an example. They should add up to 100%.
Interview questions
Run the interview and get the result
Score each answer from 1 to 5 and the total is worked out by competency. Keep this page open on your phone during the interview.
Project planning
✓ Listen for: Team estimates, dependencies, contingency and actual delivery against the plan.
⚑ Red flag: Set a date without checking scope or team availability.
✓ Listen for: Recalculated dependent dates, recovery options and an agreed revised forecast.
⚑ Red flag: Moved one task without checking its effect on others.
Team coordination
✓ Listen for: Agreed capacity, involvement of the specialist's manager and follow-up on commitments.
⚑ Red flag: Queued tasks without confirming the specialist's availability.
✓ Listen for: Specific cause, support or reassignment, revised deadline and outcome.
⚑ Red flag: Only sent reminders or blamed the person publicly.
Risk management
✓ Listen for: Early warning, impact assessment, named owner and completed mitigation actions.
⚑ Red flag: Recorded the risk but assigned nobody to act.
✓ Listen for: Impact assessment, fallback option, agreed consequences and final outcome.
⚑ Red flag: Waited for the supplier until the delivery deadline.
Budget control
✓ Listen for: Forecast to completion, causes of variance and an agreed decision with results.
⚑ Red flag: Discovered the overrun only after all invoices were paid.
✓ Listen for: Total cost, rework, timelines and the chosen option's effect on delivery.
⚑ Red flag: Compared quoted prices without checking the included scope.
Stakeholder communication
✓ Listen for: Timely communication, facts, options and a recorded decision.
⚑ Red flag: Hid the delay until the sponsor asked.
✓ Listen for: Clear priorities, an authorised decision-maker and one agreed set of requirements.
⚑ Red flag: Passed both requirements to the team without resolving the conflict.
Scope and acceptance management
✓ Listen for: Time and cost assessed before work began; a confirmed plan change.
⚑ Red flag: Promised extra work without assessing or agreeing its consequences.
✓ Listen for: Verifiable criteria, defects separated from new requests and confirmed acceptance.
⚑ Red flag: Accepted endless revisions without defining completion.
Weak:
Test task
Replan a website launch after a change request · 2 hours
Practice scenario: a company is launching a five-page website with an enquiry form in six weeks, with a $6,000 budget. All figures are assumptions for this exercise. The designer is available 16 hours weekly, the developer 24 and the tester 8; propose task estimates and state your assumptions. At the end of week two, designs are approved, $1,800 has been spent and development has not started. The sponsor requests online payments; the supplier estimates $1,500 and one additional week of development. The launch date matters because advertising is already booked. Prepare a remaining-work plan with dependencies and owners, a cost forecast, three main risks and acceptance criteria. Compare two responses to the new request and write a short message recommending a decision to the sponsor. A spreadsheet and text are enough; do not build the website.
How to assess it
- Plan accounts for team availability and task sequence
- Estimates and assumptions are separate from the supplied facts
- Forecast includes money spent and remaining costs
- Options show effects on schedule, budget and scope
- Risks have owners and specific mitigation actions
- Acceptance criteria are verifiable; the message requests a clear decision
Ready job ad
Project Manager at [company name]
At [company name], you will manage [project types] from initial agreement through acceptance. You will help the team meet commitments and the sponsor make timely decisions.
What you will do
- Agree outcomes, project scope and acceptance criteria
- Plan milestones, timelines and team capacity
- Monitor spending and forecast final costs
- Remove blockers and prepare risk responses
- Secure approval for additional work before it starts
- Organise project acceptance and operational handover
What we need
- Completed projects with a clear personal contribution
- Ability to link task schedules to team availability
- Budget tracking and early identification of likely overspending
- Ability to reach agreements with sponsors and team members
- Clear records of decisions, changes and completion criteria
What we offer
- Pay: [salary] US dollars, [bonus terms]
- Working hours: [schedule]
- Location: [city], [office or remote]
- Projects: [types and number managed concurrently]
- Authority: [decisions you can make independently]
- Support: [team, mentor and available resources]
In PapaHR this text becomes a job opening with a careers page and a candidate pipeline.
90-day onboarding plan
Before day one
- Send starting arrangements and team contact detailsHR
- Select the first project and appoint a mentorManager
- Prepare access to tasks, documents and budgetsIT
Day one
- Explain authority and the change approval processManager
- Introduce the sponsor, team and operational ownerMentor
- Review the first project's objective and record open questionsNew hire
First week
- Review the project plan, budget, commitments and change historyNew hire
- Confirm team availability and main task dependenciesNew hire
- Explain acceptance and handover procedures for completed projectsMentor
- Agree probation period goals and the project update formatManager
30 days
- Agree the first project's current plan, budget and acceptance criteriaNew hire
- Assign risk owners and deadlines for mitigation actionsNew hire
- Check forecast realism and resource availabilityManager
60 days
- Obtain acceptance of the first planned milestoneNew hire
- Update timeline and cost forecasts using actual resultsNew hire
- Review a difficult negotiation and provide feedbackMentor
90 days
- Present milestone results and reasons for variancesNew hire
- Hand accepted deliverables, documentation and access to the operational ownerNew hire
- Review probation period goals and agree the next projectsManager
Probation period goals
- Agree a workable first project plan by day 30.Sponsor confirms scope, dates, budget and acceptance criteria; every task has an owner.
- Establish regular schedule, cost and risk forecasts.Agreed weekly updates arrive on time; each variance includes its cause, action and owner.
- Secure acceptance of an agreed milestone by day 60.Sponsor confirms the result against criteria; outstanding issues have owners and deadlines.
- Hand over the accepted milestone deliverables by day 90.Operational owner confirms documentation, access and support arrangements; open questions have named owners.
Career path
Tracks tasks, minutes and updates under a project manager's guidance.
To move up: Independently take a small project from planning to confirmed acceptance.
Owns project delivery, timelines, budget and change approval.
To move up: Deliver projects involving several teams and manage significant risks.
Leads complex, connected projects and supports less experienced managers.
To move up: Demonstrate prioritisation and resource allocation across projects.
Owns the project portfolio, shared resources and manager development.
To move up: Expand responsibility for business outcomes and investment decisions.
Questions for a 1:1 meeting
- Which milestone currently determines the project completion date?
- Where does confirmed team availability differ from the plan?
- How has the total cost forecast changed, and why?
- Which sponsor decision do you need this week?
- What additional work has the team started without approval?
- Which risk needs my intervention, and by when?
- Which criteria will determine acceptance of the next deliverable?
- What prevents handover to the people who will use the result?
Mistakes in hiring and managing
- Hiring for task tool knowledge without evidence of completed projects.
Better: Discuss the candidate's decisions and accepted outcome on a specific project. - Demanding a deadline without allocating specialist time.
Better: Confirm team capacity with department managers before approving the plan. - Assessing the manager solely on completed reports.
Better: Review accepted deliverables, cost forecasts and timely decisions. - Adding requirements while keeping the original deadline and budget.
Better: Agree scope, cost or date changes before starting the work. - Treating a demonstration as project completion.
Better: Confirm acceptance and hand over documentation, access and support ownership.
What a bad hire costs: Project Manager
The same calculation as in PapaHR «HR in money»: the cost of hiring plus the salary for the months the new hire worked at half capacity.
In the first months a new hire delivers about half the result, so the company pays the other half of the salary for learning. In PapaHR the calculation uses your real leavers.
Questions and answers
What does a project manager do?
Organises work so the team delivers an agreed outcome on time and within budget. This involves planning tasks, securing resources, managing risks and arranging acceptance.
How is a project manager different from a product manager?
A product manager defines the value a product should create for users and the business. A project manager organises a specific project with agreed scope, timelines and budget. Small companies can combine the roles if both responsibilities are clearly assigned.
Does a project manager need coding skills?
It depends on the projects: an office move requires no coding. Software projects require an understanding of delivery stages, dependencies and specialists' explanations. Assess the necessary technical depth using tasks from the intended project.
Which KPIs should a project manager have?
Measure on-time milestone acceptance, costs against budget and first-time acceptance. Include change approval and complete handovers. If no relevant events occur during a period, leave that metric uncalculated and use a weight redistribution rule agreed beforehand.
How do you assess a project manager in an interview?
Discuss a completed project: the original brief, the candidate's actions and the accepted outcome. Ask them to explain a delay, budget overrun or scope dispute. A short practice exercise shows whether they can connect the plan, resources and budget.
Hire, onboard and review in one system
PapaHR is free for up to 25 employees: job profiles, openings, onboarding, goals, 1:1 meetings and reviews.