Design an internal data-access chatbot

Quick Overview

This question evaluates a candidate's ability to design production-ready ML systems that integrate retrieval-augmented generation, secure access control, tool-based workflows, data privacy, auditability, and low-latency interaction.

Design an internal data-access chatbot

Company: Atlassian

Role: Machine Learning Engineer

Category: ML System Design

Difficulty: medium

Interview Round: Onsite

Design an internal enterprise chatbot for employees. The bot should answer questions and help with tasks by accessing internal data sources (e.g., knowledge bases like Confluence, work tracking like Jira, and possibly other internal tools). Requirements: - Users ask questions in natural language; the bot returns answers with citations when applicable. - Must enforce access control: users can only see content they have permission to view. - Should support both: - Q&A over documents (RAG) - tool/use-case workflows (e.g., “create a Jira ticket”, “summarize open incidents”, “find the runbook for service Z”) - Must be auditable (logs) and safe (avoid leaking sensitive data). - Interactive latency (a few seconds). Describe the high-level architecture, key components, and how you would evaluate and monitor the system in production.

Overview: This question evaluates a candidate's ability to design production-ready ML systems that integrate retrieval-augmented generation, secure access control, tool-based workflows, data privacy, auditability, and low-latency interaction.

|Home/ML System Design/Atlassian
Atlassian logo
Atlassian
Nov 21, 2025
mediumMachine Learning EngineerOnsiteML System Design
6
0

Design an internal enterprise chatbot for employees. The bot should answer questions and help with tasks by accessing internal data sources (e.g., knowledge bases like Confluence, work tracking like Jira, and possibly other internal tools).

Requirements:

  • Users ask questions in natural language; the bot returns answers with citations when applicable.
  • Must enforce access control: users can only see content they have permission to view.
  • Should support both:
    • Q&A over documents (RAG)
    • tool/use-case workflows (e.g., “create a Jira ticket”, “summarize open incidents”, “find the runbook for service Z”)
  • Must be auditable (logs) and safe (avoid leaking sensitive data).
  • Interactive latency (a few seconds).

Describe the high-level architecture, key components, and how you would evaluate and monitor the system in production.

Submit Your Answer to Earn 20XP

Sign in to leave a comment

Loading comments...