Product design question
Claude Tag works well on Slack. You are evaluating whether to launch next on Microsoft Teams or Jira. How would you decide if a surface is worth pursuing, and if you chose it, how would you adapt Claude Tag's core interaction model so it feels native to that surface rather than a Slack clone?
- Anthropic
- Product design
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests platform expansion judgment for a collaboration tool, evaluating surface worth and adapting the interaction model to feel native rather than ported.
How to approach it
- Define worth pursuing with concrete criteria: active enterprise usage on the surface, how naturally an assistant fits its patterns, and API support.
- Compare Teams and Jira directly, noting Teams is a real time chat surface closer to Slack while Jira is structured and asynchronous.
- Choose based on which surface's interaction model Claude Tag can adapt to without becoming a worse version of the Slack experience.
- Redesign the core interaction for the chosen surface, for example on Jira shifting from a chat mention to a ticket comment invocation.
- Validate the adapted model with a small design partner group before general availability.
What a strong answer includes
- Uses concrete, comparable criteria across both surfaces instead of a gut call based on which is more popular.
- Recognizes Jira's asynchronous, structured nature demands a genuinely different interaction model than a chat mention, not a reskin of the Slack experience.
- Names a specific redesigned interaction, such as ticket comment triggered invocation, rather than saying it would adapt generally.
- Proposes validating the new interaction model with real users before wide rollout, since a native feeling redesign is a hypothesis, not a guarantee.
Common mistakes
- Picking a surface based on size alone without checking whether Claude Tag's interaction model actually fits its usage patterns.
- Porting the Slack experience directly instead of redesigning around the new surface's native interaction patterns.
Likely follow-up questions
- What specific API limitation would make you reconsider the chosen surface?
- How would you know the redesigned interaction actually feels native to users?
More product design questions
- What would you build to help enterprises trust Claude with sensitive data?Anthropic · Product design · Medium
- Design onboarding for a developer trying Claude's API for the first time.Anthropic · Product design · Easy
- Claude Code can spawn hundreds of parallel subagents in one session. What risks would you design for?Anthropic · Product design · Hard
- Design a product that helps non-developers use Claude for knowledge work (Claude Cowork).Anthropic · Product design · Medium
- How would you improve Claude Code's experience for enterprise engineering teams?Anthropic · Product design · Medium
- Vendors report that a new annotation task for Claude’s evolving real-world usage has cut worker throughput by 40%, while researchers say the richer feedback is essential. How would you redesign the workflow or interface to recover speed without degrading end-to-end data quality? Be specific about the user pain points, hypotheses, and what you’d prototype first.Anthropic · Product design · Hard
More questions from Anthropic
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 7: AI UX and human oversight: design for a system that is wrong sometimes
- Chapter 14: Get the job: the AI PM interview loop