179 questions
No questions match those filters.
Users report the assistant gets 'how many' and 'total' questions wrong, but retrieval recall@20 is 0.94. What do you change?
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansThe core failure stems from evaluating aggregation questions (‘how many’, ‘total’) with standard top-k retrieval metrics like recall@20. Recall@20 measures whether relevant passages appear within 20 retrieved items. However, an aggregation query requires full coverage over all M items in a set (e.g., M = 3,200). In such cases, the RAG pipeline’s coverage ceiling is capped at 20/3,200 (less than 1%), rendering the generator incapable of producing correct totals regardless of how high recall@20 scores.
To resolve this, route aggregate and count queries away from standard unstructured top-k passage retrieval and into structured execution paths, such as a SQL tool or database query interface that computes over the entire dataset. If no SQL layer or database tool exists, the fallback strategy is to use metadata-filtered counting where supported by the schema, or explicitly abstain from answering when full coverage cannot be guaranteed.