Katkat
Back

Managing Delivery Dates When a Team Commitment Is at Risk

GoogleSoftware Engineer · Onsite
MediumSoftware EngineerOnsiteBehavioral & Leadership

Last updated

A behavioral question for an engineering manager on how they set, track and protect delivery dates, followed by a real case where a committed date was at risk. It tests early risk detection, weighing scope, staffing and date options, stakeholder communication, and protecting quality and team health.

The interviewer asks how you, as an engineering manager, handle deadlines and due dates: how dates for your team's work get set, how you track them, and what you do when one is in danger. Then walk through a specific time a date your team had committed to was at risk: how you found out, what you did, and how it ended.

Clarifying Questions

  • Are you more interested in externally fixed deadlines, internal targets, or both?
  • Should the example be one where the date was ultimately met, or is a well-managed slip acceptable?

Hints

Hint 1

Bring options, not only news: Think about how early you raised the risk, and what choices you put in front of the people who owned the date.

Follow-up questions

  • A director commits your team to a date without consulting you. What do you do?
  • How do you handle an engineer who repeatedly misses their own estimates?
  • When is letting a deadline slip the right call?