← Google Interview Insights

Google·Technical Product Manager·Onsite - Behavioral / Leadership·Senior

Senior
Apr 2026

Summary

Interviewed for a TPM role at Google and got hit with a scenario-based question about handling sick leave on a team right before a deadline. Short loop, nothing too wild, but the question had more layers than I expected.

Questions Asked (1)

Q1

A team member goes on sick leave right before a critical project deadline. How do you handle it?

Stakeholder ManagementCross-functional AlignmentAdaptability & Ambiguity
Author's notes

My first instinct was to jump straight into resource reallocation and I think that was the wrong move to lead with.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Acknowledge the situation calmly, then outline a structured plan to assess impact, reallocate work, and communicate with stakeholders. Emphasize prioritization, cross-functional collaboration, and maintaining team morale while meeting the deadline.

Pro tip: Show empathy for the team member's health first, then focus on solutions. Mention that you'd document lessons learned to improve future contingency planning, demonstrating proactive leadership.

1. Assess Impact and Prioritize

Quickly evaluate the absent team member's critical tasks and dependencies. Identify which deliverables are must-have versus nice-to-have for the deadline.

2. Reallocate and Support

Redistribute work among available team members based on skills and capacity, or bring in temporary help. Ensure no one is overloaded and provide necessary context.

3. Communicate Transparently

Inform stakeholders (e.g., engineering, design, leadership) about the situation, adjusted plan, and any risks. Set clear expectations on what will be delivered and when.

4. Monitor and Adjust

Track progress daily, remove blockers, and be ready to descope or extend timeline if needed. Keep the team motivated and focused on the critical path.

5. Follow Up and Learn

After the deadline, check in on the team member's recovery and conduct a retrospective to improve future contingency planning.

Key Points to Mention

  • Prioritization frameworks (e.g., MoSCoW, RICE) to decide what to cut or defer.
  • Cross-functional collaboration: leveraging partners in engineering, design, or other PMs.
  • Stakeholder communication: transparent updates and expectation management.
  • Risk mitigation: having a contingency plan or buffer in project schedules.
  • Team well-being: avoiding burnout and supporting the sick team member.
  • Documentation and knowledge sharing to reduce single points of failure.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.