Strategy question
Vault underpins how law firms store and use sensitive documents in Harvey. How would you define Vault’s product vision and a 12-month roadmap across ingestion/file management, search and Q&A, extraction, and secure sharing? Walk through how you’d segment customer needs, choose platform vs. feature investments, and handle high-priority requests from top firms without fragmenting the product.
- Harvey
- 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
Tests long range product vision and roadmap sequencing across four distinct capability areas while handling high priority pressure from top accounts.
How to approach it
- Segment customer needs by firm size and practice area, since a large firm's ingestion and permissions needs differ sharply from a smaller firm's search and Q&A priorities.
- Sequence ingestion and file management first, since search, Q&A, and extraction are only as good as the underlying document access and permissions foundation.
- Layer search and Q&A next, since it delivers the clearest day to day value once ingestion is solid.
- Sequence extraction and secure sharing later, treating them as higher value adds once the core platform is trusted and adopted.
- Choose platform investments, like a unified permissions model, over one off features when a request would otherwise fragment the product across firms.
- Handle high priority requests from top firms by mapping them against the roadmap sequence, fast tracking only requests that also serve the platform investment, and negotiating timeline on the rest.
What a strong answer includes
- Sequences foundation, ingestion and permissions, before higher layer features, which reflects the real technical dependency in a document platform like Vault.
- Distinguishes platform investments from one off feature requests explicitly, protecting the roadmap from fragmenting under pressure from top firms.
- Gives a concrete method for handling top firm pressure, mapping requests against the existing sequence, rather than just deprioritizing everyone equally.
Common mistakes
- Building search, Q&A, and extraction features before the underlying ingestion and permissions foundation is solid.
- Fragmenting the product roadmap by building one off features for every high priority request from a top firm.
Likely follow-up questions
- How would you say no to a top firm's one off feature request without damaging the relationship?
- What would make you accelerate secure sharing ahead of extraction in the roadmap?
More strategy questions
- How should Harvey price for law firms vs. in-house legal teams?Harvey · Strategy · Hard
- How would you grow Harvey adoption among conservative, risk-averse law firms?Harvey · Strategy · Hard
- You inherit Vault with strong customer interest but limited engineering capacity. How would you set Vault’s product vision and a 12-month roadmap across file management, AI search/Q&A, document extraction, secure sharing, and platform investments like permissions, indexing, and integrations? Walk through your prioritization framework, major bets, and what you would explicitly defer.Harvey · Strategy · Hard
- Harvey can fund only one major integration track next: deeper iManage support, broader SharePoint coverage, or cross-platform capabilities like sync, permissions mapping, and admin controls. How would you decide what to build first, and what tradeoffs would you make across customer demand, implementation effort, security risk, and strategic leverage?Harvey · Strategy · Hard
- Harvey’s Command Center needs to serve three jobs for enterprise admins: understanding adoption, managing users and access, and enforcing governance. How would you define the product strategy and first 12-month roadmap for Command Center, and what framework would you use to make trade-offs across those three areas for Harvey’s largest legal customers?Harvey · Strategy · Hard
- You inherit a platform where teams lack visibility into request failures, latency regressions, customer-impacting incidents, and model-quality degradation. How would you define the product scope for observability, decide what to ship first, and ensure the work improves customer outcomes rather than just adding internal tooling?Harvey · Strategy · Hard
More questions from Harvey
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 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop