Metrics question

If you were the PM in charge of the Google Pixel's camera app, how would you measure your success?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests defining success metrics for a hardware-tied software feature, balancing usage frequency with output quality.

Clarify the goal: the camera app should drive both daily usage and genuinely better photos, since photo quality is a key Pixel differentiator and purchase driver.
Set the north star as photos captured per active user per week, since more capture indicates the app feels reliable and fast enough to use.
Add a quality proxy: retake rate, since users retaking or deleting many shots signals the camera isn't performing well in real conditions.
Add downstream signals: photos shared or edited after capture, since sharing implies satisfaction with the result.
Segment by lighting and scene conditions, low light versus daylight, since Pixel's camera differentiation is strongest in challenging conditions like night photography.

Picks retake rate as a clever proxy for actual photo quality, not just capture volume.
Ties the metric to Pixel's known differentiator, computational photography in low light, rather than a generic camera-app metric.
Uses downstream sharing behavior as a genuine satisfaction signal beyond the capture moment itself.

Measuring only photos taken without any signal for whether the photos were actually good.
Ignoring the low-light and night-mode use case, Pixel's most distinctive camera capability.

How would you measure photo quality without manually reviewing every image?
How would you weigh capture volume against actual satisfaction if they disagree?