Strategy question

Claude has web, mobile, and desktop surfaces, plus free and paid plans. If you had the next two quarters to move growth, how would you identify the highest-leverage opportunities across acquisition, activation, retention, and monetization, and how would you prioritize them into a roadmap?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests growth prioritization across the full acquisition, activation, retention, and monetization funnel for a multi-surface subscription product.

Map current performance at each funnel stage across web, mobile, and desktop to find where the biggest absolute drop-off or biggest gap versus benchmark sits.
Size the opportunity at each candidate stage, for example estimating incremental paid conversions from a retention fix versus an acquisition channel expansion.
Weigh speed to impact, since activation and retention fixes often show results faster than acquisition channel bets that take a quarter to mature.
Prioritize one or two high-leverage bets rather than spreading effort thin across all four funnel stages simultaneously.
Sequence the roadmap with the fastest, highest-confidence win first to build momentum, then a bigger, riskier bet in the second quarter.

Uses actual funnel data to find the stage with the biggest opportunity instead of assuming acquisition is always the highest leverage lever.
Sizes each opportunity with a rough quantitative estimate, for example the incremental paid users from closing a specific activation gap.
Explicitly weighs speed to impact given only two quarters, favoring faster-to-prove bets like activation over slower acquisition channel experiments.
Commits to one or two bets rather than a scattershot roadmap touching every stage lightly.

Defaulting to acquisition-focused growth tactics without checking whether retention or activation has the bigger leverage.
Proposing too many parallel initiatives across all four stages instead of focusing limited two-quarter capacity.

How would you decide between a mobile-specific fix and a cross-platform one?
What would you do if the highest leverage opportunity required a slow-moving platform change?