2 min lesson
Cross-functional & data rounds
Answer this as if it were happening now: "Three teams want three different things from you this quarter. How do you decide what to build and how do you de-risk it?" Say what supports your choice.
Step 1 of 2
Two rounds that test the other half of the job: scoping the right work with Marketing, Growth, Data and Eng and proving it worked with data. Building is necessary; choosing what to build and measuring it is what scales.
Start from the outcome a stakeholder wants, not the tool.
Write a one-page spec; get the owner to confirm it.
Ship a thin slice to de-risk before the full build.
When three teams want three things, rank by impact.
Prefer a primitive that serves several programs.
Say no with a reason and a sequence, not a flat refusal.
Feed sales/product outcomes back into scoring.
Recalibrate routing thresholds from what converted.
Make the dashboard the source of the next decision.
On the panel, the trap is sounding like an order-taker or an empire-builder. Show cross-functional humility: you partner to find the most impactful fix and you de-risk with a thin slice before committing the team.
“When Marketing, Growth and the SDR lead each wanted something different, I didn't pick by who asked loudest. I scored each by impact - how many programs it would serve and how much toil it removed - and the winner was a shared routing primitive all three could reuse. I shipped a one-segment version first so we'd learn before building the general one.”