Strategy question
North can only build a handful of integrations in the next 2 quarters. How would you prioritize the first wave across CRM, ITSM, productivity, data warehouses, knowledge stores, and identity, using customer demand, ARR potential, strategic leverage, and implementation cost? Be explicit about the framework, the inputs you’d require, and how you’d sequence quick wins vs. foundational bets.
- Cohere
- 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 structured prioritization across many integration candidates using multiple weighted inputs and a clear sequencing logic.
How to approach it
- Collect inputs for each candidate integration: customer demand volume, projected ARR impact, implementation cost, and strategic leverage such as data exclusivity.
- Score each candidate on those dimensions using a simple weighted framework rather than ranking by gut feel.
- Separate quick wins, low cost and high demand integrations like common CRMs, from foundational bets, higher cost integrations that unblock several future ones.
- Sequence a mix: ship one or two quick wins early for momentum and customer trust, while starting a foundational bet in parallel.
- Require input from sales and customer success on which integrations are actually blocking deals, not just requested in surveys.
- Set a checkpoint at the midpoint of the two quarters to reassess priority based on early adoption data.
What a strong answer includes
- Uses a named weighted framework with explicit inputs rather than an unstructured ranked list.
- Deliberately sequences a mix of quick wins and foundational bets instead of only chasing fast, visible wins.
- Requires deal blocking evidence from sales, not just survey demand, since survey demand can overstate willingness to pay.
Common mistakes
- Ranking integrations purely by how many customers asked for them without weighing implementation cost or strategic value.
- Choosing only quick wins and neglecting any foundational investment that would unblock future integrations faster.
Likely follow-up questions
- How would you handle a foundational bet that turns out to be twice as costly as estimated mid quarter?
- What would you do if the highest ARR potential integration also has the highest implementation cost?
More strategy questions
- Managed North needs to remove deployment complexity while still giving customers confidence on data residency, compliance, and reliability. How would you decide which capabilities are launch blockers versus post-launch investments, and what principles would you use to trade off speed to market against enterprise readiness?Cohere · Strategy · Hard
- Customer discovery shows most mid-market accounts prefer a simple multi-tenant deployment, but a smaller high-value segment requires stronger infrastructure isolation for compliance. Which deployment model would you launch first, and what data would you use to decide whether isolated infrastructure should be delayed, sold as an upsell, or not offered?Cohere · Strategy · Hard
- A strategic customer will expand if North ships a custom integration for a high-value workflow, but key primitives like auth, permissioning, or data sync are still immature. How would you decide what to build as a one-off to close the customer need versus what to invest in as reusable platform infrastructure, and how would you sequence that work?Cohere · Strategy · Hard
- Google Keep is a free product to save, share notes etc. How would you make it a subscription product & monetize it?Google · Strategy · Hard
- How would you launch (roll out) Amazon Go?Amazon · Strategy · Hard
- With an unlimited network bandwidth what would you build?Google · Strategy · Hard
More questions from Cohere
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