Tell me about a time you worked to a very tight deadline.
Explain the deadline and why it was tight, how you planned and prioritised, what you dropped or simplified, and the final outcome. Show that you delivered without cutting important corners.
Explain it simply
Tight deadlines force choices. The interviewer wants to know how you choose: what you do first, what you leave out, and whether you keep quality where it matters.
A good story shows a plan, honest communication about what could and could not be done, and a result. If you had to drop something, say what and why.
Example
Situation: Fatima's college announced the national-level project expo with only four days to submit a working model and report.
Task: Prepare the model, report and video in four days alongside classes.
Action: She listed every requirement, agreed with her two teammates who owned what, and fixed a daily evening check. They used their existing smart-irrigation prototype instead of starting new, and dropped a planned mobile app, showing data on a simple web page instead. She wrote the report while the hardware was tested.
Result: They submitted six hours before the deadline and were shortlisted for the final round.
What to say in the interview
"We had four days for X. I listed everything, split ownership, reused what we had and dropped Y to keep quality on Z. We submitted early and..."
Common mistakes
- Describing all-nighters as the only strategy.
- Missing the deadline and calling it a success.
- Not mentioning any prioritisation.