How the interviewer opens it
“Design an AI receptionist platform for businesses. Customers can call or chat to ask questions and request help. The receptionist must follow each business's rules and let a person control the conversation.”
The prompt is vague on purpose. The first minutes are for you. Reduce the prompt to the core features and agree on the numbers before you draw.
What to clarify first
- Channels and scale
- Session shape
- Read and write mix
- Knowledge and permitted actions
- Latency
- Availability and correctness
- Business updates
- Transfer to a person
- Durability and privacy
- External services and exclusions
The interviewer has the answers. In a SysRound round, Alex gives these answers, as a real interviewer does.
Scope of a strong answer
Core requirements
- Support inbound phone calls and web chat
- Answer questions from business-approved knowledge
- Create and cancel appointments within business permissions
- Transfer a live conversation and its context to a person
Usually out of scope
- Train speech or language models
- Build a phone network or calendar service
- Process payments
- Make outbound calls
What interviewers ask about
- The live conversation
- Speech crosses several services before the customer hears a reply. Interruptions can leave old speech and actions in progress.
- Business answers
- The receptionist must use each business's current facts. A fluent answer can still contain false facts or another business's private data.
- Business actions
- The model can misunderstand a request. External calendar calls can also succeed after a timeout, which makes retries dangerous.
- Transfer to a person
- The AI and the person share one live channel. A transfer must stop old AI work without hiding an action already in progress.
Common mistakes
- Treats the receptionist as a chatbot and ignores live audio delays and interruptions.
- Uses a model prompt as the only control for facts, permissions, and private data.
- Confirms an appointment change before the calendar confirms it.
- Retries uncertain actions without checking whether the calendar already completed them.
- Transfers context to a person without transferring control of the conversation.
- Creates many independent services before defining session ownership and action state.
The bar by level
- Senior (L5/E5)
- Defines latency budgets, interruption behavior, tenant boundaries, and permission checks. Handles uncertain calendar results and gives one owner control during transfer.
- Staff (L6+/E6+)
- Defines invariants across session control, output, and external actions. Explains failure recovery, provider limits, and safe regional expansion. Distinguishes enforceable guarantees from model quality.