Should Google Workspace (G Suite) add built-in malware protection? Evaluate the call

Quick Overview

A product strategy question asking how a PM would decide whether Google's workplace suite should add malware and virus detection. It tests decision criteria, customer and competitor analysis, build versus buy and pricing options, security risks such as false positives and privacy, and a recommendation backed by metrics.

Should Google Workspace (G Suite) add built-in malware protection? Evaluate the call

Company: Google

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

G Suite, Google's bundle of workplace apps such as Gmail, Drive, Docs and Calendar (since renamed Google Workspace), is considering adding malware and virus detection. As the product manager, how would you evaluate whether to go ahead, and what would you recommend? ```hint Decide what you are deciding Pin down what the detection would scan and who pays for the suite before weighing pros and cons; the right call for a small business with no IT staff may differ from the call for a large enterprise that runs its own security tools. ``` ### Clarifying Questions - Which surfaces would the detection cover: Gmail attachments and links, files uploaded to or shared through Drive, links inside Docs and Chat, or all of them? - Does the suite scan anything today, making this an upgrade, or should it be treated as completely new? - Is the target paying business and education customers, free consumer accounts, or both, and would the feature be included in every plan or sold separately? - Is the open question only whether to do it, or also whether to build it, buy a security company, or partner with one? ### What a Strong Answer Covers - Decision criteria tied to the suite's goals, such as customer trust, winning and keeping organizations, and revenue, rather than an unweighted list of pros and cons. - Who needs the protection and how they get it today, plus how rival productivity suites and dedicated security vendors would react. - Concrete options (include it, sell a paid tier, partner, do nothing; build versus buy) with their full cost, including the ongoing work of keeping detection current. - Risks specific to security features: false positives that block real work, missed threats, privacy of scanning customer content, and liability. - A clear recommendation with success metrics, guardrails and conditions for a staged rollout. ### Follow-up Questions - In a pilot, admins complain that legitimate supplier invoices are being quarantined. How do you respond, and how would you set the blocking threshold? - A customer in a regulated industry objects to Google scanning its files. What options would you give them? - How would you show that the feature reduced real security incidents rather than just producing more warnings?

Overview: A product strategy question asking how a PM would decide whether Google's workplace suite should add malware and virus detection. It tests decision criteria, customer and competitor analysis, build versus buy and pricing options, security risks such as false positives and privacy, and a recommendation backed by metrics.

Google logo
Google
Jan 1, 2025
mediumProduct ManagerOtherProduct Design & Strategy
0
0

G Suite, Google's bundle of workplace apps such as Gmail, Drive, Docs and Calendar (since renamed Google Workspace), is considering adding malware and virus detection. As the product manager, how would you evaluate whether to go ahead, and what would you recommend?

Clarifying Questions Guidance

  • Which surfaces would the detection cover: Gmail attachments and links, files uploaded to or shared through Drive, links inside Docs and Chat, or all of them?
  • Does the suite scan anything today, making this an upgrade, or should it be treated as completely new?
  • Is the target paying business and education customers, free consumer accounts, or both, and would the feature be included in every plan or sold separately?
  • Is the open question only whether to do it, or also whether to build it, buy a security company, or partner with one?

What a Strong Answer Covers Guidance

  • Decision criteria tied to the suite's goals, such as customer trust, winning and keeping organizations, and revenue, rather than an unweighted list of pros and cons.
  • Who needs the protection and how they get it today, plus how rival productivity suites and dedicated security vendors would react.
  • Concrete options (include it, sell a paid tier, partner, do nothing; build versus buy) with their full cost, including the ongoing work of keeping detection current.
  • Risks specific to security features: false positives that block real work, missed threats, privacy of scanning customer content, and liability.
  • A clear recommendation with success metrics, guardrails and conditions for a staged rollout.

Follow-up Questions Guidance

  • In a pilot, admins complain that legitimate supplier invoices are being quarantined. How do you respond, and how would you set the blocking threshold?
  • A customer in a regulated industry objects to Google scanning its files. What options would you give them?
  • How would you show that the feature reduced real security incidents rather than just producing more warnings?