How would you estimate user base for a new feature before coding?
Sizing an opportunity with proxy data before coding. A strong answer defines the behavioral profile, then triangulates internal segments, competitor analogs, and market data to bound the estimate with stated assumptions.
What's really being asked
This question tests whether you can de-risk product bets with data before committing engineering time. Interviewers want to see that you understand how to construct proxy audiences, triangulate multiple data sources, and communicate uncertainty. It is not about getting the exact number right; it is about demonstrating structured thinking and business pragmatism.
The full answer
First, define the behavioral profile and the job-to-be-done so you know what signal to proxy. Second, identify internal analogs such as adoption curves from similar features or adjacent user segments already in your data warehouse. Third, layer external proxies including competitor public metrics, industry reports, and demand signals like search volume or social listening. Fourth, synthesize these into a bounded range using a top-down TAM sanity check and a bottom-up funnel with assumed conversion rates at each step. Fifth, explicitly state your assumptions and confidence intervals so stakeholders understand the error bars.
The mistakes people make
A major red flag is insisting that no estimate is possible without shipping an MVP first. Another weak pattern is relying solely on gut instinct or executive opinion without any data anchor. Giving a single point estimate without ranges or assumptions is also problematic because it hides uncertainty. Finally, using only one data source, such as just a survey or just a competitor press release, shows a lack of triangulation discipline.
What usually comes next
The interviewer may ask how you would validate the proxy after launch, how you would prioritize this feature against others with firmer data, or what you would do if internal analogs do not exist. They might also probe how you would adjust the estimate if the feature targets a niche B2B audience rather than a broad consumer market.
A concrete example
Suppose you are launching a hard seltzer brand and no direct consumer data exists yet. Following the proxy audience framework, you would first build a lifestyle audience around demographics and psychographics of health-conscious younger drinkers. If the segment is niche, you would layer in publications and influencers they follow. If you are an established brewery looking at growth, you would start with competitor seltzer audiences and refine them with your existing customer demographics and consumption data. You might then cross-reference this against search trend volume and liquor-store category growth reports to bound the market size before producing a single can.
Interview question
Which approach best demonstrates how to estimate user base for a new feature before coding begins?
- a.Run a broad user survey and use the raw number of interested respondents as the projected user base
- b.Define the behavioral profile, triangulate internal and external proxy data, and synthesize a bounded range with stated assumptionsCorrect
- c.Rely primarily on executive opinion and industry benchmarks to set a single revenue target
- d.Build a minimum viable product first, then extrapolate user base from early usage metrics
Why? this is the answer
The card emphasizes de-risking bets by defining the job-to-be-done, layering multiple proxies, and bounding the estimate with explicit assumptions and ranges. Option D is a common red flag because insisting on an MVP first avoids pre-coding estimation entirely, while D relies on a single data source without triangulation.
Just read this? Test yourself on what you have been reading.
Read the original → telmarhelixa.com
- #product strategy
- #proxy audiences
- #market sizing
- #data estimation
- #pre-build analysis
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 product strategy — each one lists the topics its interview covers.
See open roles