How do you evaluate embedding quality for RAG?

Embedding quality in RAG should be evaluated by asking a practical question:

Does this embedding model retrieve the right chunks for real user queries?

Looking at embedding dimension or individual similarity scores is not enough.

1. Build a labeled evaluation set

Create realistic queries and identify which document chunks should be considered relevant.

Example:

Query: "How many days can an enterprise customer request a refund?"

Relevant chunk: "Enterprise customers may request a refund within 45 days."

This gives you a known target for retrieval evaluation.

2. Measure retrieval quality

Run the queries through the embedding model and vector search, then measure whether relevant chunks appear near the top.

Useful metrics include:

• Recall@K
• Precision@K
• MRR
• NDCG
• Hit Rate

For RAG, Recall@K is especially important because if the correct evidence is never retrieved, the generator cannot use it.

3. Test difficult semantic cases

A good embedding model should handle queries whose wording differs from the document.

Example:

Query: "Can unused vacation days move to next year?"

Document: "Employees may carry forward up to 10 days of unused annual leave."

The words are different, but the meaning is similar.

This is where embedding quality matters.

4. Include hard negatives

Do not evaluate only obvious examples.

Include documents that are semantically close but wrong.

Example:

Query: "Enterprise refund period"

Relevant: "Enterprise customers: 45 days"

Hard negative: "Standard customers: 30 days"

A good embedding model should rank the enterprise policy higher.

5. Compare models under the same conditions

When comparing embedding models, keep other variables fixed:

• Same documents
• Same chunking
• Same queries
• Same Top-K
• Same vector index settings
• Same similarity metric when appropriate

Otherwise, you may incorrectly attribute improvements to the embedding model.

6. Evaluate your actual domain

A model that performs well on general benchmarks may still perform poorly on:

• Medical terminology
• Legal documents
• Source code
• Product identifiers
• Internal abbreviations
• Multilingual content

So benchmark results are useful for shortlisting, but your own retrieval dataset is more important.

7. Check downstream RAG quality too

Better retrieval metrics should ideally improve the final answer.

After comparing embedding models, also measure:

• Final answer correctness
• Groundedness
• Citation accuracy
• Latency
• Embedding cost
• Storage requirements

A larger or more expensive embedding model is only worthwhile if it produces meaningful retrieval or answer-quality gains.

Interview takeaway

Evaluate embedding quality through retrieval performance on a representative labeled query-document dataset. Compare models using metrics such as Recall@K, MRR, and NDCG, include paraphrases and hard negatives, keep the rest of the retrieval pipeline fixed, and validate the results on your own domain. The best embedding model is the one that retrieves the right evidence reliably at an acceptable latency and cost.