Dataford
Interview QuestionsInterview GuidesExperiencesMock InterviewsPricing
Get started

Recover a Delayed Gemini Launch

EasyExecution00:00
Practice interviewer
In session
5 left
00:00

Your question is Recover a Delayed Gemini Launch. Take a moment with it on the right.

Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).

You need to log in / sign up to chat or submit.

Problem

Project Context

Google Workspace is preparing to launch a new Gemini-powered meeting summary feature in Google Meet for enterprise customers. A 14-person cross-functional team has completed a pilot, but the pilot failed to meet quality targets and generated strong negative feedback from Sales and a design partner customer. You are the PM responsible for recovering the launch plan before the end of the quarter, which is 10 weeks away.

Key Stakeholders

The VP of Google Workspace wants the feature launched this quarter to support a public roadmap commitment. The Engineering Manager wants to reduce scope to protect reliability. Legal and Privacy require stricter review after pilot feedback flagged possible exposure of sensitive meeting content. Sales wants the original feature set because two large enterprise deals reference it in renewal conversations.

Constraints

You have 10 weeks, a fixed budget of $180,000 for vendor evaluation and QA support, and no additional headcount beyond 8 engineers, 2 UX designers, 1 UX researcher, 1 data analyst, 1 TPM, and you as PM. The current pilot showed only 68% summary accuracy versus a 85% launch target, and latency averaged 11 seconds versus a 5-second requirement. Privacy review must be completed before any external rollout. A Google Cloud infrastructure dependency will not be available until Week 4.

Complications

  1. A design partner customer has escalated that one inaccurate summary was shared internally and damaged trust.
  2. The VP has asked whether a limited launch is possible despite the failed pilot.
  3. One senior engineer is rotating off the team in Week 3.

Deliverables

  1. Build a 10-week recovery plan with milestones, owners, and launch criteria.
  2. Explain how you would handle the failed pilot and incorporate stakeholder feedback into the roadmap.
  3. Recommend whether to launch full scope, reduced scope, or a phased rollout, and justify the trade-offs.
  4. Define success metrics, go/no-go criteria, and a rollback plan.
  5. Identify the top risks and how you would mitigate them during execution.