HireHireInterview Quizzes › Project / Program Manager

Project / Program Manager Interview Questions

Think you're ready? These are the questions that actually decide Project / Program Manager interviews. Warm up on Easy — then face the Hard round, where 95% of candidates crumble. 60 questions across 3 levels, instant score, completely free.

60Questions
3Difficulty levels
95%Fail the hard round
FreeInstant score
Easy
Warm-up · 20 Qs
Medium
Practical · 20 Qs
Hard
Brutal · 20 Qs
⚡ Take the Project / Program Manager quiz — get your score →

The Project / Program Manager interview questions

Below are the real questions, grouped by difficulty. Expand any one to reveal the correct answer and why — or take the timed quiz for a score you can share. Can you clear the Hard round?

Easy round 20 questions

Your project kickoff is next week and the sponsor asks for a timeline. What should you do first?
  • A. Work backward from the sponsor's desired launch date to produce the timeline they want
  • B. Clarify the project's objectives, scope and success criteria before estimating dates ✓
  • C. Reuse the schedule from a similar past project, adjusting the dates to fit
  • D. Have the team give bottom-up task estimates so you can roll them into a date
Correct answer: B. You cannot credibly plan or estimate until the objectives, scope and definition of success are agreed.
A stakeholder emails you a new feature request midway through the project. What is the right response?
  • A. Add it straight to the product backlog to be picked up in a later sprint
  • B. Refuse it outright because the scope was already signed off
  • C. Log it, assess its impact on scope, cost and schedule, and route it through change control ✓
  • D. Approve it yourself since it looks small and ask the team to get started
Correct answer: C. New requests should be captured and assessed for impact through change control, not silently absorbed or reflexively rejected.
What is the most useful purpose of a weekly status report to stakeholders?
  • A. To create an audit trail that protects the PM if the project is later questioned
  • B. To give a clear, honest picture of progress, risks and decisions needed ✓
  • C. To list every task completed in exhaustive detail
  • D. To keep stakeholders confident by emphasising the wins and progress made
Correct answer: B. Good status reporting communicates real progress, surfaces risks and flags where stakeholders must decide or act.
A task on the critical path is running late. Why does this matter more than a late task off the critical path?
  • A. Critical-path tasks have the most dependencies feeding into them
  • B. A slip on the critical path directly pushes out the project end date ✓
  • C. A delay off the critical path can never affect the finish date, however large it is
  • D. The critical path is the chain of highest-cost tasks, so slipping it costs the most
Correct answer: B. By definition the critical path has no slack, so any delay on it moves the whole project's finish date.
You identify a risk that a key vendor may deliver late. What is the best immediate action?
  • A. Wait and see whether the vendor actually slips before reacting
  • B. Log the risk, assess likelihood and impact, and plan a mitigation and contingency ✓
  • C. Immediately escalate to senior leadership to put pressure on the vendor
  • D. Line up a backup vendor now before assessing whether the risk warrants it
Correct answer: B. Risks are managed by documenting, assessing and planning mitigations proactively, not by waiting for them to become issues.
Two team members disagree about the technical approach and it is stalling work. What should the PM do?
  • A. Pick the approach yourself since you are in charge
  • B. Facilitate a focused discussion to surface trade-offs and reach a decision ✓
  • C. Give it a few more days to see if they resolve it themselves
  • D. Escalate the disagreement to the sponsor immediately
Correct answer: B. A PM unblocks by facilitating a structured decision that weighs trade-offs, not by imposing or avoiding the call.
When is the best time to identify risks on a project?
  • A. Only after the first issue actually occurs
  • B. Continuously, starting at planning and revisiting throughout delivery ✓
  • C. Just once, in a single workshop at kickoff
  • D. Only at the very end during the retrospective
