Dashboard
0%
1
Curious builder0 XP earned · 300 to level 2
0 daysFinish a lesson to begin
Badge collection0 of 6 unlocked
51 small wins to finish your pathNext question →

Q39HardSystem design

Design an internal enterprise AI platform that 50 product teams use to build LLM features.

30-second answerSay your answer out loud first, then reveal.
Three team apps call a platform SDK, which routes to an LLM gateway, retrieval, guardrails, a tool/MCP registry and a prompt registry, with tracing and evals alongside, and the gateway and fine-tune pipeline sit on API providers plus a self-hosted pool.

Platform principles

  1. Golden paths, not mandates: templates for common patterns (RAG chatbot, extraction workflow, agent with tools) that come with logging, evals and guardrails by default.
  2. Central governance:
    • Approved model catalogue with data classification rules (which data can go to which provider).
    • Per-team budgets and chargeback.
    • Security review for agents with write access to systems.
  3. Shared retrieval: connectors to enterprise sources with permission-aware indexes, so teams don't each copy sensitive data into their own vector stores.
  4. Evaluation as a service: dataset management, LLM-judge templates, CI integration, dashboards per app.
  5. Observability: standard tracing (OpenTelemetry GenAI conventions), cost per feature, incident response.
  6. Model lifecycle: testing new models across all teams' eval suites before switching defaults; deprecation management.
  7. Developer experience: self-service API keys via SSO, sandbox environments, documentation, an internal community of practice.

Success metrics: time-to-first-production feature for a new team, number of apps on the platform, platform-level cost savings (caching, routing), incidents avoided, eval coverage.

This is what real progress feels like.