Measure the Health and Effectiveness of an Add-Question Button
Company: Quora
Role: Data Scientist
Category: Analytics & Experimentation
Difficulty: medium
Interview Round: Technical Screen
# Measure the Health and Effectiveness of an Add-Question Button
A question-and-answer platform wants reporting metrics for the health and effectiveness of its “Add question” button. How would you design those metrics? Explain what the button is intended to accomplish, how you would instrument the path from seeing it to publishing a question, and how you would distinguish a technically healthy interface from one that helps users create useful questions.
No event schema or existing target is provided. Propose definitions with clear populations, denominators and time windows, and explain which details you would confirm with the product team. Consider users who click but do not publish and users who publish a question that receives little useful response. Avoid selecting a metric merely because it is easy to count.
### What a Strong Answer Covers
- Exposure, click, creation-start and publish measurements with consistent units.
- Reliability and friction indicators that help locate failures in the creation path.
- Question-quality and downstream-response measures, with time to observe outcomes.
- Reporting cuts and guardrails that prevent increased clicks or volume from concealing worse user outcomes.
### Follow-up Questions
- What could cause button click-through to rise while successful question creation falls?
- How would you interpret more published questions but fewer useful answers per question?
Overview: Design reporting metrics for an Add-question button from exposure and creation reliability through useful answers and content quality.
Measure the Health and Effectiveness of an Add-Question Button
A question-and-answer platform wants reporting metrics for the health and effectiveness of its “Add question” button. How would you design those metrics? Explain what the button is intended to accomplish, how you would instrument the path from seeing it to publishing a question, and how you would distinguish a technically healthy interface from one that helps users create useful questions.
No event schema or existing target is provided. Propose definitions with clear populations, denominators and time windows, and explain which details you would confirm with the product team. Consider users who click but do not publish and users who publish a question that receives little useful response. Avoid selecting a metric merely because it is easy to count.
What a Strong Answer Covers Guidance
Exposure, click, creation-start and publish measurements with consistent units.
Reliability and friction indicators that help locate failures in the creation path.
Question-quality and downstream-response measures, with time to observe outcomes.
Reporting cuts and guardrails that prevent increased clicks or volume from concealing worse user outcomes.
Follow-up Questions Guidance
What could cause button click-through to rise while successful question creation falls?
How would you interpret more published questions but fewer useful answers per question?