Correct answer: B. Risk identification is an ongoing activity because new risks emerge as the project evolves.
A dependency means Team B cannot start until Team A finishes. How should you manage this?
  • A. Assume both teams will sort it out between themselves
  • B. Make the dependency visible, track Team A's finish date and confirm Team B's readiness ✓
  • C. Add buffer to Team B's start date and leave the dependency untracked
  • D. Let Team B start early on assumptions before Team A delivers to save time
Correct answer: B. Dependencies must be made explicit and actively tracked so a slip upstream is caught before it blocks the downstream team.
The sponsor asks 'are we on track?' What is the most professional answer?
  • A. 'Yes, we're on track' since the current sprint is going well
  • B. A clear status backed by facts on scope, schedule and the top risks ✓
  • C. A detailed rundown of every challenge the team is currently working through
  • D. A long list of everything the team did this week
Correct answer: B. Stakeholders need an honest, evidence-based status that names the real risks, not blanket reassurance.
What is the primary value of breaking work into a task breakdown before scheduling?
  • A. It lets you present a more granular, polished plan to stakeholders
  • B. It exposes the real work, dependencies and estimates so the schedule is realistic ✓
  • C. It ensures every task has a named owner assigned before work starts
  • D. It satisfies the methodology's requirement to produce a work breakdown structure
Correct answer: B. Decomposing work reveals the true scope and sequence, which is what makes the resulting schedule credible.
A team member is blocked waiting on access from another department. What should the PM do?
  • A. Log it as a blocker in the tracker and wait for the other team to respond
  • B. Actively chase the other department and remove the blocker for them ✓
  • C. Reassign the task to someone else to avoid the issue
  • D. Mark the task as at-risk and move on
Correct answer: B. Unblocking the team by driving the dependency to resolution is a core PM responsibility.
You are estimating a task and the engineer is unsure. What is the healthiest way to handle the uncertainty?
  • A. Pick the most optimistic number so the plan looks good
  • B. Capture a realistic range and note the uncertainty as a risk to manage ✓
  • C. Demand a single precise number and hold them to it
  • D. Skip the estimate and fill it in later
Correct answer: B. Honest estimation acknowledges uncertainty with a range and tracks it, rather than committing to false precision.
How should you decide the order in which to sequence project tasks?
  • A. By estimated duration, scheduling the shortest tasks first
  • B. By dependencies, priority and resource availability ✓
  • C. By whichever tasks the loudest stakeholder wants first
  • D. By starting with the easiest tasks to build momentum only
Correct answer: B. Sequencing follows the logical dependencies, priorities and who is available to do the work.
A minor risk you logged weeks ago has now started to materialise. What is the best response?
  • A. Enact the contingency plan you prepared and inform stakeholders ✓
  • B. Update the register to mark it closed and handle it informally
  • C. Escalate to leadership to decide what to do next
  • D. Wait to confirm it is fully an issue before acting
Correct answer: A. The point of pre-planned contingencies is to trigger them promptly and communicate as the risk turns into an issue.
What is the purpose of a project kickoff meeting?
  • A. To energise and motivate the team with a launch celebration
  • B. To align the team and stakeholders on goals, scope, roles and how you will work ✓
  • C. To walk the team through the detailed technical design and architecture
  • D. To hand over the finished plan so the team can start executing right away
Correct answer: B. Kickoff exists to create shared understanding of objectives, scope, roles and ways of working before delivery begins.
A stakeholder keeps missing your status updates and then complains they are surprised. What should you fix?
  • A. Send even longer reports so nothing is missed
  • B. Agree the right cadence, channel and level of detail that this stakeholder will actually consume ✓
  • C. Stop reporting to them since they ignore it anyway
  • D. Escalate their behaviour to their manager
Correct answer: B. Effective communication is tailored to how each stakeholder wants to receive information so it is actually absorbed.
The team says a requirement is unclear. What is the best first move?
  • A. Guess the intent and build something so work continues
  • B. Go back to the requester to clarify the intent and acceptance criteria ✓
  • C. Escalate to the sponsor that requirements are bad
  • D. Pick the interpretation that is easiest to build
