Strategy question
Anthropic wants PMs to uncover non-obvious use cases for frontier models and feed those insights back into research. How would you structure opportunity discovery, compare adjacent versus novel use cases, and choose the first experiments to run?
- Anthropic
- Strategy
- 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
Ability to structure opportunity discovery for a frontier model and connect it back to research priorities.
How to approach it
- Set up structured channels to surface use cases: customer interviews, support and sales signals, and hands-on internal experimentation with new capabilities.
- Separate adjacent use cases, which extend something the model already does well, from novel ones that need new capability or evaluation.
- Score candidate use cases on user value, technical feasibility given current model limits, and what they would teach research about model behavior.
- Choose a small first batch of experiments that spans both adjacent and novel cases, so learnings are not skewed toward the easy wins.
- Define what evidence from each experiment feeds back to research, such as failure modes or unexpected capability edges.
- Set a short cycle time so findings reach research while the underlying model version is still current.
What a strong answer includes
- Keeps adjacent and novel use cases in separate tracks since they need different validation approaches and timelines.
- Prioritizes experiments that generate research-relevant signal, not just ones likely to succeed commercially.
- Builds a lightweight, repeatable intake process instead of one-off exploration, so discovery keeps running after this project ends.
- Names a concrete first experiment and the specific question it would answer for research.
Common mistakes
- Only chasing obvious adjacent use cases and missing genuinely novel ones.
- Treating discovery as a one-time project instead of an ongoing feedback loop with research.
Likely follow-up questions
- How would you prioritize if a novel use case has high value but low current feasibility?
- What signal would convince research to prioritize a capability gap you found?
- How often would you refresh this process as models improve?
More strategy questions
- Claude is sold direct and via AWS Bedrock, Google Vertex, and Azure. How do you avoid channel conflict?Anthropic · Strategy · Hard
- How would you grow MCP adoption among third-party tool developers?Anthropic · Strategy · Hard
- How would you price Claude's Max plan ($100-200/mo) to maximize revenue without cannibalizing Pro?Anthropic · Strategy · Hard
- Should Anthropic build more consumer products or double down on API and enterprise?Anthropic · Strategy · Hard
- Anthropic positions itself around AI safety. How would you turn 'safety' into a product differentiator enterprises will pay for?Anthropic · Strategy · Hard
- A top researcher needs a bespoke data-collection workflow in 2 weeks for an upcoming training run, but engineering believes the same need may recur across several teams next quarter. How would you decide whether to ship a one-off tool, extend the current platform, or invest in reusable infrastructure? Walk through the criteria, stakeholders, and how you’d manage platform debt.Anthropic · Strategy · Hard
More questions from Anthropic
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovering and Sizing AI Opportunities
- Chapter 9: Measuring AI Product Economics
- Chapter 14: Interviewing for AI PM Roles