Interview Drills — GTM & Launch Strategy

Open-ended case questions of the "How would you launch this?" / "Take this feature to market" type — the take-home-case-and-present format of real PMM interviews. Each has a Framework (the structure a strong answer follows), a Model answer (a concise example), and a Rubric (what an interviewer listens for). Practice thinking aloud and always tie the plan back to a specific audience and a success metric defined in advance. The app can role-play these as mock interviews (see mock-interview.md).

The universal GTM structure: Clarify the goal and what's launching → pick a target audience/segment → nail positioning and the core message → choose a channel mix that matches where that audience is → decide pricing/packaging and timing → coordinate the cross-functional launch (product, sales, support, content) across before/during/after → define success metrics in advance. Use it on almost any "launch this" or "take it to market" question.

D1

difficulty: easy
concept: go-to-market-and-launches Walk me through how you'd launch a new product. What are the pieces of a GTM plan?
Framework: Name the components in order: clarify the goal → target audience/segment → positioning & core message → channel mix (matched to the audience) → pricing/packaging & timing → cross-functional coordination (before/during/after) → success metrics defined in advance. Show it's a connected plan, not a checklist.
Model answer: "I'd start by clarifying the goal — say, sign-ups in the first quarter — and the target audience. Then positioning: who it's for, the category, and the one benefit that makes it the best choice. That message drives the channel mix; I pick channels where that audience already is rather than blasting everyone. I decide pricing and a launch date, then coordinate across product, sales, support, and content for a before/during/after plan — prepare materials and brief teams, announce everywhere at once, then measure. And I'd define the success metric up front so we know if it worked."
Rubric: Strong answers cover audience → positioning → channels → pricing/timing → coordination → metrics as a connected plan and stress matching channels to the audience plus defining success in advance. Weak answers list random tactics ("run some ads, post on social"), skip audience and positioning, or never define what success means.

D2

difficulty: medium
concept: positioning-and-messaging Take this feature to market: our budgeting app just added automatic bill-splitting for shared households. Build the GTM plan.
Framework: Clarify the goal (adoption among existing users? new acquisition?) → pick the audience this feature serves → write positioning ("for [who] who [problem], this is [what] that [benefit], unlike [alternative]") → translate the feature into a benefit → channel mix → timing/coordination → success metric.
Model answer: "Goal: drive adoption among existing users in shared living situations and use it to acquire roommates of current users. Audience: people splitting rent and utilities — roommates and couples. Positioning: 'For people who share a household and hate chasing each other for money, our app now splits bills automatically so no one has to do the awkward math or the awkward ask.' That's the benefit, not the feature. Channels: in-app announcement and email to existing users (highest-intent), plus a referral hook since splitting is inherently multi-person, plus content like 'how to split rent fairly.' Timing: launch before the 1st of the month when rent is top of mind. Success metric: % of eligible users who create their first split, and invited-roommate sign-ups."
Rubric: Strong answers pick a specific audience, write real benefit-led positioning (not feature-dumping), choose channels that fit (in-app/email for existing users, referral for an inherently multi-person feature), tie timing to the audience's context, and name a metric. Weak answers describe the feature's mechanics, target "everyone," or pick generic channels with no rationale.

D3

difficulty: medium
concept: go-to-market-and-launches How would you decide the channel mix for a launch? Take a B2B project-management tool aimed at small agencies.
Framework: Start from the audience and where they actually are → consider product fit per channel (price point, complexity, sales motion) → propose a primary channel plus 1–2 supporting → say how you'd measure which works → note that you'd double down on winners. Match channels to audience and product, don't list all of them.
Model answer: "Audience: ops leads at small creative agencies — they research solutions and have a real but modest budget. For a B2B tool at this price, I'd lead with content/SEO targeting what they search ('how to manage agency projects'), because it compounds and builds trust, plus a light sales-assisted motion for demos. Supporting channels: partnerships with tools agencies already use, and targeted LinkedIn. I'd skip mass paid social — wrong audience intent. I'd measure conversion and CAC per channel and shift budget toward whatever brings qualified sign-ups cheapest. Referrals become a channel later once happy agencies refer peers."
Rubric: Strong answers reason from where this specific audience is and the product's price/complexity, pick a primary channel with justification, explicitly rule a channel out, and commit to measuring CAC/conversion and reallocating. Weak answers list every channel equally, ignore audience fit, or never mention measuring which channel works.

D4