Correct answer: B. Ambiguous requirements should be clarified with the requester before building to avoid costly rework.
Why maintain a risk register throughout the project?
  • A. Because auditors require the paperwork
  • B. To track identified risks, owners and mitigations so nothing is forgotten ✓
  • C. To produce a governance report the sponsor signs off at each gate
  • D. To capture every conceivable risk in exhaustive detail
Correct answer: B. A risk register keeps risks, their owners and mitigations visible and actively managed rather than lost.
A small scope addition seems harmless. What is the mature way to handle it?
  • A. Add it immediately since it is small
  • B. Assess even small changes for cumulative impact before accepting them ✓
  • C. Reject all changes on principle
  • D. Let the developer decide whether to include it
Correct answer: B. Even small changes accumulate, so they should be assessed for combined impact rather than waved through.
What best defines a successful project outcome?
  • A. The team worked very hard the whole time
  • B. It delivered the agreed value and outcomes for stakeholders within the agreed constraints ✓
  • C. It used every hour of the budget available
  • D. It generated a large volume of documentation
Correct answer: B. Success is measured by delivering the intended outcomes and value within the agreed scope, time and cost, not by effort or output volume.

Medium round 20 questions

Two senior stakeholders each insist their feature is the top priority and both cannot fit in the release. What is the best approach?
  • A. Build whichever stakeholder is more senior to avoid conflict
  • B. Facilitate a prioritisation using shared criteria like value, risk and cost, and get a joint decision ✓
  • C. Split effort evenly so both get half a feature
  • D. Delay the release until both can be fully delivered
Correct answer: B. Competing priorities are resolved by prioritising transparently against shared business criteria rather than by seniority or splitting.
Your timeline is slipping and you are two weeks behind at the midpoint. What is the most responsible first step?
  • A. Quietly ask the team to work weekends to catch up
  • B. Diagnose the root cause of the slippage before choosing a recovery option ✓
  • C. Immediately tell stakeholders the deadline will move
  • D. Cut testing to claw back the two weeks
Correct answer: B. You cannot choose the right recovery lever until you understand why the slippage happened.
A developer tells you privately that the deadline is impossible but the sponsor expects it. What should you do?
  • A. Keep quiet and hope the team pulls it off
  • B. Validate the concern with data and have an honest conversation with the sponsor about options ✓
  • C. Tell the developer to be more positive
  • D. Commit to the date publicly and manage the fallout later
Correct answer: B. A PM must surface credible delivery risk to the sponsor early with evidence, not suppress it and over-commit.
Scope has quietly grown 30% since kickoff through many small 'quick' additions. What went wrong and what do you do now?
  • A. Nothing went wrong; responsiveness to requests is good
  • B. Change control was not enforced; re-baseline scope and route future changes formally ✓
  • C. Blame the team for accepting the extra work
  • D. Absorb it silently and push the deadline out
Correct answer: B. Uncontrolled small additions are scope creep; the fix is to re-baseline and enforce change control going forward.
A critical dependency on another team is at risk because their PM keeps deprioritising your work. How do you handle it?
  • A. Escalate to leadership immediately without talking to them
  • B. First engage the other PM to understand constraints and negotiate, escalating only if unresolved ✓
  • C. Reroute around them by having your team do their work
  • D. Absorb the delay silently into your schedule
Correct answer: B. Cross-team dependencies are best resolved by direct negotiation first, reserving escalation for when collaboration fails.
Halfway through, you realise your original estimates were too optimistic across the board. What is the best move?
  • A. Keep the original plan and hope the team catches up
  • B. Re-forecast honestly using actuals to date and reset expectations with stakeholders ✓
  • C. Add buffer secretly so no one notices the change
  • D. Reduce the quality bar to hit the old numbers
