situational Hard GeneralProduct Manager

Midway through a project, leadership cuts your budget or team but still expects delivery. How would you handle it?

This is a hypothetical scenario question — the interviewer wants your decision framework, not a war story. Here is a model answer, the mistakes to avoid, and the follow-ups to expect.

A strong example answer

We shipped on time with the reduced team, and onboarding support tickets fell by roughly a third the following quarter — close to the original goal on a fraction of the original resources. Getting there started with a hard moment: midway through the build, leadership pulled engineers off the project while keeping the deadline intact. Two temptations had to be refused — pretending the original plan still worked, and trimming scope quietly so stakeholders would find out at launch. Instead, I went back to the one metric the project existed to move and asked which features actually moved it. The answer concentrated fast: a small cluster of features carried most of the value, and the rest was negotiable.

I listed everything remaining with rough cost and expected impact, then brought the sponsor three tiers: what we could ship by the original date, what would slip, and what should be cut entirely — with a recommendation attached. She agreed in one meeting. After launch I wrote a short retrospective recording what was cut and why, so the dropped features could be revisited later against real usage data rather than nostalgia. Since then, every project I kick off starts with a tiered scope list from day one, which turns the next resource cut into a conversation instead of a crisis.

A framework for your own answer

  • Situation: Set up the project, the cut, and the unchanged expectation.
  • Task: Clarify what success metric the project still has to move.
  • Action: Show how you re-scoped with tiers and got explicit sponsor alignment.
  • Result: Give the shipped result and how you documented what was cut.

Common mistakes to avoid

  • Never accept the cut while committing to the original plan unchanged — that guarantees a late or broken delivery.
  • Candidates often trim scope silently, and stakeholders discover the missing features at launch.
  • An evenly spread cut feels fair but abandons the few features that actually drive the outcome.
  • Why complain about resources to the team when leadership needs a decision-ready proposal?

Follow-up questions to prepare for

Interviewers use follow-ups to verify your story is real. If you get this question in a real interview, expect probes like:

  • How do you decide which features carry the most value when data is thin?
  • What if the sponsor rejected all three of your tiers?
  • How do you keep team morale up after losing people mid-project?

Related practice questions

Keep drilling with these, or browse the complete question bank.

Next up

Practice this question on the clock

Reading an answer and delivering one are different skills. Run a timed round and rate yourself.

Start a practice round

Next up

Interview coming up?

Have your post-interview follow-up email ready before you need it.

Follow-up email generator