Market Research and Competitive Landscape Questions
Broad market analysis capabilities including identifying major competitors, assessing market dynamics and pricing strategies, sizing markets using top down and bottom up approaches, validating customer pain points, and prioritizing opportunities. Encompasses competitor mapping, market sizing, trend analysis, and turning market research into strategic recommendations.
MediumTechnical
21 practiced
You have three personas: Solo Freelancer (low ACV, high volume), Small Agency (medium ACV, growth potential), Enterprise PMO (high ACV, long sales cycle). Given five candidate features (improved mobile UX, admin console, enterprise SSO, cheaper starter plan, analytics dashboard), describe a framework to score and prioritize these features using personas and revenue impact.
Sample Answer
Approach: use a weighted, persona-aware expected-value framework — combine (1) persona benefit, (2) revenue impact (ACV × volume × conversion uplift), and (3) development cost/effort and risk. Score each feature per persona, compute expected revenue uplift, then divide by effort to get a “prioritized ROI”.Steps:1. Define inputs- Persona metrics: Solo (volume V1, ACV A1), Agency (V2, A2), Enterprise (V3, A3).- Effort: estimate story points or T-shirt size → EffortScore.- Baseline conversion/retention rates.2. Scoring per persona- For each feature, estimate BenefitScore (0–10) for each persona (how much it increases acquisition/retention).- Compute ExpectedRevenueUplift = sum_over_personas(Vi * Ai * BenefitScore_i%). (BenefitScore% = BenefitScore/10 × plausible % lift, e.g., 5–25% scaled.)3. Weighted priority metric- PriorityScore = ExpectedRevenueUplift / EffortScore.- Optionally multiply by StrategicWeight if strategic (market positioning, platform).Example (illustrative):- Solo: V1=10k users/mo, A1=$10; Agency: V2=500, A2=$500; Enterprise: V3=10, A3=$50k.- Improved mobile UX: BenefitScores [8,4,1] → uplift ~$ (10k*10*0.08)+(500*500*0.04)+(10*50k*0.01)=8k+10k+5k=23k. Effort 5 → Priority 4.6- Enterprise SSO: [0,2,9] → uplift ~(0)+(500*500*0.02)+(10*50k*0.09)=0+5k+45k=50k. Effort 8 → Priority 6.25Action:- Compute numbers with real metrics, rank by PriorityScore.- Run sensitivity analysis on lift estimates and effort.- Validate with customer interviews and quick experiments (A/B or concierge).This balances persona needs, revenue impact, and execution cost for a data-driven roadmap.
EasyTechnical
37 practiced
Explain price elasticity of demand in plain terms and calculate elasticity given this example: you raise your mobile app subscription from $5 to $10 and the conversion rate drops from 8% to 6%. Show the calculation and interpret the result for pricing decisions.
Sample Answer
Price elasticity of demand measures how sensitive customers are to a price change: specifically, the percentage change in quantity demanded (here, conversions) divided by the percentage change in price. If elasticity > 1 (in absolute value), demand is elastic—customers respond a lot to price changes. If < 1, demand is inelastic—customers are less price-sensitive.Calculate using the midpoint (arc) method for a symmetric percentage:1) Change in price:- From $5 to $10 → ΔP = 10 − 5 = 5- Average price = (10 + 5) / 2 = 7.5- %ΔP = ΔP / avg = 5 / 7.5 = 0.6667 = 66.67%2) Change in quantity (conversion rate):- From 8% to 6% → ΔQ = 6 − 8 = −2 percentage points- Average conversion = (8 + 6) / 2 = 7%- %ΔQ = ΔQ / avg = −2 / 7 = −0.2857 = −28.57%3) Elasticity = %ΔQ / %ΔP = (−28.57%) / 66.67% ≈ −0.4286Interpretation and pricing decision:- Elasticity ≈ −0.43 (inelastic): the drop in conversions is proportionally smaller than the price increase.- Revenue per visitor = price × conversion rate: - At $5: 0.08 × $5 = $0.40 - At $10: 0.06 × $10 = $0.60- Revenue per visitor increased, and because demand is inelastic, raising price increased overall revenue.Actionable guidance:- Validate with A/B tests and cohort analysis (check churn, LTV, retention effects).- Examine customer segments: some segments may be more elastic.- Consider long-term impacts (e.g., lower acquisition, worse reviews) before making the change permanent.
HardSystem Design
23 practiced
Design a continuous competitive intelligence system for a mid-size SaaS company. Describe data sources to ingest (e.g., product pages, pricing, app-store updates, reviews), the ingestion and analysis pipelines, dashboards/alerts you'd build, roles who consume the outputs, refresh cadence, and a rough cost/complexity trade-off.
Sample Answer
Requirements & constraints:- Continuous, near-real-time CI for product, pricing, reviews, feature launches for a mid-size SaaS (global customers, ~$50–200M ARR). Low to medium budget; prioritize actionable signals for PMs, Sales, Marketing, Execs.High-level architecture:- Data sources: competitor product pages, pricing pages, docs/changelogs, app-store listings, release notes, public roadmap posts, social (Twitter/LinkedIn), review sites (G2, Capterra), job postings, SEC/press releases, web traffic/tech stack signals (BuiltWith), RSS/feeds.- Ingestion: lightweight crawler + API connectors (where available) -> message queue (Kafka) -> raw S3 data lake.- Processing: stream ETL (Flink/Glue) for parsing, de-dup, detect schema; NLP service for change detection, summarization, intent classification, sentiment; entity resolution to map competitors/products.- Storage: curated lake + OLAP store (Redshift/Snowflake) and Elasticsearch for search.- ML: change detection models, pricing normalization, feature extraction, topic modeling, trend detection.- Serving: dashboards (Looker/Metabase), alerting (PagerDuty/Slack/email), daily summary emails, searchable CI portal.Dashboards & alerts:- Executive weekly snapshot: market moves, big price changes, major launches.- Product feed: feature release diff, changelog highlights, sentiment trends.- Pricing watch: normalized price matrix, discounting alerts.- Win/loss + sales enablement: competitor mentions on deals, new integrations that affect positioning.- Alerts: immediate Slack for major breaking changes (pricing cut >X%, acquisition, major feature launch), daily digest for lower-priority changes.Roles & consumption:- PMs: product feed, feature-level alerts- Strategy/BD: M&A, partnerships, job-posting trends- Sales/RevOps: objection handling, battlecards, pricing alerts- Marketing: messaging shifts, campaign opportunities- Execs: weekly summary + strategic flagsRefresh cadence:- High-priority sources (pricing, app-store, docs): near real-time (5–15 min)- Reviews & social: hourly- News/press/jobs: daily or immediate for high-severity events- Aggregated reports: daily/weeklyCost / complexity trade-offs:- Low-cost (MVP): scheduled crawlers + PostgreSQL + simple diffs + Slack/email alerts. Low complexity, higher latency, manual triage.- Medium: add streaming ETL, NLP for summarization, Snowflake + BI. Better signal quality, moderate cost.- High-end: real-time pipelines, advanced ML for intent/signal scoring, enterprise search, dedicated CI portal — high cost but automates insight generation and scales for many competitors.Implementation plan (phased):1) MVP: crawl top 10 competitors, pricing/app-store, daily diffs + Slack alerts + simple dashboard (6–8 weeks).2) Scale: add streaming, review sentiment, normalized pricing, role-based dashboards (next 3 months).3) ML & automation: intent detection, anomaly scoring, CI portal + integrations to CRM (6–12 months).Key success metrics:- Time-to-detect critical events- % of alerts leading to actionable changes- Adoption: weekly active users (PMs, Sales)- Reduction in surprise product/price competition incidentsThis design balances business needs, speed of insight, and incremental investment.
MediumTechnical
30 practiced
Design an experiment to test willingness to pay for a new premium feature in a B2C mobile app. Detail cohorts, randomization, price points to test, primary metrics, minimum detectable effect or sample size considerations, and guardrails to avoid harming long-term revenue.
Sample Answer
Goal: measure true willingness to pay (WTP) for a new premium feature while protecting short- and long-term revenue and user experience.Experiment design (high level)- Hypothesis: A meaningful share of active users will convert to the premium feature at price X, increasing ARPU without harming retention.- Population: Active monthly users (used the app ≥1 session in last 30 days). Exclude recent trials or very new users (<7 days).Cohorts & randomization- Control (C): baseline experience, no premium upsell.- Treatment price arms (randomized, user-level, stratified): - T1: low price (e.g., $0.99/mo) - T2: mid price (e.g., $2.99/mo) - T3: high price (e.g., $6.99/mo)- Optional: T4 with mid price + premium messaging (value framing) to measure elasticities from messaging.- Randomize at user level; stratify by platform (iOS/Android), geography, tenure, and past spend to ensure balance.Offer & exposure- Single prominent in-app modal and store listing update (same UX across arms except price/messaging).- Limit exposure frequency (max 1 show per user per 7 days).- Run a short pilot (2 weeks) to validate instrumentation and crude signals.Primary metrics- Primary: conversion rate to paid (first purchase within 14/30 days).- Revenue metrics: ARPU, average revenue per payer (ARPPU), incremental revenue per user (IRPU).- Retention/engagement: 7/30-day retention, DAU/MAU of buyers vs. non-buyers.- Long-term: 90-day churn among converters, LTV projection.- Safety & perception: NPS or satisfaction survey for exposed users, refund rate/disputes.Minimum Detectable Effect (MDE) / sample size- Use two-tailed test, α=0.05, power=0.8. Conversion baseline example p0 = 2% (0.02). Want to detect relative lift of 20% (absolute Δ = 0.004).- Rough sample-size approximation per arm: n ≈ (Zα/2√(2p(1−p)) + Zβ√(p0(1−p0)+p1(1−p1)))^2 / Δ^2 Plugging p≈0.02, Δ=0.004, Zα/2=1.96, Zβ=0.84 gives n ≈ ~40,000–60,000 users per arm.- Practical step: compute exact sample with your analytics or online calculator and adjust price arms or test length if sample scarce. For rare events consider longer duration or coarser price buckets.Analysis plan & attribution- Pre-register primary metric and analysis window (e.g., 30 days).- Intention-to-treat analysis to avoid bias from selective exposure.- Adjust for multiple comparisons (Bonferroni or hierarchical testing) since several price arms.- Segment analysis: by cohort (new vs. existing payers), geography, device.Guardrails to avoid harming long-term revenue- Revenue cap: Hold out a revenue-protection cohort — e.g., 5% of high-LTV users never see cheaper offers.- Exposure limits and opt-in: do not force-charge; use clear UI and trial periods where appropriate.- Monitor leading indicators in real time: spikes in refunds, support tickets, app uninstalls, retention drops. Stop/roll back on pre-defined kill criteria.- Price anchoring: show original price or bundle to avoid training users to expect discounts.- Avoid permanent price leaks: keep buyer messaging consistent across channels; don't advertise test prices widely.- Post-test rollout: graduated rollout by segment, monitor LTV over 3–6 months before full-scale change.What I’d deliver cross-functionally- Experiment spec: cohorts, randomization, success metrics, kill-switches- Analytics dashboard: conversion, ARPU, retention, refunds, support volume- QA plan: instrumentation checks, payment flows validated- Legal/comms review: refund policy, store complianceThis provides statistically-powered answers to WTP while protecting revenue through holdouts, monitoring, and staged rollouts.
HardSystem Design
45 practiced
Design a forecasting model that blends top-down market growth and bottom-up pipeline/opportunity conversion to produce three scenarios (conservative, base, aggressive) with confidence intervals. List the inputs, how you'd estimate uncertainty, and how you would present the model to leadership for strategic planning.
Sample Answer
Requirements & objectives:- Produce three scenarios (conservative, base, aggressive) combining top-down market growth and bottom-up pipeline -> revenue/ARR forecasts with confidence intervals for next 12–24 months.- Explain inputs, uncertainty sources, propagation method, and presentable outputs for leadership to inform strategy.High-level approach:1. Hybrid model: scenario-weighted blend = α * TopDownForecast + (1-α) * BottomUpForecast, where α can vary by scenario and product maturity.2. Generate probabilistic distributions for both top-down and bottom-up components, then combine via convolution/sampling (Monte Carlo) to produce scenario percentiles and CI.Inputs- Top-down: - Total Addressable Market (TAM) & Serviceable Obtainable Market (SOM) growth rates (quarterly) - Market share assumptions per scenario - Macroeconomic indicators (GDP growth, industry indices) - Competitor moves and pricing trends- Bottom-up: - Active pipeline by stage, ARR/ACV per opportunity, close probability per stage, expected close date - Historical conversion rates, sales cycle times, average deal size, churn/expansion rates - Sales capacity (headcount, quota attainment), ramp plans, planned product launches/marketing campaigns- Calibration & priors: - Historical forecast error distribution by product/segment, seasonality factors, lead time- Business constraints: - Capacity limits, delivery timelines, contractual renewal calendarsEstimating uncertainty- For top-down: model market growth as a distribution (e.g., normal/log-normal with mean=market research forecast, sigma = consensus variance or historical volatility). Scenario definitions shift mean and sigma (conservative: lower mean, higher sigma).- For bottom-up: treat each opportunity as a Bernoulli/random variable with probability = calibrated stage conversion (use beta distributions to represent uncertainty). Model deal size as distribution (empirical or log-normal). Simulate time-to-close variability.- Combine with Monte Carlo: run 50k simulations sampling top-down growth and bottom-up outcomes; compute scenario percentiles (10th, 50th, 90th) → define conservative/base/aggressive mapping to percentiles (e.g., conservative = 25th, base = 50th, aggressive = 75th) or use scenario-specific α blending.- Incorporate correlated risks: model correlation between macro shocks and pipeline (e.g., downturn reduces close rates) via copulas or correlated random draws.- Validate: backtest model on past quarters to calibrate sigma and conversion distributions; report calibration metrics (coverage, bias).Scenario construction- Conservative: lower market growth, lower win rates, lower deal sizes, higher churn; α tilted toward top-down if pipeline weak.- Base: consensus market growth, calibrated conversion rates, expected product launches realized.- Aggressive: higher market growth, higher conversion uplift from campaigns, larger average ACV; α may favor bottom-up where high-confidence pipeline exists.Outputs & presentation to leadership- Dashboard / one-pager per scenario: - Key numbers: expected revenue/ARR per quarter, CIs (10–90%), probability of hitting target thresholds. - Waterfall decomposition: starting ARR → additions from closed-won → net expansion → churn → net ARR, with CI bands. - Contribution split: % from market expansion (top-down) vs. new pipeline (bottom-up). - Sensitivity analysis: tornado chart showing which inputs (market growth, close rate, deal size, churn) most affect outcomes. - Risk register: list of correlated shocks, time-to-mitigate, leading indicators to watch (win-rate, lead velocity, competitor actions). - Recommended actions per scenario: hiring changes, pricing experiments, go-to-market pushes, contingency triggers (e.g., if monthly win-rate drops 15%, move to conservative plan).- Visuals: fan charts for forecast intervals, stacked area charts for scenario comparisons, Monte Carlo density plots, and KPI trend lines with control limits.Operationalization- Data pipeline: automated ETL from CRM (opportunities), billing system (ARR), market research sources; scheduled Monte Carlo runs weekly/monthly.- Governance: versioned model with documented assumptions, ownership (analytics team product + finance), scheduled re-calibration and postmortems vs actuals.- Communication: 15–30 minute executive brief with 1-page summary + appendices (assumptions, sensitivity) and interactive dashboard for deeper exploration.Why this works- Blends strategic market view with actionable sales reality, quantifies uncertainty explicitly, provides leadership with both numbers and levers to act on. Backtesting and sensitivity make the model credible and operational.
Unlock Full Question Bank
Get access to hundreds of Market Research and Competitive Landscape interview questions and detailed answers.
Sign in to ContinueJoin thousands of developers preparing for their dream job.