Katkat
Back

Why Would Users Care and Why Build It?

GoogleProduct Manager · Technical Screen
HardProduct ManagerTechnical ScreenProduct Design & Strategy

Last updated

Build a product strategy answer for a Google AI productivity assistant across Search, Gmail, Docs, and Calendar. Covers user pain points, MVP, 15-year vision, VP pitch, Google advantages, metrics, and risks.

You are interviewing for a Google Product Manager role. Assume the product is a new Google AI productivity assistant integrated into Search, Gmail, Docs, and Calendar for knowledge workers.

The interviewer asks:

  1. Why would users care about this product today?
  2. How could its value proposition evolve over the next 15 years?
  3. If speaking to a VP, how would you convince them Google should build it?

Constraints & Assumptions

  • Focus on user value first, not AI novelty.
  • Identify target users, jobs to be done, pain points, and trust constraints.
  • Include a near-term MVP and long-term vision.
  • Explain why Google is uniquely positioned without overstating certainty.
  • Discuss risks such as hallucination, privacy, user control, enterprise compliance, and over-automation.

Clarifying Questions to Ask

  • Is this for consumer users, Workspace enterprise users, or both?
  • Which workflow is the initial wedge: email, documents, meetings, search, or calendar?
  • Are autonomous actions in scope or only suggestions?
  • What business model is being considered?

Follow-up questions

  • What should the MVP not do?
  • How would you measure time saved credibly?
  • What would make users stop trusting the assistant?
  • How would you pitch this differently to an enterprise buyer?