Project manager interviews are won and lost on the failure question. Anyone can narrate a project that went well; panels are looking for the candidate who can describe one that went badly, say what they missed, and show what they changed — without quietly making it someone else's fault.
Roles across Ireland and the UK span construction, IT, financial services and the public sector, and the methodology expected varies with it. Certification is often listed, but panels usually spend more time on stakeholder handling and recovery than on process vocabulary.
For each one: what the interviewer is testing, and what a strong answer contains. Two things no page can give you — your own examples, and whether your answer holds up when they ask for one. That part only comes from saying it out loud.
Why they ask it
The most informative question on the panel. Evasion here outweighs a strong answer anywhere else.
What a strong answer contains
Names a real failure and owns a decision within it. Explains what the early warning signs were, why they were missed, what was done to recover, and what specifically changed in how they run projects since. Avoids blaming stakeholders or the team.
Why they ask it
Scope creep is the most common cause of project failure and it is a relationship problem before it is a process one.
What a strong answer contains
Makes the trade-off visible rather than refusing — what the change costs in time, budget or other scope — and routes it through change control so the decision is the sponsor's and it is documented. Distinguishes a genuine requirement discovered late from indecision.
Why they ask it
Tests candour and timing. Late disclosure is the failure mode panels have all lived through.
What a strong answer contains
Raises it as soon as the slip is credible rather than waiting for certainty, arrives with options and their consequences rather than only a problem, and is specific about the new forecast and its confidence. Never a surprise at the deadline.
Why they ask it
Most project authority is influence rather than line management, and that catches out managers used to hierarchy.
What a strong answer contains
Builds the relationship early, is clear about what is needed and by when, makes the work visible so priorities can be negotiated with their actual line manager, and escalates through the sponsor rather than confronting. Focuses on making it easy to help.
Why they ask it
Tests whether you have a framework or default to whoever pushes hardest.
What a strong answer contains
Prioritises by dependency, risk and value to the project's objective rather than by requester seniority, makes the reasoning explicit, and gets the sponsor to arbitrate genuine conflicts. Says clearly what will be dropped or delayed rather than implying everything fits.
Why they ask it
Separates managers who report status from those who manage it.
What a strong answer contains
Concrete artefacts appropriate to the setting, honest reporting including bad news, and reporting pitched at what the audience needs to decide. Mentions leading indicators rather than only reporting what has already happened.
Why they ask it
The difference between a maintained register and an actual practice.
What a strong answer contains
Identifies risks with the team rather than alone, assesses likelihood and impact, assigns owners and mitigations, and revisits regularly rather than at kickoff only. Gives an example of a risk that materialised and how the mitigation held or failed.
Everyone walking into that room has read a page like this one. What separates them is whether the answer survives “can you give me an example?” — and that is not something you can read your way into. Matilda runs a voice mock interview built from your own CV and the exact job description, and follows up when an answer is thin. Hear a real exchange before you decide anything.
Full mock interview with Matilda
€39.99one-off
Pay once. No subscription, no account, nothing to cancel.
Free question sets are also available at free interview questions.