Selected engineering work

Retrieval engineering

GenAI Research Assistant

A local research Q&A application with reproducible FAISS Flat, HNSW and Annoy retrieval benchmarks.

PythonLangGraph/LangChainSentence-TransformersChromaDBFAISSAnnoyStreamlitpandasMatplotlibRAGAS
Choose your depth
Architecture, choices & results

Compare retrieval quality, throughput, build time and memory under a common research workload.

Follow the flow from input to evaluated output. Select a stage to inspect its role.

PDF ingestion — PDF ingestion

StreamlitUnified VectorStoreFAISS / HNSW / AnnoyRAGAS
Engineering decision

Compare retrieval backends explicitly

Problem
Make quality, speed and resource trade-offs inspectable.
Approach
Use a unified VectorStore interface for ANN and exact-search comparisons.
Trade-off / scope
Local results require benchmark context; no production service performance is implied.
direct evidenceRetrieval benchmark

7,641 chunks and 76 queries; recall, throughput, build time and reported memory overhead.

Documented result7,641 chunks · 76 queriesANN / exact retrieval benchmark (local research; completed): Unified VectorStore comparisons across ANN and exact/Flat approaches; RAGAS end-to-end quality evaluation is documented without supplied numerical scores. arXiv document corpus: 7,641 chunks, 76 queries. Document chunks: 7,641. Benchmark corpus size. Benchmark queries: 76. Number of retrieval benchmark queries. HNSW recall: ≥0.998. Local HNSW retrieval benchmark; recall cutoff and aggregation not supplied. HNSW retrieval throughput: ~1,439 QPS. Local retrieval queries per second, not application request latency or production throughput. FAISS-Flat index build time: 0.002 s. Local index construction time; not request latency. FAISS-Flat reported memory overhead: 0.09 MB. Reported local benchmark memory overhead; measurement definition not supplied. Local research application and retrieval benchmark, not a production service benchmark. QPS and index build time are not application request latency. Benchmark hardware, query distribution, recall cutoff and full per-backend outputs are not supplied.

ANN / exact retrieval benchmark: completed. arXiv document corpus: 7,641 chunks, 76 queries.

A documented safety and scope boundary.

Local research application and retrieval benchmark, not a production service benchmark. QPS and index build time are not application request latency. Benchmark hardware, query distribution, recall cutoff and full per-backend outputs are not supplied.

Documented services

Streamlit · Unified VectorStore · FAISS / HNSW / Annoy · RAGAS

Context limited to Retrieval Laboratory

Challenge this project.

Ask about the decisions, evaluation or boundaries behind the work.

Deterministic answers from documented portfolio evidence · project-scoped

A claim is only the beginning

Where did I use it?
What did I build?
How did I measure it?

Follow the projects, decisions and evaluation behind each answer. Every important claim has somewhere to go.

Direct · measured implementation Supporting · documented use Related · adjacent experience
An inspectable claimPG / 001
CAPABILITYRetrieval-augmented generation
IMPLEMENTATION

BM25+semantic retrieval

Trace the evaluation behind the number