Project 10 — Production insurance AI platform
Practice this questionRequirements
- Combine policy RAG, claim status, guided intake, document processing, reviewed communication, staff escalation, and multi-tenant operations.
- Define supported tasks and explicit exclusions.
Architecture
Use section 27; start with one assistant plus controlled routes and add specialists only after evidence of benefit.
Technologies
Next.js, Node, MongoDB or PostgreSQL, chosen vector search, Redis/queue, approved models, LangGraph where needed, optional MCP/Python, eval/tracing platform.
Database design
Canonical customers/policies/claims, versioned documents/chunks, scoped conversations/memory, drafts/approvals, runs/receipts, outbox/audit.
API design
Authenticated conversational APIs, secure uploads/source reads, draft review/submit, durable run status/resume, and staff escalation.
AI design
Evaluated routing, grounded policy explanations, exact status tools, bounded information gathering, and meaningful abstention.
Security
Tenant/object isolation, prompt-injection defense through limited authority, minimized PII, exact approval, safe egress, and deletion propagation.
Evaluation
End-to-end customer tasks plus security, unknown evidence, OCR ambiguity, failure recovery, policy change, stale consent, and concurrent submissions.
Observability
Task success, review/escalation, latency/tokens/cost, source freshness, queue/approval age, tool denials, and operation reconciliation.
Deployment
Staging fixtures, limited rollout, region/data policy, capacity/quota testing, prompt/model/graph versioning, rollback, and operational runbooks.
Interview questions
- “Which steps are agentic?” Answer: interpretation and bounded information gathering.
- “Who decides claim approval?” Answer: authoritative rules and authorized review.
- “How do you prove completion?” Answer: a canonical receipt and audit trail.
Acceptance: Demonstrate a complete customer journey, a safe denied request, no-evidence abstention, a restarted approval workflow, and a duplicate/uncertain submission without duplicate claims. Explain every architecture component and why simpler alternatives were insufficient.