Correct answer: B. When actuals show estimates were wrong, you re-forecast transparently rather than clinging to a plan you know is broken.
A stakeholder wants weekly green/amber/red status but everything you report as amber gets challenged. How do you keep reporting honest?
  • A. Report green to avoid the arguments
  • B. Define clear, objective criteria for each status so the rating is defensible ✓
  • C. Stop using RAG status altogether
  • D. Only show red once it is undeniable
Correct answer: B. Objective, agreed criteria for status make honest ratings defensible and remove the pressure to inflate them.
An issue emerges that you could probably resolve within the team, but it might breach the budget. When do you escalate?
  • A. Never; escalating shows you cannot handle your project
  • B. When it exceeds your authority or threatens a baseline you cannot protect alone ✓
  • C. Always, for every issue, to stay safe
  • D. Only after the budget has already been breached
Correct answer: B. Good escalation judgement triggers when an issue exceeds your authority or threatens a baseline, and while options still exist.
Your team is consistently missing sprint commitments. What is the most useful thing to investigate first?
  • A. Whether individuals are simply not working hard enough
  • B. Whether the team is over-committing, blocked, or estimating poorly ✓
  • C. Whether you should replace the underperformers
  • D. Whether to just extend every sprint by a few days
Correct answer: B. Chronic misses usually point to systemic causes like over-commitment or blockers, which must be diagnosed before acting on people.
A key subject-matter expert is a bottleneck because every decision routes through them. How do you reduce the risk?
  • A. Accept it since they are the expert
  • B. Document decisions, spread knowledge and empower others to reduce single-point dependency ✓
  • C. Escalate to have them assigned full-time to you
  • D. Route around them and make the calls yourself
Correct answer: B. Single points of failure are mitigated by spreading knowledge and decision rights, not by depending on one person harder.
You are asked to add a feature that benefits one stakeholder but adds risk to the launch. How do you decide?
  • A. Add it because the stakeholder asked and is important
  • B. Weigh the value against the added risk and delay, and decide with the sponsor if it is close ✓
  • C. Reject it to protect your timeline no matter what
  • D. Let the team vote on whether to include it
Correct answer: B. Trade-off decisions weigh value against risk and cost, escalating the close calls to the accountable owner.
Two workstreams both need the same limited specialist next week. What is the best resolution?
  • A. Give the specialist to whoever asked first
  • B. Prioritise based on which workstream's need is more critical to the overall goal and sequence accordingly ✓
  • C. Split the specialist 50/50 and slow both down
  • D. Ask the specialist to work double hours
Correct answer: B. Contended resources are allocated by overall priority and critical-path impact, not first-come or splitting that harms both.
A risk you flagged was dismissed by stakeholders as unlikely, and now it is happening. What is the best response?
  • A. Say 'I told you so' and document that you warned them
  • B. Focus on managing the issue now and calmly revisit the risk process for next time ✓
  • C. Escalate that stakeholders ignored you
  • D. Handle it silently to avoid embarrassing anyone
Correct answer: B. The priority is resolving the live issue; process lessons are handled constructively afterward, not as blame.
Mid-project, the business context shifts and the original goal is now less valuable. What should the PM do?
  • A. Finish the plan as agreed since it was signed off
  • B. Raise it with the sponsor and reassess whether scope or objectives should change ✓
  • C. Quietly pivot the team to what you think is now right
  • D. Keep going and let leadership notice on their own
Correct answer: B. When the underlying value changes, the PM surfaces it so the sponsor can decide whether to re-scope, rather than delivering the wrong thing.
You have to give bad news about a slip to a demanding executive. How do you approach the conversation?
  • A. Bury it at the end of a long positive update
  • B. Lead with the issue, its impact, the cause and your recommended options ✓
  • C. Wait until they ask directly before mentioning it
  • D. Present it as entirely the vendor's fault
