Top 5 Ingestion Interview Questions
Browse 5 real-world technical and behavioral interview questions about Ingestion. Review scenarios, edge cases, and architectural best practices.
An upstream team renames a field in the events you consume and nobody tells you. What should your pipeline have done?
Validate every record against a declared schema at the ingestion boundary, quarantine what fails instead of dropping it, treat additive changes as safe and renames as breaking, and alert on a field that has gone all-null rather than waiting for a dashboard to look wrong.
How do you choose a chunking strategy for a document corpus?
Chunk boundaries decide what can ever be retrieved, so you derive them from the questions the corpus must answer and from the document's own structure, then confirm the choice with retrieval recall on a gold set rather than by eye.
Your corpus is scanned PDFs, spreadsheets and slide decks. How do you ingest it?
Route each format to a parser that respects its structure, treat OCR output as text with a confidence score rather than as truth, convert tables into rows that carry their headers, and record a section path and stable anchor per chunk so every retrieved passage can be cited back to a place in the original.
A supplier sends you a feed of ten thousand products. How many of them are already in your catalogue?
You cannot know without matching, and matching is the work: suppliers send their own identifiers, spell the same manufacturer three ways, and describe attributes in units you do not use. Treat ingestion as a matching problem with a confidence threshold and a review queue, not as an import.
What metadata do you store alongside each chunk, and what is each field for?
Each chunk needs its source document and version, its section path, an anchor precise enough to open, effective and ingestion dates, and the permission set that governed the original — because filtering, citation, freshness and access control are all served from metadata rather than from the vector.