Imagine you are two weeks from a committed launch date and you realize the project will need four more weeks. What would you do?
The interviewer is looking for: what you clarify before answering, whether you reason from a real framework about scope, time and quality rather than improvising, and whether you can ground the answer in something you have actually lived through.
Note: This is a hypothetical. Ask your clarifying questions out loud, reason through them, and then anchor it with a brief real example.
How to approach it
- Hint 1
Hypotheticals test judgment when experience cannot be assumed. The interviewer is watching for what you ask before you answer, and whether you have a repeatable way of thinking about a slip -- not whether you land on a specific right answer.
- Hint 2
Open with one or two sharp clarifying questions and then answer them yourself as stated assumptions, so you keep moving: is the date externally committed or internal? Is the scope divisible? Then reason through the levers you actually have -- cut or phase the scope, move the date, trade quality or manual workarounds, add help knowing it may slow you down -- and say which you would reach for first and why.
- Hint 3
Do not stop at abstraction. Spend the last third grounding it in a real slip you handled: how early you raised it, what you brought to the conversation besides bad news, and what the options you offered actually were. Escalating with options attached is the behavior being scored.
Ready to answer it out loud?
Record your answer in 2:00 and Preptile scores it 1–10 with specifics — what landed, what you skipped, and what to say next time.
Practising needs an invite code. Join the waitlist and we’ll send you one.