All jobs / Project / delivery manager
Leadership interview questions
Leadership questions a Project / delivery manager can be asked, from first job to senior. Open one to see the strongest answer and why it works.
A developer has been stuck on access for two days and has not said so. What do you do first?
The strongest answer: I make the stuck visible on the board and I take the access as my work today — I do not praise silent struggle
Why it works: Exactly. An impediment that stays private is a delivery defect. Make it visible and move it.
- Make the stuck visible.
- Take the impediment as work.
- Do not reward silence.
- Do not wait for Friday.
The team looks at you to name who takes the next ticket. Strongest move?
The strongest answer: I ask who has capacity and who knows the slice — I do not assign as if I own the people
Why it works: Exactly. Facilitate the pull. Assigning as the boss is a different job.
- Ask capacity and knowledge.
- Let the team pull.
- Do not assign to “grow” someone.
- Do not become the backlog.
Two people start a design argument in the daily. What do you do?
The strongest answer: I park it with a time and names after the daily — I do not let the board wait on a sidebar
Why it works: Exactly. Park with an owner and a time. The daily is not a design room.
- Park with names and a time.
- Protect the daily.
- Do not mute without a follow-up.
- Do not design in the standup.
Half the team is on a video call and two people cannot be heard. What do you fix first?
The strongest answer: That every voice can enter — a spoken round, a typed lane, or a slower pace — I do not run a room only the loud office can use
Why it works: Exactly. Access to speak is the first facilitation job. Theatre is not inclusion.
- Every voice can enter.
- Offer a typed lane if audio fails.
- Do not equate cameras with participation.
- Do not exile remote people to the recording.
A decision has come up in three meetings and is still not made; each time it is “parked for more information.”
What do you do?
The strongest answer: I name the decision, get one person agreed as the decider, write down the options and what information would actually change the choice, and set a date to decide with what we know
Why it works: Exactly — most stalls are missing an owner and a deadline, not missing information; naming both usually ends it.
- Owner, options, deadline.
- Name the decider.
- Write what would change the choice.
- Decide by a date with what you know.
The daily has gone quiet — people say “same” and look down. How do you facilitate?
The strongest answer: I change the prompt: walk the board right-to-left, ask what is stuck, and I do not fill the silence with my own status
Why it works: Exactly. Change the shape. Walk the work. Do not become the narrator.
- Walk the board, stuck first.
- Change the prompt.
- Do not narrate for them.
- Do not replace the talk with a dashboard only.
The same access ticket has blocked three sprints. This is no longer a personal stuck. What do you do?
The strongest answer: I treat it as an organisational impediment: I show the wait cost on the board and I take it to the person who can change the policy — I do not only coach the developer to “follow up again”
Why it works: Exactly. Repeat waits are system problems. Show the cost. Escalate to the policy owner.
- Name it as a system wait.
- Show the cost on the board.
- Take it to the policy owner.
- Do not only coach “follow up.”
Two seniors are talking over each other in planning and the rest of the team has gone silent. What do you do?
The strongest answer: I stop the cross-talk, I give each a timed turn, and I pull a quieter voice in before we decide — I do not pick a winner to save the hour
Why it works: Exactly. Structure the talk. Hear the quiet. Facilitators do not award the work.
- Stop the cross-talk.
- Timed turns.
- Invite a quieter voice.
- Do not decide as the facilitator.
You keep being the person who unblocks every access, vendor, and environment issue. What is the risk?
The strongest answer: The team cannot move when I am away, and I am hiding a system problem — I teach the path and I change the policy, I do not collect heroics
Why it works: Exactly. Heroics hide the system. Teach the path; change the policy.
- Teach the unblock path.
- Change the repeating policy.
- Do not collect heroics.
- Do not replace yourself with another hero.
A retro turns into who slipped. How do you recover the room?
The strongest answer: I stop the blame, I move to the system (WIP, waits, unclear ready), and I leave with one change — I do not finish the hunt
Why it works: Exactly. Blame is not a retro. System, then one change.
- Stop the hunt.
- Talk about the system.
- One owned change.
- Do not cancel retros as punishment.
You must facilitate a two-hour planning with twelve people, six remote. What do you design first?
The strongest answer: How every person will contribute in writing and in speech, who holds the board, and the decision you need by the end — I do not “share my screen and hope”
Why it works: Exactly. Remote facilitation is designed: lanes, board, decision. Screen-share hope is not a plan.
- Design written and spoken lanes.
- Name the decision and the board owner.
- Do not rely on one room mic.
- Do not replace the workshop with a deck.
Steerco wants a demo and a decision but spends the hour on slides. How do you facilitate?
The strongest answer: I put the decision and the range on page one, I time-box the demo, and I end on the ask — I do not let the slide tour eat the decision
Why it works: Exactly. Decision first. Demo as evidence. End on the ask.
- Decision and range on page one.
- Time-box the demo.
- End on the ask.
- Do not decide later in email by default.
A new scrum master copies your stand-up word for word and then looks at you to run it. What do you do?
The strongest answer: I coach from the side: they hold the room, I give notes after, I do not take the marker back because it is faster
Why it works: Exactly. They hold the room. Notes after. Taking the marker trains helplessness.
- They hold the room.
- Notes after, not during.
- Do not take the marker back.
- Do not abandon them for a quarter.
A manager wants to sit in every retro “to stay close to the team.” What do you do?
The strongest answer: I protect the room: the team chooses the guest, we have a path to speak without them, and I do not sell the retro as a status hour
Why it works: Exactly. Safety is the condition for a change. A standing manager seat is how people go quiet.
- The team chooses guests.
- Keep a path to speak without them.
- Do not turn retro into status.
- Do not run a polite shadow retro.
Every squad is blocked by the same change-advisory wait. Local SMs keep “following up.” What is your job?
The strongest answer: I treat it as one systemic impediment: I show the wait across teams and I change the policy with the owner — I do not fund twenty follow-up heroes
Why it works: Exactly. Same wait, one policy change. Hero follow-ups are the smell.
- One impediment, one policy owner.
- Show the wait across teams.
- Do not fund follow-up heroes.
- Do not skip the control in silence.
The company is remote-first and leadership still designs rooms for the HQ table. What do you change at the org level?
The strongest answer: Default artifacts and decisions that work in writing first, overlap hours for the few talks that need voices, and I do not treat HQ as the real room
Why it works: Exactly. Remote-first is designed defaults, not a camera policy. HQ-as-real is the defect.
- Writing-first artifacts and decisions.
- Overlap only where voices are needed.
- Do not make HQ the real room.
- Do not tax people with travel-as-planning.
A planning room has a VP who talks first and a team that then agrees. How do you facilitate?
The strongest answer: I take written input first, I ask the VP to speak last, and I make dissent safe to put on the board — I do not call silence alignment
Why it works: Exactly. Power rooms need structure: write first, seniority last, dissent visible. Silence is not agreement.
- Written input first.
- Senior voices last.
- Put dissent on the board.
- Do not call silence alignment.
You can change team boundaries. Handoffs dominate every forecast. What do you optimise for?
The strongest answer: Fewer joins on the money path — teams that can finish a user slice — I do not optimise for utilisation of every specialist
Why it works: Exactly. Org design for flow is fewer joins. Utilisation of specialists is how you add waits.
- Design teams that can finish a slice.
- Cut joins on the money path.
- Do not optimise specialist utilisation.
- Do not add an approval matrix.
Managers are rewarded for starting new initiatives and engineers for tickets closed. WIP explodes. What impediment is this?
The strongest answer: The incentive system — I change what we reward (finishes, outcomes, stopped starts), I do not add a WIP poster on top of the old bonuses
Why it works: Exactly. Incentives that pay for starts will beat a poster. Change the reward.
- Name incentives as the impediment.
- Reward finishes and stopped starts.
- Do not poster over the bonus.
- Do not raise WIP to match the smell.
The product manager and the tech lead of a key team escalate to you almost every week — scope versus technical risk, date versus refactor.
What do you do?
The strongest answer: I settle this case by getting both to name interests and who owns the call, then fix the pattern — agreed decision rights, a forum where they decide together, coaching — rather than becoming the standing tie-breaker
Why it works: Right — a senior fixes the decision system that keeps producing escalations, not just the escalation in front of them.
- Fix the pattern, not the week.
- Agree decision rights.
- Give them a forum.
- Refuse to be the standing tie-breaker.
Three sites must plan together and one site always “agrees after” in their local language. What do you redesign?
The strongest answer: A written decision in a shared artifact before the call ends, plus a facilitation rotation so no site is the audience — I do not treat after-agreement as alignment
Why it works: Exactly. Multi-site is a written close and a rotation. After-agreement is a second meeting you did not admit.
- Close in a shared written artifact.
- Rotate who facilitates.
- Do not accept after-agreement.
- Do not record the HQ table as inclusion.