Agentic AI — Quick Reference

Framework Comparison

Dimension Raw SDK (Anthropic) LangGraph CrewAI
Control Maximum High Medium
Configuration effort High Medium Low
Typed state Manual TypedDict built-in Implicit (task context)
Checkpointing Manual Built-in (PostgresSaver) Limited
HITL Manual interrupt_before Not native
Best for Custom topology; learning Production stateful workflows Role-based team patterns
Choose when No framework overhead needed Complex routing + HITL + persistence Rapid role-based prototyping

Common Interview Questions

  1. When would you choose an agent over a chain? — When the task requires dynamic tool selection based on results; when control flow cannot be determined in advance.
  1. What is the "agent paradox"? — Complex tasks benefit most from agents, but are also hardest to evaluate. Always define evaluation before deployment.
  1. How does LangGraph's checkpointing enable HITL?interrupt_before pauses execution and returns control; PostgresSaver persists state durably; the caller resumes by invoking graph.invoke() with the human decision in state.
  1. Why enforce tool authorization at the MCP server rather than relying on the agent? — The LLM is not a reliable security boundary — it can be manipulated by prompt injection. The MCP server is code; it enforces authorization independent of the model's reasoning.
  1. What are the four HITL trigger categories? — Confidence-based (agent uncertainty), risk-based (action side-effect level), policy-based (business rule mandates review regardless of confidence), anomaly-based (agent detects unexpected state).
  1. What is the M×N problem MCP solves? — Without a standard protocol, M AI applications × N backend systems = M×N integrations. With MCP: M clients + N servers; each addition requires one implementation, not M or N.