A Glean-signature design question where deletions, not ingestion, are the trap. Covers the connector framework, change detection per source class, tombstones, and the freshness SLO customers actually sign.
more free answers with an account · no card
← RAG & Agent System Design / 18
mediumGleanDatabricksMicrosoft
Ingest 40 enterprise sources (SharePoint, Confluence, Jira, drives) with incremental sync and deletion handling
A Glean-signature design question where deletions, not ingestion, are the trap. Covers the connector framework, change detection per source class, tombstones, and the freshness SLO customers actually sign.
Updated Sep 2026 · Grounded in real Forward Deployed Engineer interview loops and written to a senior-engineer editorial bar.
UP NEXT ON YOUR JOURNEY
Learners often go here nextDesign the full eval harness for an LLM product: offline goldens, LLM-judge, online A/B, CI gatesNext in this trackDesign RAG over 10M documents with per-user permissions: a user must never see data they can't accessNext in this trackGive an agent memory across sessions without blowing up the context window or leaking between users
DISCUSSION · 0
No comments yet — be the first to share your approach.