When I interviewed for a data analyst position at a known startup, I was asked to define a target KPI for a controlled pseudo-A/B experiment, and I suggested total revenue. The interviewer replied "that's a dumb answer because revenue can be gamed; you should have said # of sales."
I was too taken aback to follow up asking why # of sales can't be gamed too.
Number of sales (or customers) is a vanity metric favored by startups looking to entice investment. Revenue is a metric useful for measuring actual business health.
Any chance the interviewer was overly exit eager ?
Why is that credit? Good interview questions don't have a right or wrong answer, they have a right or wrong process of coming up with an answer. Especially for a question like "Pick a metric," almost any relevant metric is defensible and has tradeoffs, and the question should be about how the interviewee analyzes engineering tradeoffs, gathers requirements, defends their initial proposal, and is open to counterarguments.
(If there's a correct answer, you can just give them a quiz. If there's a Googleable correct answer, you can just employ them and give them Google.)
I was too taken aback to follow up asking why # of sales can't be gamed too.