Strategy question
A Fortune 500 customer asks Scale to build a GenAI copilot on proprietary data, but the executive sponsor is split between sales enablement, advisor workflow, and business intelligence. In your first 2-3 weeks, how would you identify the highest-value wedge, quantify the opportunity, and turn that into a product strategy and phased roadmap both the customer and Scale can commit to?
- Scale AI
- 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 identifying the highest-value wedge among three plausible use cases under executive disagreement, and converting that into a phased roadmap both sides can commit to quickly.
How to approach it
- In week one, interview the three stakeholder groups, sales enablement, advisor workflow, and business intelligence leads, to map each use case's frequency, current pain, and how directly it ties to revenue or cost.
- Quantify the opportunity for each: for sales enablement, time saved per rep per week; for advisor workflow, faster case resolution; for business intelligence, decision-making speed or accuracy improvement, using rough but defensible estimates.
- Assess feasibility with the available proprietary data for each use case, since a copilot is only as good as the data it can access, and one use case may have much cleaner data than another.
- Pick the wedge with the best combination of quantified value, data feasibility, and executive-sponsor enthusiasm, likely sales enablement if it has the clearest data and fastest measurable ROI.
- Propose a phased roadmap: a narrow pilot on the chosen wedge in the first month, with the other two use cases explicitly sequenced as phase two and three, not abandoned.
- Present the roadmap with the quantified opportunity sizing to get executive sponsor buy-in, framing deferred use cases as next, not no.
What a strong answer includes
- Quantifies each use case with a concrete, if assumption-based, value estimate instead of picking based on executive sponsor volume alone.
- Weighs data feasibility explicitly, recognizing a copilot's quality depends on data access, which can differ sharply across use cases.
- Frames the two deferred use cases as sequenced phases rather than rejected ideas, keeping all three sponsors engaged.
- Moves from discovery to a committed phased roadmap within the stated 2 to 3 week window, showing decisiveness under ambiguity.
Common mistakes
- Picking the wedge based on which sponsor is most senior or vocal rather than quantified value and feasibility.
- Spending the full 2 to 3 weeks in discovery without converging on a committed roadmap.
- Treating the two deprioritized use cases as rejected instead of sequenced, risking those sponsors disengaging.
Likely follow-up questions
- How would you validate your value estimates before committing to the wedge?
- What would you do if the executive sponsor disagrees with your chosen wedge?
More strategy questions
- You've shipped a bespoke Text2SQL workflow for one large customer, and leadership wants to know whether it should become a repeatable product. What criteria would you use to decide which components should be standardized into reusable software, which should stay configurable, and which should remain fully custom?Scale AI · Strategy · Hard
- You own pay and incentives for Scale's global contributor marketplace. How would you design a compensation and incentive system that improves fill rates for scarce skills while protecting gross margin and data quality? Include how you'd segment contributors, set base pay versus bonuses, and guard against gaming or unintended quality regressions.Scale AI · Strategy · Hard
- During task construction, Scale may uncover live vulnerabilities or handle sensitive offensive artifacts. How would you design the responsible-development and release process for this portfolio, including containment, coordinated disclosure, access controls, artifact handling, and customer vetting? Where would you set hard launch gates versus case-by-case exceptions?Scale AI · Strategy · Hard
- Scale is standing up a net-new cybersecurity portfolio. How would you choose the first 2-3 capabilities to launch across vulnerability discovery, exploit reproduction, patch validation, secure code review, malware analysis, and incident triage? Walk through the prioritization framework you would use, including customer value, execution difficulty, benchmark credibility, and dual-use risk, and explain what you would explicitly defer from v1.Scale AI · Strategy · Hard
- Two near-term customer commitments pull the platform in different directions: one requires stronger auth and secure-by-default deployment into a constrained environment, while another needs better agent runtime primitives to improve forward-deployed team velocity. Engineering capacity is fixed and both asks are only partially specified. How would you sequence the work, what framework would you use to make the call, and how would you explain that decision differently to platform engineers, FD PMs, and executives?Scale AI · Strategy · Hard
- You see repeated workflow friction across multiple enterprise deployments. How would you convert those field observations into a product recommendation that a core platform team can act on? Be specific about the evidence, segmentation, counterfactuals, and tradeoffs you would present to show this is a durable platform gap rather than one customer's preference.Scale AI · Strategy · Hard
More questions from Scale AI
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