Metrics question
How would you measure whether Lindy agents reliably complete their tasks?
- Lindy
- Metrics
- Medium
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests metrics design for evaluating whether autonomous agents actually complete tasks correctly, not just run without crashing.
How to approach it
- Define task completion precisely: the agent achieved the user's actual intended outcome, not just executed without an error.
- Build the core metric: task success rate, where success is verified against a clear definition per task type, like a correctly sent email versus a technically sent but wrong one.
- Separate technical failure from logical failure: an agent that errors out is different from one that runs cleanly but does the wrong thing, and both need tracking.
- Add a human correction signal: rate at which users edit, undo, or manually redo an agent's output, which reveals silent failures completion rate alone would miss.
- Segment by task type and integration, since reliability on a simple calendar check likely differs from reliability on a complex multi step CRM update.
- Confirm with the interviewer whether reliability should be measured per agent, per task type, or as one platform wide number.
What a strong answer includes
- Distinguishes technical failure from logical failure, since an agent that runs without error but produces the wrong output is a more dangerous and harder to detect failure mode.
- Uses human correction or undo rate as a proxy for silent failures, catching cases a simple completion flag would miss entirely.
- Segments reliability by task type and integration complexity, avoiding a misleading single blended number across very different task difficulties.
- Proposes a sampled human audit of a subset of completed tasks, since fully automated verification cannot judge every kind of output correctness.
Common mistakes
- Measuring only whether the agent ran without a technical error, missing the more common failure of a wrong but well executed action.
- Reporting one blended reliability number across very different task types and difficulties.
- No signal for silent failures, where the agent appears successful but produced output the user had to quietly fix.
Likely follow-up questions
- How would you verify task correctness for tasks with no clear right answer?
- What would you do if reliability was high for simple tasks but low for complex multi step ones?
- How would you use this reliability data to decide which agents get more autonomy?
More metrics questions
- What metrics would you track for Lindy's agent activation and retention?Lindy · Metrics · Medium
- How would you measure the success of Facebook Likes?Meta · Metrics · Medium
- Walmart's order return rate is increasing. As a product manager, what things would you look into to isolate the problem?Amazon · Metrics · Medium
- What metrics would you track if you were PM of Facebook Birthdays?Metrics · Medium
- How do you define success for Yelp reviews?Google · Metrics · Medium
- Utilization went down by 45% on app XYZ in Italy for the month of August. Give a reason why and draft a plan to fix it.Spotify · Metrics · Medium
More questions from Lindy
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 2: Data fluency: SQL, logs, and reading the truth yourself
- Chapter 14: Get the job: the AI PM interview loop