Full Mock: Strategy Round

This is a complete mock strategy round. Set a timer for 30 minutes and answer the question below. Then compare to the sample.

The question: 'You are the VP of Product at a Series C B2B SaaS company ($80M ARR, 300 employees). Your largest competitor just announced an AI-powered version of their product. Your CEO is asking for your AI strategy. What do you present?' This is a high-stakes strategy question that tests business acumen, competitive analysis, and AI strategic thinking.

"Before presenting a strategy, I need to assess three things. First, what did the competitor actually announce? There is a big difference between 'we added AI to our marketing website' and 'we rebuilt our core product on top of AI.' I would analyze their announcement, their product changelog, and early user reviews to determine the substance behind the marketing. In many cases, competitive AI announcements are more aspirational than operational."

"Second, what is the customer reaction? Are our customers asking for AI features? Are we losing deals because of the competitor's AI capabilities? Or is this a market perception issue where customers assume we are behind but have not actually needed AI features yet? I would pull data from our sales team (deal loss reasons), our customer success team (feature requests mentioning AI), and our product analytics (are users doing tasks manually that AI could automate?)."

"Third, what is our current AI readiness? Do we have the data, infrastructure, and talent to build AI features? At $80M ARR and 300 employees, our engineering team is probably 100-120 people. Our ML capability is probably 0-5 people. Our data infrastructure may or may not be ready for ML workloads. Understanding our starting position determines how aggressive we can be."

[Interviewer note: The candidate resisted the urge to jump into strategy immediately and instead set up a structured situation analysis. The three assessments (competitive reality, customer demand, internal readiness) are exactly the right starting point. The skepticism about competitive announcements ('more aspirational than operational') shows market maturity.]

"Based on this analysis, here is the strategy I would present to the CEO. It has three pillars: Defend, Differentiate, and Build the Foundation."

"Pillar 1: Defend (Months 1-3, budget: $500K). Ship 3-4 AI features using foundation model APIs that address the most visible competitive gap. Focus on features customers are actively asking for: AI-powered search across the platform, automated data entry and form filling, and natural language reporting ('show me last quarter's top accounts by revenue'). These features use off-the-shelf LLM capabilities and can be built by our existing product engineering team in 2-4 weeks each. The goal is not competitive differentiation; it is table-stakes parity. If customers see our competitor has AI and we do not, we lose deals on perception alone."

"Pillar 2: Differentiate (Months 3-9, budget: $2M). Build 2-3 AI features that leverage our proprietary data to create a competitive moat. Unlike the Defend features, these cannot be replicated by a competitor using the same APIs because they depend on our unique data. Examples: predictive analytics that leverage our customers' historical data (churn prediction, revenue forecasting), automated workflow optimization based on how our most successful customers use the product, and anomaly detection that flags data quality issues before they cascade. These features require ML engineering investment and domain-specific models."

"Pillar 3: Build the Foundation (Months 1-12, budget: $1.5M). Invest in the infrastructure and talent to sustain AI innovation long term. Hire 3-4 ML engineers and 2 data engineers. Build a clean data pipeline, feature store, and experiment tracking. This is the most important pillar because without it, Pillars 1 and 2 are one-time efforts. With it, we can continuously ship AI features faster than our competitor."

[Interviewer note: The three-pillar strategy is clear, actionable, and well-sequenced. Defend addresses the immediate competitive threat. Differentiate creates a moat. Build the Foundation enables sustained advantage. The budgets and timelines are realistic. The distinction between API-based features (fast, no moat) and proprietary-data features (slower, defensible) shows strategic sophistication.]

"The key risks are: Execution risk: can we ship the Defend features in 3 months while simultaneously hiring and investing in infrastructure? I would mitigate this by keeping Defend features simple (API integrations, not custom models) and separating the teams. Talent risk: hiring 3-4 ML engineers in this market takes 4-6 months. I would start recruiting immediately and use contractor/consulting ML engineers for the first 3 months. Customer risk: AI features that do not work well are worse than no AI features. Every feature must meet a quality bar before launch. Better to ship 2 good features than 4 mediocre ones."

"Metrics I would report to the CEO quarterly: Win rate on competitive deals (should improve from current baseline within 6 months). Feature adoption rate for AI features (target: 30% of active users within 3 months of launch). Customer NPS impact (AI features should improve, not degrade, NPS). Incremental revenue attributable to AI features (track upgrades and retention tied to AI feature usage)."

Overall scoring: Business Acumen: 4.5/5. AI Realism: 4/5 (could have discussed specific model approaches for the Differentiate pillar). Quantitative Reasoning: 4/5 (budgets are specific, but a detailed ROI projection would improve this). Strategic Communication: 5/5 (clear three-pillar structure, well-paced, CEO-ready). Overall: 4.3/5 (Strong Hire).