How would you structure your growth team's experimentation portfolio?
Capital allocation across risk classes in growth.
3 asset classes (iterative 30-70%, tech investments, big bets 20-40%), use expected value per week, and evolve the mix.
Gut voting or flat effort without expected ROI.
What's really being asked
This question tests whether you view engineering time as a finite capital pool that must be allocated across investments with different risk and return profiles. The interviewer wants to see portfolio thinking rather than a flat backlog of ideas. They are looking for familiarity with expected value calculations, the ability to balance short term output against long term optionality, and the judgment to shift that balance as the product and market mature.
The full answer
A strong response names the three asset classes from growth portfolio theory and gives their typical success rates. First, iterative experiments in established areas usually win 30-70% of the time and provide steady returns. Second, investments in tech or user experience do not always move metrics immediately but increase future velocity or protect brand reputation. Third, big bets such as new channels or onboarding overhauls succeed only 20-40% of the time yet can transform the trajectory of the business. The answer should then describe a rigorous selection process that replaces democratic brainstorming votes with an expected value formula per engineering week, specifically probability of success multiplied by incremental impact divided by engineering cost. It should also note that a small gain at the top of a core funnel usually beats fixing a broken edge flow, and that the portfolio mix should evolve over time as the product matures and the highest leverage iterative opportunities are exhausted.
The mistakes people make
Candidates often say they would let the team vote on ideas or prioritize whatever feels most exciting, which ignores opportunity cost and confuses activity with impact. Another red flag is treating all experiments as equal without distinguishing between iterative optimizations and strategic bets. Some candidates also forget tech and UX investments entirely, focusing only on experiments that directly move a metric this quarter and leaving the team slower or the brand degraded over time.
What usually comes next
An interviewer might ask how you would estimate the probability of success for a project that has no historical precedent. They could also ask what percentage of the portfolio you would allocate to big bets in year one versus year four, or how you would defend a UX investment that slightly hurts a growth metric. Be ready to discuss how you would build a tooling investment that compounds experiment velocity.
A concrete example
Suppose your team wants to improve email reactivation. An iterative experiment might test a new subject line that you expect to lift open rates by 5%; with a 60% chance of success and one week of work, the expected value is high. A tech investment might be building automated copy localization so future email experiments launch in ten markets instead of one; it has no immediate user gain but doubles experiment surface area for the next year. A big bet might be replacing the entire email preference center to create a new personalized send-time feature; it takes six weeks and has a 30% chance of a 15% lift, but if it works it opens a durable new growth loop. You would score all three with the same expected value per week metric and fund the highest ROI mix.
Interview question
As a product matures and high-leverage iterative opportunities are exhausted, how should the experimentation portfolio evolve?
- a.Democratize idea selection through team voting to surface the most exciting opportunities
- b.Maintain a fixed allocation to preserve predictable output and stakeholder confidence
- c.Shift resources toward big bets and tech investments while rigorously scoring expected value per engineering weekCorrect
- d.Increase iterative volume targeting edge flows and secondary metrics to sustain short-term wins
Why? this is the answer
The card states that the mix must evolve as iterative opportunities are exhausted, shifting capital toward big bets and tech investments while still scoring expected value per engineering week. Option D is tempting because increasing test volume feels productive, but the card notes that edge-flow gains usually lose to core-funnel optimizations and that flat backlogs ignore opportunity cost.
Just read this? Test yourself on what you have been reading.
Read the original → jwegan.com
- #growth
- #experimentation
- #portfolio
- #expected value
- #leadership
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on growth — each one lists the topics its interview covers.
See open roles