You're halfway through a Meta PM interview, and the VP leans in: "Your users come from Instagram, Facebook, and WhatsApp. They share a single goal: launching a paid event. Define the metrics—and their priority—for this cross-product journey." Your chest tightens. This isn't a single-product metric question; it's a system-of-systems challenge. Having prepped ~40 PMs for FAANG interviews—and served as a hiring chair at Google—I've seen exactly two types of answers: the generic "DAU and retention" (fail) and the insider approach that lands offers. Here's how you deliver the latter.
The Framing Trap: Why "North Star" Is a Trap in Cross-Product Spaces
Most candidates start by naming a single North Star metric: "Revenue per user" or "Weekly active users." In a cross-product journey, that's like optimizing for speed in a relay race by only timing the last runner. The real trick? Define metrics per leg of the journey, then weight them by dependency.
Insider example: At Google, I worked on a cross-product flow where users discovered a YouTube video via Search, then installed the Google Home app to cast it to a TV. Our early mistake was optimizing for "YouTube watch time"—it ignored the handoff to Home. The right framing came from a VP's brutal question: "Which metric, if it fails, makes the whole pipeline fail?" That's your gating metric.
For your interview, use this structure:
- Awareness metric (how many users start the journey)
- Transition success rate (the % who move from Product A to B)
- Completion metric (the end-state goal, e.g., checkout, subscription)
- Symptom metric (leading indicator that something is broken, e.g., time to move from step 2 to 3)
Concrete example: Spotify's cross-product journey from Free tier (app) to Premium (web checkout) to Family plan (account page). The gating metric isn't Premium signups—it's "click-through rate on the 'Try Premium' CTA from the app." Below 12%? You're dead in the water, no matter what the landing page does.
The HEART + RICE Hybrid: Metrics with Teeth (Not Just Vibes)
Kerry Rodden's HEART framework (Happiness, Engagement, Adoption, Retention, Task Success) is a great starting point, but it's too broad for cross-product. You need to overlay RICE (Reach, Impact, Confidence, Effort) to prioritize which metrics to move first.
How to execute in an interview:
- Map each product's HEART dimension to the cross-journey step. Example: "For the Instagram discovery step, Engagement (shares per session) matters. For the WhatsApp booking step, Task Success (error rate on payment) is critical."
- Then apply RICE: "Given our team of 8 engineers, we estimate moving Instagram's share rate from 4% to 6% (Impact: Medium) with 3 sprints. But improving WhatsApp's payment error rate from 9% to 2% (Impact: High) requires only 1 sprint (Effort: Low). We prioritize WhatsApp first because the Confidence score is higher—we've seen similar flows at Airbnb reduce abandonment by 30%."
Real numbers from a DoorDash interview I coached: The candidate framed a cross-product journey (Dasher app → Merchant portal → Customer app for tracking). She proposed a "friction score": average time between "order placed" and "Dasher assigned." It was a single number that gated all three products. The interviewer's feedback: "You didn't just list metrics; you showed which levers to pull first." That's the difference between a pass and a strong hire.
The "Handoff Matrix": A Tool Most Candidates Don't Know
Here's a framework I learned building Google Photos ↔ Drive integration. Draw a 3x3 grid: rows are each product (Instagram, WhatsApp, Facebook), columns are the journey steps (Discovery, Conversion, Post-Purchase). In each cell, write the one metric that matters—but only the metrics that cross products. The diagonal cells (product's own metrics) are interesting, but the off-diagonal cells are where the interview gold lives.
Example matrix for a hypothetical Uber Eats + Uber Rides cross-promotion:
| Discovery (app A) | Conversion (app B) | Post-purchase | |
|---|---|---|---|
| Uber Rides | Riders who see food ad in ride (Reach) | Riders who click "Order now" and open Eats (Transition rate) | Riders who order within 30 min of ride end (Attribution) |
| Uber Eats | Eaters who see ride promo in checkout (Reach) | Eaters who click "Ride home" and open Rides (Transition rate) | Eaters who take ride to pick up food (Cross-funnel) |
The single most predictive metric? Transition rate from product A to product B. In an interview, say: "I'd focus 70% of my analysis on transition rates, because that's where product-specific silos break. If our transition rate from Rides to Eats is below 5%, the whole campaign fails."
The "OKR Layer": How to Avoid the "Vanity Metric" Trap
Every candidate blabbers about ARR or MAU. In cross-product, vanity metrics are poison—because they can look good while the journey is dying. For example, Instagram might report a 20% increase in shares (a vanity "win"), but if 80% of those shares never result in a WhatsApp message, you've got a leaky bucket.
Use this specific OKR structure:
- Objective: "Deliver a unified onboarding experience that reduces time-to-value for new paid event creators."
- Key Result 1: "Increase cross-product transition rate (Instagram → WhatsApp) from 8% to 15% by Q3."
- Key Result 2: "Decrease average time from first Instagram post to event purchase completion from 4.2 hours to 1.5 hours."
- Key Result 3: "Maintain per-product NPS >70 during migration (guardrail)."
Why this works in an interview: It shows you understand trade-offs. KR3 is a guardrail—if cross-product improvements hurt Instagram's standalone NPS, you stop. That's product maturity.
Salary reality check: At Meta, PMs who ace this question at E5 level land offers around $250k–$320k (base + RSU). At Google L5, expect $230k–$290k. But the real multiplier? The ability to define cross-product metrics gets you fast-tracked to Staff PM (L6), where total comp crosses $450k. I've seen exactly two candidates get Staff offers in 2023—both aced this question by using the handoff matrix above.
The "Failed Interview" Anecdote (Don't Be This Person)
A few years back, I debriefed a candidate at Google who was otherwise stellar. She answered a cross-product metrics question about YouTube + Google Photos (users record video on YouTube app, edit it, then share from Photos). Her mistake: She proposed "total video views" as the top metric. That's an obvious choice—and wrong. Why? Because the cross-product journey is about editing and sharing, not views. Views happen on YouTube; editing happens on Photos. The metric she needed was "edits completed per active YouTube creator" —a cross-product ratio.
Her rejection reason: "Candidate defined single-product metrics in a cross-product question. Did not demonstrate systems thinking." Don't be that candidate. The golden rule: If your metric can be measured inside one product's dashboard, it's probably the wrong metric for a cross-product journey.
The One Takeaway: Define Your "Gating Metric" Before the Interview
Before you walk into any PM interview, write down the one metric that, if it fails, makes the entire cross-product journey collapse. For a payments flow (Venmo → PayPal → bank), it's transaction success rate. For a content funnel (TikTok → Shopify → checkout), it's add-to-cart rate from the TikTok link. For a gaming ecosystem (Steam → Discord → Twitch), it's "invites sent via Discord from Steam game sessions."
In the interview, say: "I define success as the system's ability to move a user from product A to B without dropping off. My primary metric is the 'handoff completion rate'—the % of users who start in product A and reach the intended state in product C. Secondary metrics are per-product health: session duration in A, error rate in B, and retention in C. But I'll prioritize the handoff rate because it's the only metric that integrates all three products."
That's the answer that gets your resume to the top of the pile—and your salary to the top of the band.
Want to practice? Download my free cross-product metric grid template at [fakelink]. Or, better yet—take out a blank piece of paper and map the journey from "opening a dating app" to "going on a date" across three products (e.g., Hinge, Uber, OpenTable). That's your interview homework.