situational Medium GeneralSoftware Engineer

Your manager pressures you to ship a release two weeks early, but you know testing is incomplete. 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

Before anything else, I would find out what is actually driving the acceleration. A customer commitment, a marketing event, a competitor's launch — the real constraint often has more give than the date itself. Ask first; argue later.

Then come options, not objections. Ship the full scope early by cutting the lowest-value features. Or hold the original date and finish testing properly. Or, if the date truly cannot move, ship a hardened core release, run an abbreviated test plan aimed at the highest-risk paths, and schedule the rest as a fast follow. Each option gets a written risk assessment, and the trade-offs go into a one-page doc so the decision is explicit and shared — not silently mine. That part matters most. When leadership chooses with the risks on paper, quality stops being my private worry and becomes a business decision they consciously own.

On a payments release, my manager picked the third option. We shipped the core flow early, and the abbreviated testing caught two edge-case bugs before customers did. The remaining features followed shortly after, with no rollbacks. The date moved. The standard did not.

A framework for your own answer

  • Situation: Show the tension: a real deadline driver versus real quality risk.
  • Task: Clarify your duty — make the risk visible, not silently absorb it.
  • Action: Offer scoped options with explicit trade-offs instead of a flat no.
  • Result: Give the outcome and what made the risk discussion work.

Common mistakes to avoid

  • Don't cave and ship untested code with nothing documented — the risk then belongs to you alone.
  • Refusing flatly, before you understand what is driving the earlier date, reads as obstruction rather than judgment.
  • Complaints to peers go nowhere; structured options brought to the decision-maker are what change the outcome.
  • Who owns the business trade-off? Not you — treating quality as solely your call bypasses the manager whose decision it is.

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:

  • What if the manager insists on full scope and the early date?
  • How do you decide which tests are safe to cut?
  • Would you ever go over your manager's head on a quality risk?

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