Describe a time you had to deliberately drop or cut committed work. How did you decide what to cut, and how did you communicate it?
What they are really testing: They are testing whether you have an explicit ranking mechanism, or whether cutting is just panic dressed up as judgement. At senior level they also want to see you protect the team from the blast of the cut.
A real interview question
Describe a time you had to deliberately drop or cut committed work. How did you decide what to cut, and how did you communicate it?
What most people say
drag me
“We cut the nice-to-haves and kept the important stuff. The team pulled together and we got the critical things out.”
It gives no mechanism, no axis, and no numbers, so it could describe any project on earth. An interviewer cannot tell whether you made a good call or a lucky one, and a senior candidate is hired precisely for the mechanism.
The follow-ups they ask next
How do you handle a stakeholder who says everything is critical?
Do not argue about importance, argue about order. Ask which single item they want first if only one lands, and repeat until you have a ranked list.
What did you tell the team about the work they had already started on the cut items?
Say it directly and quickly, and own the call yourself. Sunk effort is real to people, so name it, thank them, and do not let it drag on unspoken.
Have you ever cut the wrong thing?
Have one ready. Say what signal you missed, and what check you added, for example asking one person outside the team to red team the cut list.
What the interviewer is listening for
- Names an explicit axis for the cut rather than a general sense of importance
- Makes the deferred list public with owners and dates instead of letting it vanish
- Cuts early and says explicitly that late cuts waste team hours
What sinks the answer
- Cuts testing, monitoring, or rollback plans first because they are invisible
- Lets the team keep working on items already destined to be dropped
- Cannot describe the cost of the deferred work, so the trade off was never priced
If you genuinely do not know
Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.
“I have not owned a cut this size, but here is how I would reason about it. I would rank on reversibility, keep anything that becomes impossible after the deadline, defer anything we can still do next quarter, and publish the deferred list with owners so nothing disappears silently.”
Keep going with behavioural
Foundation
Tell me about a time you had to learn a new technology quickly. How did you go about it?
Foundation
So, why cloud? You have not worked in cloud before, so walk me through what actually pulled you here.
Foundation
Why are you leaving your current job?
Foundation
Tell me about a time you noticed something was broken, wasteful or risky, and nobody seemed to own it. What did you actually do?
Junior
You join a team and inherit a service with no documentation and the original author has left. Walk me through your first week.
Junior
Describe a time you were blocked and there was genuinely nobody available to ask. What did you do?
Knowing the answer is not the same as recalling it under pressure
Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.
Start free