Project Manager Job Description

Great project managers have a calm authority that emerges from preparation and transparency rather than authority by title. Look for candidates who manage risks before they become issues — ask them to walk you through how they run a risk register and what they do when a red risk materialises. Equally important is stakeholder management under pressure: what do they do when an executive sponsor changes direction mid-project? Strong candidates will give you structured answers that reveal a methodology, not just a story.

Candidates with domain expertise in your industry are easier to onboard and add value faster than pure methodology specialists who need extensive context-setting. Business analysts who have grown into project delivery, consultants who have led client workstreams, and operations professionals who have managed change programmes are all strong adjacent pipelines. PMO analyst roles are a good feeder for earlier-career PMs. Professional bodies such as PMI and APM publish job boards and have active membership communities where practitioners post availability.

Ask them to walk through a project that went off-track and what they did to recover it — this reveals problem-solving and communication under pressure more than any success story. Follow with 'How do you handle a key stakeholder who consistently misses commitments that are on the critical path?' Then test methodology thinking: 'How do you decide whether to run a project using Agile or waterfall?' Finish with 'Walk me through how you manage the budget on a project and what you do when you forecast an overrun.' You are testing structure, judgement, and commercial awareness simultaneously.

A junior Project Manager runs a single, well-defined project, keeping the plan, status, and stand-ups on track under guidance. A senior PM handles larger, ambiguous, or multi-stakeholder projects where scope shifts, dependencies tangle, and politics complicate delivery. Seniors are trusted to make judgment calls, manage difficult stakeholders, negotiate scope and trade-offs, and recover a project that is drifting off course. They also mentor other PMs and improve how the organisation delivers, not just their own work. When hiring, match the level to the complexity: a capable junior thrown into a fraught cross-departmental programme without support will usually struggle with the stakeholder management and risk judgment that seniority brings.

Design the loop to test delivery under pressure, not just methodology recall. Start with a behavioural screen on a project that went wrong and how they responded, which reveals honesty and problem-solving far better than a success story. Add a scenario exercise: hand them a project slipping on scope, budget, or timeline and watch how they prioritise, communicate, and decide what to escalate. Include a stakeholder round, since much of the job is managing people who do not report to them, and check how they handle a difficult sponsor or a resistant team. A methodology conversation confirms they can flex between agile, waterfall, or hybrid rather than dogmatically applying one. Score against outcomes and communication clarity, not certification alone.