Correct answer: B. Bad news is delivered early and directly, paired with impact, cause and options, so the executive can act.
Your recovery plan for a slipping timeline could involve adding people, cutting scope, or extending the date. How should you choose?
  • A. Always add people since more hands means faster delivery
  • B. Evaluate each against quality, cost and the specific cause of the slip, then recommend the best fit ✓
  • C. Always cut scope because it is the cheapest
  • D. Let the sponsor pick blindly from the three
Correct answer: B. The right recovery lever depends on the cause and the trade-offs; adding people to a late project often makes it later.
A stakeholder bypasses you and directs the team to change priorities. How do you handle it?
  • A. Let it slide to avoid confrontation
  • B. Address it directly with the stakeholder, reaffirming how changes should flow through the plan ✓
  • C. Complain to the team about the stakeholder
  • D. Escalate to the sponsor before talking to anyone
Correct answer: B. Undermining of the process is handled with a direct, professional conversation to re-establish the change path.
You inherit a project with no risk register and a nervous sponsor. What is the best early action?
  • A. Reassure the sponsor that everything is under control
  • B. Run a risk identification workshop and establish visible tracking and reporting ✓
  • C. Rewrite the entire plan from scratch first
  • D. Wait until you fully understand everything before acting
Correct answer: B. Establishing risk visibility quickly builds sponsor confidence and gives you a basis to manage proactively.
A team member's task is late and they keep saying 'almost done' each day. What is the best PM response?
  • A. Trust them and keep waiting for it to land
  • B. Break the remaining work into concrete steps and get a specific, evidenced completion plan ✓
  • C. Take the task away and do it yourself
  • D. Escalate them to their line manager
Correct answer: B. 'Almost done' is a signal to decompose the remaining work and get a concrete, verifiable plan to close it out.
Stakeholders want more frequent updates, but reporting is eating your delivery time. How do you balance this?
  • A. Give them everything they ask however often they ask
  • B. Right-size the reporting cadence and automate or standardise it to reduce overhead ✓
  • C. Cut reporting to the minimum to protect delivery
  • D. Delegate all reporting to a junior with no oversight
Correct answer: B. You meet the communication need efficiently by standardising and automating reporting rather than over- or under-serving it.

Hard round 20 questions

You have no formal authority over the teams delivering your program, yet you must get their commitment. What is most effective?
  • A. Remind them that the sponsor mandated the program
  • B. Build relationships, align the work to their goals, and make the shared value and trade-offs visible ✓
  • C. Escalate to their managers whenever they hesitate
  • D. Track their tasks tightly and report misses upward
Correct answer: B. Influence without authority comes from relationships, aligned incentives and transparent value, not from mandate or surveillance.
Two of your programs are both behind, and you can only rescue one this quarter with the available budget. How do you decide?
  • A. Save the one whose sponsor is most senior
  • B. Assess which delivers greater strategic value and probability of recovery, and recommend that with clear rationale ✓
  • C. Split the budget so both limp forward
  • D. Save the one that is furthest along regardless of value
Correct answer: B. Portfolio-level calls weigh strategic value and recoverability, and the reasoning is made explicit to leadership.
Your project is on time and budget, but early signals suggest it will not actually move the business metric it was meant to. What do you do?
  • A. Deliver on time and budget as agreed and declare success
  • B. Raise the outcome risk with the sponsor and reassess whether the approach still achieves the intended benefit ✓
  • C. Keep quiet since the metric is not your responsibility
  • D. Change the success metric to one you will hit
Correct answer: B. Mature PMs manage to outcomes, not just on-time delivery, and surface benefit risk even when the triple constraint looks green.
A powerful executive keeps pushing a pet feature that data shows users do not want. How do you handle the HiPPO?
  • A. Build it since they hold the budget
  • B. Bring evidence and a small test to inform the decision, framing it around the shared goal ✓
  • C. Refuse and cite the data flatly
  • D. Build it but quietly deprioritise it and hope they forget
