MangaAssist Interview Pack - Basic

Level: Basic
What this tests: Project understanding, customer framing, component recognition, and clear explanation of the happy path.

Memory Map

graph TD
    A[Business Goal] --> B[Customer Needs]
    B --> C[Use Cases]
    C --> D[Core Architecture]
    D --> E[Safe Response]

    A1[Increase conversion] --> A
    A2[Reduce support cost] --> A
    A3[Improve satisfaction] --> A

    B1[Discovery] --> B
    B2[Product Q&A] --> B
    B3[Order help] --> B

    C1[Recommendation] --> C
    C2[FAQ] --> C
    C3[Tracking] --> C

    D1[Orchestrator] --> D
    D2[Intent Classifier] --> D
    D3[RAG / APIs / Reco] --> D

    E1[Guardrails] --> E
    E2[Formatter] --> E
    E3[Escalation] --> E

Interview Questions

Hiring Manager

Tell me what problem MangaAssist is solving for the JP Manga store.
Who are the main users of this chatbot, and how do their needs differ?
Why is this system more than just a FAQ bot?

Product Manager

Which user journeys would you call the most important for the MVP, and why?
What is the north-star experience this chatbot is trying to create for the customer?

Senior Engineer

Walk me through the high-level architecture layers of MangaAssist from the store page to the final response.
Why does the system have an orchestrator instead of letting the frontend call every backend directly?
What kinds of requests should go to direct APIs, and what kinds should go through RAG or the LLM path?

Support Lead

When should the chatbot answer on its own, and when should it hand off to a human agent?

Data Analyst

What are the first three success metrics you would watch after launch?

Quick Recall Diagram

sequenceDiagram
    participant User
    participant Widget as Chat Widget
    participant Gateway as API Gateway
    participant Orch as Orchestrator
    participant Router as Intent Classifier
    participant Services as APIs/RAG/Reco
    participant Safety as Guardrails

    User->>Widget: Ask question
    Widget->>Gateway: Send message
    Gateway->>Orch: Auth + route
    Orch->>Router: Classify intent
    Router-->>Orch: Intent type
    Orch->>Services: Fetch data or context
    Services-->>Orch: Results
    Orch->>Safety: Validate answer
    Safety-->>Widget: Safe response