Validate needs and benchmark competitor adoption

Before any build work, put together a research plan that checks user demand and compares how competitors have adopted group calling.

Part A (survey): Write 8–10 specific survey questions, each with exact wording and response options, to surface use cases, preferred group size, willingness to invite others, tolerable latency, and obstacles; include at least two randomized vignettes (for example, different UI/latency trade-offs). Define the sampling frame, how participants will be recruited, and the method for connecting their answers to behavioral telemetry without compromising privacy.

Part B (competitors): With no internal data available, produce a U.S. adoption estimate within ±20% relative error. Identify concrete signals and how to gather them (e.g., search trends, app store review mining, third-party mobile panels, web telemetry, WebRTC STUN/TURN traffic proxies, public earnings remarks), then describe a triangulation and calibration model that converts those signals into adoption estimates. State assumptions, bias risks, and validation steps (e.g., back-testing on known launches).

Overview: This question tests a candidate's ability in research design and survey methodology, validating user needs, linking survey and telemetry data in a privacy-preserving way, and estimating competitor adoption through triangulation of external signals.