How to Hire a Technology Project Manager Who Can Actually Deliver

The short answer: Match the candidate’s delivery history to your specific programme stage, technical dependencies and stakeholder environment. Methodology qualifications can be useful, but evidence of managing risk and decisions matters more.

A project manager supporting a relatively stable system rollout has a different challenge from someone recovering an ERP programme that has missed milestones. Hiring succeeds when those distinctions appear in the role brief and interview.

Define the delivery context

Set out the current stage, budget governance, sponsor, team structure, vendors, risks and major dependencies. Clarify whether you need a project manager, programme manager, delivery manager or PMO specialist. An undefined brief can attract impressive candidates who are wrong for the work.

Interview for decisions under pressure

Ask for a project that was off track. What was the original plan, which signals suggested trouble and what did the candidate do? Probe how they escalated, reset the delivery plan, managed supplier commitments and communicated with executives.

Strong answers distinguish the individual’s actions from the broader team’s achievements and explain what changed as a result.

Look at technical literacy and commercial judgment

The project manager does not need to perform every technical task. They do need to understand enough about architecture, data, testing, environments and cutover to recognise dependencies and ask informed questions.

For vendor-heavy programmes, test contractual awareness, acceptance criteria and governance. Do not assume PRINCE2, PMP or Agile terminology is evidence of successful delivery.

Decide the engagement model

A defined recovery or implementation phase may suit a carefully scoped engagement. Long-term programme ownership might suit an ongoing appointment. A fixed-term employee is not the same as an independent contractor; follow New Zealand rules and obtain advice where classification is unclear.

Interview questions worth using

1. What did you do when a supplier’s delay threatened the critical path?
2. How did you discover a programme reported as green was at risk?
3. Which decisions did you escalate and which did you own?
4. What would your sponsor say you improved?

Need technology delivery leadership? Discuss the programme and the outcomes you need with ANZ Talent Hub: https://www.anztalenthub.com/contact

Related ANZ Talent Hub support

Explore the relevant ANZ Talent Hub service or contact our Auckland team.