difficulty: medium
concept: go-to-market-and-launches Lay out the launch coordination: walk me through the before / during / after of bringing a major feature to market.
Framework: Before → finalize positioning/messaging, prepare all materials (site, emails, blog, in-app, sales deck), brief and train sales and support, build anticipation. During → announce across all channels at once so the message lands everywhere, in one consistent story. After → measure against predefined metrics, gather feedback, fix issues, sustain momentum. Stress tight cross-functional coordination and one clear message.
Model answer: "Before: I lock the positioning and one core message, then produce every asset off it — landing page, announcement email, blog post, in-app banner, and a sales one-pager — and I brief sales and support so they can answer questions on day one. Build a little anticipation with a teaser. During: a coordinated announcement — email, social, blog/press, and in-app message all go out together so the same story lands everywhere at once, not a trickle. After: I track the metrics we set in advance — adoption, conversion, support tickets — gather feedback, fix what breaks, and keep momentum with follow-up content. A launch is a start, not a one-day event."
Rubric: Strong answers structure before/during/after, emphasize one consistent message across coordinated channels, explicitly include briefing sales/support, and treat the launch as ongoing (measure + sustain). Weak answers equate "launch" with a single announcement, forget internal enablement, or skip post-launch measurement and iteration.

D5

difficulty: hard
concept: go-to-market-and-launches Here's a take-home case: we're launching a free AI writing assistant and want to move users to a $20/month paid tier. Present your full GTM, including pricing/packaging and timing.
Framework: Clarify goal and constraints → target audience → positioning vs. alternatives → packaging (what's free vs. paid, and why) and pricing rationale → channel mix → launch timing/sequence → success metrics. Connect pricing/packaging to the funnel (free acquires, paid monetizes) and define both an adoption and a conversion metric.
Model answer: "Goal: grow a free top-of-funnel and convert a healthy share to $20/mo. Audience: solo professionals and small-team writers — marketers, founders — who write a lot and feel the time cost. Positioning: 'the writing assistant that sounds like you,' versus generic tools. Packaging: free tier generous enough to form a habit (limited monthly generations) with the paid tier unlocking volume plus the differentiator (custom voice, longer docs) — free acquires, paid monetizes. $20 sits at a familiar prosumer price point and clears value if it saves a few hours a month. Channels: content/SEO and product-led referrals to fuel the free funnel; in-product upgrade prompts at the moment users hit the free limit. Timing: launch free first to build a base, introduce paid once activation is strong. Metrics defined up front: activation (users who complete a first real doc), free-to-paid conversion rate, and CAC vs. the $20 LTV."
Rubric: Strong answers tie packaging to the funnel (free acquires, paid monetizes), justify the price against value and a reference point, sequence the launch deliberately, and predefine both an adoption and a conversion metric (plus LTV vs. CAC awareness). Weak answers set price arbitrarily, give everything away or gate the wrong things, ignore timing/sequence, or name only a vanity metric like total sign-ups.

D6

difficulty: hard
concept: go-to-market-and-launches Your last feature launch flopped — low adoption despite a big announcement. As the PMM, how would you diagnose what went wrong and what would you do differently?
Framework: Resist blaming one thing → diagnose against the GTM pillars in order: was the audience right, the positioning/message clear and benefit-led, the channels matched to that audience, the timing sensible, the coordination tight (sales/support briefed, message consistent)? → use the metrics to localize the break in the funnel (no traffic vs. traffic-but-no-conversion vs. sign-up-but-no-use) → propose a specific fix and how you'd validate it. Stay humble and data-led.
Model answer: "I'd start from the funnel data to localize the break. If awareness was high but adoption low, the problem is likely message or fit, not reach — maybe we led with the feature instead of the benefit, or targeted the wrong segment. If even awareness was low, the channels didn't match where the audience is. I'd check whether sales and support were actually briefed — a sloppy hand-off undermines a great product. Say the data shows people saw it but didn't try it: that points to weak positioning. I'd rewrite the message benefit-first, re-target the segment that has the underlying pain, relaunch through in-product and email where intent is highest, and define a clear adoption metric to judge it. I'd validate the new message with a few users before relaunching rather than guessing."
Rubric: Strong answers diagnose systematically across audience/positioning/channels/timing/coordination, use funnel metrics to localize the failure rather than guessing, propose a specific evidence-based fix, and stay humble about validating. Weak answers blame a single cause without evidence, jump to "we needed more ads," or never use the metrics to figure out where the funnel actually broke.