DevSocialUpcoming · 3rd editionAI Agents ConferenceNov 23–27, 2026Live onlineMembers only17days leftRegisterMembers onlyFeatured eBookClaude for AI-Native BuildersDownload nowWrite an article and earn +1,000 SHARP when it is approved.
Write an articleThis guide helps you assess a RAG Developer who can build reliable answers from company documents and databases. Use it to test retrieval quality, grounding, citations, document handling, and permission-aware access.
Step 1 of 3
Describe who you need, in your own words. We turn it into a short brief you can check.
300 characters left
Can prepare documents, create basic chunks and embeddings, connect a vector store, and implement a simple cited question-answer flow with guidance on design choices.
Can own a RAG feature from ingestion through evaluation, including hybrid retrieval, metadata filters, parsing failures, prompt design, and useful quality checks.
Can design reliable RAG systems across varied sources, diagnose retrieval and generation failures, enforce document permissions, and make quality tradeoffs visible to stakeholders.
Can set the RAG architecture and delivery standards, align security and product needs, guide evaluation strategy, and lead a team through complex ingestion and answer-quality problems.
A good answer covers: Covers parsing, normalization, metadata, chunking, deduplication, versioning, failed documents, and a re-indexing strategy. Distinguishes source structure and access rules rather than applying one splitter everywhere.
A good answer covers: Separates retrieval from generation, inspects queries and top-k results, checks chunk boundaries and metadata filters, compares dense and keyword search, and uses labeled queries to isolate the failure.
A good answer covers: Explains that embeddings handle semantic similarity while lexical search helps names, codes, and exact terms. Describes candidate retrieval, re-ranking, latency and cost tradeoffs, and measurable success criteria.
A good answer covers: Applies identity and tenant filters at retrieval time, not just in the prompt, and discusses security trimming, authorization-source consistency, cache isolation, logging, and tests for cross-user leakage.
A good answer covers: Requires claims to be supported by retrieved passages, preserves source identifiers and page or section details, handles conflicting or missing evidence, and prefers abstention over unsupported certainty.
A good answer covers: Builds a representative labeled set with expected sources and answer behavior, measures retrieval recall and answer correctness separately, includes permission and abstention cases, and reviews failures qualitatively.
A good answer covers: Checks parsing and page mapping, chunk overlap and section metadata, retrieval ranking, prompt citation rules, and answer-to-source validation. Proposes regression cases for clause numbers, definitions, and tables.
Given a small set of PDFs, HTML files, and JSON tickets plus sample users and permissions, build a RAG API or CLI. Return an answer, citations, and an abstention when evidence is insufficient. Hand back code, setup notes, and a few evaluation cases.
The role and the skills are enough to start. There is no charge to talk.
Tell us who you needA good answer covers: Compares existing infrastructure, filtering, hybrid search, scale, operations, security, latency, portability, and team expertise. Starts with requirements and tests rather than choosing by brand preference.