What interviewers are really asking
This question probes two things simultaneously: your practical time management skills and your emotional response to pressure. Interviewers want to hire people who get things done under pressure without either missing the deadline or falling apart in the process. The worst answer is "I work really hard and stay late." That describes effort without any structure or method.
The question is most commonly asked for roles where deadlines are a real feature: project management, journalism, legal, finance (quarter-close, audit, regulatory filings), software development (sprint cycles, release gates), and any client-facing role where external parties set the schedule. If you are applying to one of these roles, expect this question or a close variant.
How to structure your answer
Use a STAR structure (Situation, Task, Action, Result) but lead with a brief statement of your general approach before the specific example. This gives the interviewer a framework before the story. Opening statement (1-2 sentences): "When I face a tight deadline, my first move is always to break the deliverable into the minimum viable version versus the nice-to-have additions, so I know what I am protecting." Then move into a specific example that demonstrates that approach in action.
The best examples involve: a deadline that was genuinely tight (not just slightly uncomfortable), a proactive response (you did not just react when the deadline was already missed), clear prioritisation, and a result that was either delivered on time or where a smart trade-off decision was made and communicated in advance.
Sample answers
Example for a project or operations role: "At my previous company, we had a client deliverable that suddenly moved forward by four days due to their own board meeting. I sat down with the team that evening and identified the three components the client would actually review in the meeting versus the four additional sections that were for the appendix. We redirected all effort to the core three, finished them the day before the meeting, and flagged clearly to the client that the appendix sections would follow the following week. They appreciated the transparency and the delivery. The appendix arrived on time without a second crunch."
Example for an individual contributor role: "During our product launch, the QA sign-off was delayed by two days and the release date did not move. I spent the first hour creating a priority matrix of which test cases covered the highest-risk user flows versus edge cases with low traffic. I completed the high-priority tests within the reduced window, documented the outstanding items clearly, and gave the product manager an honest risk assessment so they could make an informed go/no-go call. We launched. The two remaining test areas were cleared within two days post-launch and there were no production issues."
What not to say
Do not say you "thrive under pressure" without demonstrating the mechanism. It is the most common non-answer to this question and interviewers have heard it thousands of times. Do not pick an example where you simply worked longer hours and everything was fine: that shows endurance, not skill. Do not choose an example where you missed the deadline or significantly reduced quality without having communicated the trade-off in advance: that is a red flag, not a story. If the honest answer is that you struggle with deadlines, be prepared to talk about what you have put in place to address that: tools, habits, early flagging behaviours.