Slack Spam Strategy: Defining It, Picking What to Fix First and Measuring Progress
Company: Slack
Role: Product Manager
Category: Product Design & Strategy
Difficulty: medium
Interview Round: Other
You are a product manager at Slack. How would you stop spam on the product? Explain what you count as spam and how it reaches people, decide what you would do about it and in what order, and say how you would know your approach is working.
```hint Map the paths in
List every way an unwanted message can reach a Slack user, along with who sends it and why; each path points to a different place to intervene.
```
### Clarifying Questions
- Does "spam" mean unsolicited messages from outside the recipient's organization (cross-company invitations and direct messages, strangers in open community workspaces, abused invitation emails), or noise from inside it, such as overused workspace-wide mentions and chatty bots?
- Which customers matter most here: paid workspaces with admins and security teams, or free and open community workspaces run by volunteers?
- Can the solution inspect message content, or must it rely on behavior signals and user reports because of customer privacy commitments?
- Is the priority protecting users from harm such as phishing, or reducing annoyance?
### What a Strong Answer Covers
- A working definition of spam on Slack that separates its sources and says which one to tackle first, and why
- The people affected, including recipients, workspace admins and legitimate senders, and what each needs
- Countermeasures at different points in a spam message's life (before sending, at delivery, after delivery), compared and prioritized
- How the plan avoids blocking or muting messages people actually want, and how mistakes get corrected
- Success metrics with guardrails, and how the plan stays effective as senders change their behavior
### Follow-up Questions
- Senders work around a new rule or limit within weeks. How do you keep the plan effective without constant manual tuning?
- A large customer says your changes are holding back messages its people legitimately need to send. How do you respond, and what would you change?
- How would your approach differ for large public community workspaces whose admins are volunteers?
Overview: A product prompt about reducing spam on Slack. It tests deciding what counts as spam, whether unwanted contact from outside an organization or noise from inside it, mapping how those messages reach people, ordering fixes, protecting legitimate messages from mistakes, and measuring whether the approach works.