Interview Q11: Why chunk documents for RAG?
Chunking creates retrievable units small enough to rank and fit into context while preserving useful meaning. Chunk size and overlap should be tuned with evaluations.
Interview structure: define the concept, explain the design trade-off, and give one production example.
Note
Interview approach: explain the concept, show the control boundary, and discuss the failure mode.
Minimal illustration
// Example: validate a boundary before doing work.
function requireNonEmptyString(value) {
if (typeof value !== "string" || value.trim() === "") {
throw new Error("Expected a non-empty string");
}
return value;
}💡 The snippet demonstrates a general boundary-validation principle. Adapt the example to the concept and explain how the application enforces the rule at runtime.
Key Takeaways
- State the concept clearly.
- Mention one limitation or failure mode.
- Connect it to a production decision.
Knowledge Check
What is a common problem with chunks that are too small?