The employer wants to see judgment in tradeoff decisions under schedule pressure. A project manager must evaluate scope, time, cost, and quality rather than defaulting to overtime or hiring.
Name the three classic levers, then explain how you would compare them against the project's fixed constraint and risk. Use a specific example where you chose one and why.
Start by saying plainly that there is no single right lever, only the right lever for the project's fixed constraint. Explain that you would first identify what cannot move: a regulatory filing, a client launch, a contractual penalty. If the date is truly hard, then reducing scope becomes your primary option, but only after you map the must-have versus nice-to-have features with the client and get explicit sign-off on what is deferred. Extending the date is the honest choice when the deadline is internal or negotiable, and when pushing scope or adding people would wreck quality; in that case, you protect the team from burnout and the product from defects. Adding people is the weakest default, especially in a Philippine BPO or tech context where onboarding, training, and communication overhead can eat the very days you are trying to save, so you would only consider it if the remaining work is highly parallelizable and the new hires come from a ready bench. Then walk through your reasoning aloud: estimate the critical path, quantify the cost of each option, and state what you protect, whether that is the date, the scope, or the team's wellbeing. Close by saying you would present the tradeoff to stakeholders with a clear recommendation and a fallback, and that the mark of a good PM is making the call before the deadline forces it on you.
Some candidates answer 'Dagdagan na lang ng tao para sure' without considering onboarding time and communication overhead. Weigh all three options and state what you would protect: date, scope, or cost.
Situation
During a freelance website build for a startup client, we were nine days behind the agreed launch date because the client kept requesting small design changes beyond the signed scope.
Task
I needed to decide how to recover the schedule without damaging the relationship or burning out the two developers.
Action
I compared three options: cut the remaining lower-priority pages, push the launch date by two weeks, or bring in an additional developer. I recommended reducing scope by deferring the blog and FAQ pages to phase two, because the fixed launch date was tied to a product release. I presented the tradeoff to the client with data on hours saved and risk.
Result
The client approved the phased scope, and the core site launched on time. The deferred pages went live ten days later as a small phase two.
The best recovery option depends on whether the deadline or scope is the fixed constraint.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.