Behavioral: Delivering Under a Tight Deadline and Handling a Difficult Situation
MicrosoftSoftware Engineer · OnsiteLast updated
A senior behavioral question in two parts: describe delivering an important project against a tight deadline, then a difficult work situation and how you handled it. It tests prioritization, scope negotiation, stakeholder communication, ownership of decisions, and composure under pressure.
This question comes from a competency-based behavioral round for a senior engineering role. The round is unhurried: the interviewer asks only a few questions in an hour and spends most of the time on follow-ups, so each story needs enough depth to survive several rounds of "why" and "what exactly did you do". Two of the reported prompts are about delivering under pressure. Prepare a different real story for each part.
Constraints and Clarifications
- Use real experiences from your own work; the follow-ups will probe details that an invented story cannot support.
- At a senior level, the story should show decisions you made about scope, people and risk, not only extra hours worked.
- Expect each answer to take several minutes, with follow-ups.
Clarifying Questions
- Should the two stories come from different projects, or can one project illustrate both?
- How recent should the examples be?
- Is the interviewer more interested in the decisions I drove or in the final outcome?
Part 1 — An important project on a tight deadline
Tell me about an important project you delivered under a tight deadline. What made the deadline tight, what did you change about how the work was done, and what was the result?
What This Part Should Cover
- Why the deadline mattered and what made it hard to meet
- Concrete prioritization or scope decisions the candidate drove
- How risk was managed and communicated to stakeholders
- A measurable outcome and an honest account of its cost
Part 2 — A difficult situation
Describe a difficult situation you faced at work and how you handled it. Choose one where the right course of action was not obvious at the start.
What This Part Should Cover
- What made the situation hard, in specific terms
- The options considered and why one was chosen
- The candidate's personal actions rather than what the team did in general
- What changed afterward as a result
Hints
Hint 1
What did you give up: Be ready to name what was cut, deferred or done differently to hit the date, who agreed to it, and what it cost afterward.
Hint 2
Make the difficulty concrete: Pick a situation with a specific obstacle, such as an incident, a failing dependency or a sudden change of direction, where your own actions changed how it ended.
Follow-up questions
- If you had had one more week, what would you have done differently?
- What did you push back on to protect the deadline, and how did that conversation go?
- How did you keep the team from burning out while you pushed for the date?
- What early signal would tell you that a project is heading toward a deadline crisis?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.