It is launch week for a big campaign, and constant meetings, requests, and fire drills are leaving no time for your core work. How would you handle the week?
This is a hypothetical scenario question — the interviewer wants your decision framework, not a war story. Here is a model answer, the mistakes to avoid, and the follow-ups to expect.
A strong example answer
The campaign launched on time and beat its signup target — and what saved the week was a single message posted on Monday morning. Launch weeks are never calm, so I stopped fighting that and designed around it. Before the flood started, I named the couple of outcomes only I could deliver that week and blocked focus windows on my calendar each day, treated like meetings I was not allowed to miss. Everything else got triaged with two questions: does this block the launch, and does it need me specifically?
Roughly half the interruptions turned out to need an answer, not a meeting, and I handled those in two batched windows daily. Another chunk could be delegated — I handed recurring approvals to a teammate with a one-page decision guide so the calls stopped routing through me. Then came the message itself: I posted in the team channel that I was in launch mode, what to escalate immediately, and what would wait until Friday. People self-triaged, and the incoming pings dropped noticeably. Looking back, none of it was heroics — I decided on Monday what mattered, said so out loud, and let everything else queue behind it. The requests never shrank; my exposure to them did. I still post that message at the start of every big week, and the week no longer happens to me.
A framework for your own answer
- Situation: Set up the launch week and the flood of incoming demands.
- Task: Name the one or two outcomes only you can deliver that week.
- Action: Show how you protected focus time, triaged requests, and set expectations.
- Result: Give the campaign result and the working norm you kept afterward.
Common mistakes to avoid
- Rank urgency, or the week will simply happen to you.
- Candidates often go dark without telling anyone, so teammates escalate or duplicate their work.
- Nobody benefits when you refuse to delegate trivial approvals because only you can do it right.
- What does a week of nights and weekends buy? Tired, error-prone launch work.
Follow-up questions to prepare for
Interviewers use follow-ups to verify your story is real. If you get this question in a real interview, expect probes like:
- How do you handle a request from someone senior that does not block the launch?
- What does your decision guide for a delegate actually contain?
- How do you recover the deep work that got displaced during a week like this?
Related practice questions
Keep drilling with these, or browse the complete question bank.
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator