Strategy question
Assume you join Harvey tomorrow and have 60 days to shape the Command Center vision. How would you work with enterprise admins, security stakeholders, Sales, and Customer Success to identify the highest-value admin pain points, and how would you turn that input into a roadmap that executives and engineers will both support?
- 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 running fast discovery across multiple stakeholder types to shape a new product's vision and building a roadmap that wins both executive and engineering buy-in.
How to approach it
- In the first two to three weeks, run structured conversations separately with enterprise admins, security stakeholders, Sales, and Customer Success, since each surfaces different pain points.
- Look for overlap across groups: pain points named independently by multiple stakeholder types are the strongest early roadmap candidates.
- Weight security stakeholder input heavily for sequencing, since unresolved security concerns typically block deals regardless of how much admins or CS want other features.
- By day 30, synthesize findings into a small set of themes, not a long feature list, so the vision is communicable to both executives and engineers.
- By day 45, translate themes into a roadmap with named tradeoffs, what ships first and what is deferred, tested against both business impact and technical feasibility.
- By day 60, present the roadmap with the evidence trail visible, so executives see the business case and engineers see it is grounded in real technical scoping, not just aspiration.
What a strong answer includes
- Finds pain points named independently across multiple stakeholder types as the strongest signal, not just the loudest single voice.
- Weights security input heavily for sequencing, correctly reflecting its outsized effect on deal-blocking in enterprise legal sales.
- Presents the roadmap with a visible evidence trail so both executives and engineers can independently verify it is well-founded.
Common mistakes
- Talking to only one stakeholder type, like Sales, and missing security or admin pain points that actually block deals.
- Presenting a long feature list instead of a small set of synthesized, prioritized themes.
Likely follow-up questions
- How would you handle conflicting priorities between security and Sales?
- What would you do if 60 days is not enough to validate technical feasibility for a key theme?
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: Discovering and Sizing AI Opportunities
- Chapter 9: Measuring AI Product Economics
- Chapter 14: Interviewing for AI PM Roles