Correct answer: B. You counter HiPPO decisions by reframing around shared goals and letting evidence or a low-cost experiment inform the call.
Your team has been in crunch for months and morale is collapsing, but the deadline is fixed by a regulator. What is the wisest move?
  • A. Keep pushing; the deadline is non-negotiable so there is no choice
  • B. Rescope to the true regulatory minimum and protect the team, escalating trade-offs that remain ✓
  • C. Add more people immediately to share the load
  • D. Extend the deadline unilaterally to relieve pressure
Correct answer: B. With a fixed date, the lever is scope; you protect sustainable pace by cutting to the genuine must-haves and escalating the rest.
How should you measure the impact of a program that delivered a platform other teams build on?
  • A. By the number of tasks and milestones your team completed
  • B. By the downstream outcomes it enabled, tied to the original business case and adoption ✓
  • C. By how much of the budget was spent
  • D. By the volume of features shipped
Correct answer: B. Enabling programs are measured by the business outcomes and adoption they unlock, not internal output or spend.
A trusted senior engineer is quietly gold-plating their work, adding polish nobody asked for and slipping the schedule. How do you address it?
  • A. Let it go because the quality is genuinely high
  • B. Reconnect them to the priorities and definition of done, and agree what 'good enough' means here ✓
  • C. Publicly call out the slippage in standup
  • D. Remove them from the critical path entirely
Correct answer: B. Gold-plating is corrected by realigning the person to agreed priorities and a shared definition of done, respectfully and directly.
A vendor issue threatens your launch, and escalating will expose that you approved the vendor. Do you escalate?
  • A. No; protect your reputation and try to fix it silently
  • B. Yes; escalate promptly with the facts and options because the project outcome outweighs personal optics ✓
  • C. Only if you cannot resolve it before anyone notices
  • D. Escalate but frame it so the blame lands on the vendor
Correct answer: B. Escalation judgement puts the project's outcome above personal optics; delaying to protect yourself compounds the damage.
Two departments are locked in a turf conflict that is blocking your program, and both have legitimate concerns. What is the senior move?
  • A. Pick the department with more political weight
  • B. Facilitate a session to surface the real interests behind their positions and broker an option that serves the program goal ✓
  • C. Escalate to force a top-down ruling immediately
  • D. Wait for them to resolve it themselves
Correct answer: B. Deep conflicts are unblocked by getting beneath positions to underlying interests and brokering a goal-serving solution.
Leadership asks you to commit to an aggressive date publicly, but your analysis shows only a 40% chance of hitting it. What do you do?
  • A. Commit to the date; leaders want confidence, not caveats
  • B. Present the probability and the conditions or trade-offs that would raise it, and commit to a defensible plan ✓
  • C. Refuse to give any date until certainty is high
  • D. Privately plan for the realistic date while announcing the aggressive one
Correct answer: B. Senior PMs commit honestly, exposing the confidence level and the levers, rather than over-committing to a number they do not believe.
Your program's original business case assumptions are now clearly outdated. How do you handle governance?
  • A. Keep delivering to the approved case to avoid reopening decisions
  • B. Bring the revised assumptions back to the steering group to re-validate whether the program should continue, pivot or stop ✓
  • C. Adjust the plan yourself based on the new assumptions
  • D. Wait until the program ends to note the assumptions changed
Correct answer: B. When assumptions underpinning the case change materially, good governance means re-validating the investment decision, including stopping.
You must recover a red program a peer just handed you, with a team that has lost trust in leadership. Where do you start?
  • A. Announce an aggressive new plan on day one to show control
  • B. Rebuild an honest picture with the team, stabilise the top risks, then reset realistic commitments ✓
  • C. Replace the people you think are underperforming
  • D. Report green upward to buy time while you figure it out
