Metrics question

What is your favorite game? What feature would you create for this game? What metrics would you look at to determine if this is worthwhile, before spending a single engineering dollar?

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

Metrics discipline before building: defining what success looks like for a feature idea prior to any engineering investment.

Pick a specific, well known game rather than a vague genre answer.
Propose one concrete feature for that game, tied to a real gap you have personally noticed in play.
State the hypothesis: what player behavior or business outcome this feature is meant to change, such as session frequency or in-app purchase rate.
Define a small, cheap test before full investment, such as a prototype or a limited beta with a control group.
Name the metrics that would justify full investment: for example, lift in day 7 retention or increase in average revenue per daily active user versus a holdout group.
Set a guardrail metric, such as session length not dropping, to catch unintended side effects.

Ties the feature idea to a specific, personally observed gap in the game rather than a generic 'more content' answer.
Proposes a controlled test, a limited beta with a holdout group, before committing full engineering resources.
Names both a growth metric (retention or revenue lift) and a guardrail (session length), showing balanced thinking before spending budget.

Proposing a feature without any hypothesis for what business metric it should move.
Jumping straight to full build without describing a cheaper validation step first.

What would make you kill this feature idea before building it further?
How would you size the potential revenue impact before pitching it to leadership?