🚢The Product Execution Interview
'How would you ship X?' Tests project sense, trade-offs, communication. The interview type most likely to surface real PM craft.
Execution interviews are where senior candidates differentiate. The structure is the same as product sense; the depth and trade-off explicitness is where you score points.
An execution interview asks how you'd ship a specific feature or initiative. Strong answers cover: problem definition, success metrics, scope decisions, milestone plan, dependencies and risks, stakeholder communication, and post-launch measurement. Senior candidates handle the unhappy paths (slipping deadlines, scope cuts, sales escalations) without prompting.
The execution answer structure (15-20 min)
1. Clarify (2 min). What problem are we solving? Who's it for? Any constraints (timeline, team size)?
2. Success metric (1 min). Define what 'shipped successfully' means. Primary + guardrails.
3. Scope (3 min). What's in v1, what's NOT. Reasoning. Acknowledge the trade-off.
4. Plan (3 min). Milestones over the next 4-12 weeks. Discovery, build, launch phases.
5. Dependencies (2 min). Engineering, design, legal, sales — what do you need from each.
6. Risks (2 min). Top 3 things that could go wrong. Mitigation for each.
7. Stakeholders (2 min). Communication plan. Cadence and audience.
8. Post-launch (1 min). How you'll measure and what success vs failure looks like.
Common prompts
- How would you launch a paid tier for [free product]?
- A new competitor just launched a feature you don't have. What do you do?
- Your team has 8 weeks to build X. Walk me through the plan.
- You inherited a team with no roadmap. First 90 days?
- How would you turn around a feature with 5% adoption?
What separates A from B answers
- A: Explicit scope decisions and trade-offs. "v1 is X and explicitly NOT Y because Z."
- B: Tries to do everything. Doesn't make the trade-off.
- A: Names specific risks and mitigations. "Engineering says vendor API is unreliable; we'll build a fallback for week 1 and switch vendors by week 6 if needed."
- B: Generic 'we'll mitigate risks.'
- A: Cross-functional thinking. "Marketing needs the launch narrative by week 4 to ship docs by week 8."
- B: PM-centric plan.
- A: Pre-mortem on the unhappy path. "If engineering slips by 2 weeks, we cut feature Y and ship the smaller v1.0."
- B: Assumes everything goes well.
Watch-outs
- Don't get lost in the build details. You're a PM, not an engineer. Stay at the right level.
- Don't skip the post-launch. Interviewers care that you measure and iterate.
- Acknowledge stakeholders. Sales, support, marketing will come up — pre-empt.
- Time-box. 20 min total. Don't ramble through 10 min of clarifying questions.
The senior twist
For senior PM interviews, expect a follow-up: 'now imagine 3 weeks into the build, sales escalates that they need feature X for a major deal that's not in scope.' Strong candidates handle gracefully — surface the trade-off, propose options, decide.
Real-world examples
Meta's PM interview is heavy on execution — they're hiring PMs to ship at scale with high stakeholder load. Strong execution answers (specific, trade-off-explicit, cross-functional) clear the loop reliably.
Go deeper — recommended reading
Interview questions (2)
Q1How would you launch a paid tier for a free product?executionsenior▼
Clarify. What product, what's the company stage, what's the current monetization? I'll assume mid-stage SaaS, currently free for individuals, 100K active users.
Success metric. 5% of active users on paid tier within 90 days, with no churn lift on free.
Scope. v1 = three-tier pricing (Free, Pro $20/mo, Team $50/mo per seat). Pro adds X, Y, Z features. Explicitly NOT in v1: enterprise tier, annual contracts, granular permissions.
Plan (12 weeks).
- W1-2: pricing research, packaging finalization
- W3-4: payment integration (Stripe), billing flow
- W5-7: upsell UX (paywall placement, comparison page)
- W8: internal alpha; pricing page A/B test on traffic
- W9-10: limited beta with 1K users
- W11-12: full launch + marketing push
Dependencies. Engineering (payment integration), design (paywall + pricing page), marketing (launch comms), legal (terms + refund policy), support (training on billing issues).
Risks.
- Existing power users churn rather than pay. Mitigation: grandfather the most engaged 1K users for 12 months.
- Paywall placement hurts free engagement. Mitigation: A/B test placement; revert if engagement drops >10%.
- Pricing too high / too low. Mitigation: Van Westendorp research pre-launch; willing to adjust in week 4 if conversion is off.
Stakeholders. Weekly update to CEO, biweekly to broader team. Sales briefed on what's launching (even if no sales motion yet) to handle inbound. Customer success ready for billing questions.
Post-launch. Track weekly: paid conversions, free retention, churn rate, ARPU, NPS. Decision gates at week 2 (initial conversion rate), week 4 (cohort retention), week 12 (overall metric vs target).
If by week 4 we're at <2% paid conversion, revisit pricing or paywall placement immediately. If churn on free is up >10%, soften the paywall.
Q2You inherit a team with no roadmap. Walk me through your first 90 days.executionsenior▼
Days 1-30: Listen + learn.
- 20 customer interviews
- 1:1 with every team member (engineering, design, EM)
- 1:1 with adjacent stakeholders (sales, support, marketing, leadership)
- Data deep dive: top metrics, recent launches, what's working/not
- Read all existing docs (PRDs, strategy, post-mortems)
Days 30-60: Synthesize + draft.
- Write a 1-pager strategy: where we are, where we're going, the bet, what we won't do, success metric
- Draft a 90-day roadmap (3-5 bets) based on what I've learned
- Pressure-test with team and stakeholders. Iterate.
Days 60-90: Commit + execute.
- Publish the strategy and roadmap
- Kick off the first 2 bets
- Establish operating rhythm: weekly team sync, biweekly stakeholder update, monthly metrics review
- Set up first quarter OKRs
Communication throughout.
- Week 2: send 'here's what I'm hearing' update to team + leadership
- Week 6: share draft strategy for input
- Week 10: publish committed strategy + roadmap
What I avoid.
- Making big calls in week 1 (no credibility yet)
- Killing existing work without diagnosing why it's there
- Promising leadership specific deliverables before I've done discovery
Failure modes to avoid.
- Discovery without commitment (90 days of listening, no action)
- Commitment without discovery (roadmap from gut, team unconvinced)
- Skipping stakeholder management (sales blindsided)
By day 90, the team should have a clear strategy, 3-5 bets in flight, and trust that the new PM has a plan.