Correct answer: B. Turnarounds start with an honest reassessment and rebuilding trust before making credible, realistic commitments.
A metric your program is optimising (tickets closed) is being gamed and no longer reflects real value. What is the right response?
  • A. Keep the metric; it still looks good in reports
  • B. Shift measurement to the underlying outcome the metric was a proxy for, and communicate why ✓
  • C. Add more targets on top of the same metric
  • D. Punish the teams that are gaming it
Correct answer: B. When a proxy metric becomes a target and is gamed, you refocus measurement on the true outcome it was meant to represent.
You realise cancelling your struggling project is likely the best decision for the business, though you have invested a year in it. What should you do?
  • A. Keep going to honour the investment already made
  • B. Present an objective recommendation to stop or pivot, ignoring the sunk cost ✓
  • C. Slow-roll it quietly until leadership loses interest
  • D. Push for more budget to give it one more chance
Correct answer: B. Sound judgement ignores sunk cost and recommends the option best for the business, even when it means stopping your own project.
A high-performing but abrasive tech lead is alienating the rest of the team and it is hurting delivery. How do you handle it?
  • A. Tolerate it because their output is essential
  • B. Give direct, specific feedback on the impact and set clear expectations, escalating with their manager if needed ✓
  • C. Remove them quietly to keep the peace
  • D. Reorganise the team so no one has to work with them
Correct answer: B. Difficult high performers require candid feedback on impact and clear expectations, not avoidance that lets the harm continue.
Your steering committee wants an optimistic narrative, but the program is genuinely at risk. How do you report?
  • A. Give them the optimistic story they want to hear
  • B. Present a clear-eyed status with risks and options, because their decisions depend on the truth ✓
  • C. Soften the risks so much they seem trivial
  • D. Only escalate once the risk has fully materialised
Correct answer: B. Governance bodies make decisions on your reporting, so integrity requires the honest picture even when it is unwelcome.
Adding a needed feature would require breaking a commitment you made to another team about a shared component. How do you decide?
  • A. Break the commitment; your project's needs come first
  • B. Talk to the other team to renegotiate transparently, weighing the program-wide impact before deciding ✓
  • C. Add the feature quietly and deal with fallout later
  • D. Drop the feature to avoid any conflict
Correct answer: B. Cross-team commitments are renegotiated openly with a view to the whole program's outcome, preserving trust and dependencies.
You suspect a dependency owner is over-reporting progress to avoid scrutiny, putting your milestone at risk. What is the best approach?
  • A. Accept their status to keep the relationship smooth
  • B. Ask for concrete evidence of progress and jointly verify the real state without accusation ✓
  • C. Report them to their manager for lying
  • D. Assume the worst and rebuild their part yourself
Correct answer: B. You de-risk questionable status by verifying against concrete evidence collaboratively, protecting both the milestone and the relationship.
A major risk has a low probability but would be catastrophic to the company if it hit. How should you treat it?
  • A. Deprioritise it because it is unlikely
  • B. Give it serious mitigation and contingency planning proportional to its severe impact ✓
  • C. Ignore it since planning for it wastes effort
  • D. Escalate it once and then consider it handled
Correct answer: B. Low-probability, high-impact risks warrant real mitigation and contingency because the consequence, not just the odds, drives the response.
Delivering the full scope on time would ship a mediocre product, while cutting scope would ship something genuinely valuable late. How do you frame the decision?
  • A. Ship full scope on time; hitting the date is what matters
  • B. Present the outcome trade-off to the sponsor with a clear recommendation grounded in delivered value to users ✓
  • C. Cut scope unilaterally because quality matters most
  • D. Let the team decide since they know the work best
Correct answer: B. The senior move frames it as an outcome trade-off for the accountable owner, anchored in real user value rather than defaulting to the date.

Prep for another role

Questions are original, written and independently verified for HireHire's role interview quizzes. They reflect the kind of knowledge Project / Program Manager interviews test, not any specific company's questions. HireHire maps live tech & IT jobs across India, updated regularly. Last updated: August 2026.