This was one question but it had like eight sub-questions hiding inside it.
Start by clarifying requirements and constraints (data sources, latency, accuracy, scale), then walk through the end-to-end pipeline: query understanding, routing, retrieval (vector, keyword, text-to-SQL), RAG grounding, LLM selection, and evaluation. Emphasize trade-offs at each stage and how you'd iterate with feedback loops and A/B testing.
Pro tip: Anchor your design in concrete metrics (e.g., faithfulness, answer correctness, latency) and explicitly discuss how you'd handle failure modes like hallucination or retrieval misses. Show that you think about the system holistically, not just the model.
Ask about data sources, query types, latency SLAs, scale, and accuracy targets. Define success metrics and constraints to guide design decisions.
Explain how to parse and classify queries (intent, entity extraction) and route them to appropriate retrieval methods (structured vs. unstructured).
Detail vector search for semantic retrieval, keyword search for exact matches, and text-to-SQL for structured data. Discuss hybrid approaches and re-ranking.
Describe how to ground LLM responses with retrieved evidence, choose an LLM based on cost, latency, and quality, and handle context window limits.
Define offline and online metrics (faithfulness, answer correctness, latency), set up A/B testing, and incorporate user feedback for continuous improvement.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.