AI / CrewAI Interview Questions
Explain the lifecycle of a Task's execution from assignment to TaskOutput?
flowchart LR
A[Task Defined: description, expected_output, agent/tools] --> B[Assigned to Agent: explicit or manager-delegated]
B --> C[Agent Executes using Tools]
C --> D[Result Produced]
D --> E[Wrapped in TaskOutput: raw/JSON/Pydantic]
E --> F[Passed as Context to Dependent Tasks]
- Definition: a Task is defined with a description, expected output, and optionally a specific agent and tools
- Assignment: the task is either directly assigned to a named agent, or, under the Hierarchical process, dynamically assigned by the manager based on role and availability
- Execution: the assigned agent works through the task, calling whatever tools it needs along the way
- Output: the result is wrapped in a TaskOutput object, exposing it as raw text, and optionally as JSON or a Pydantic model if the task specifies a structured output format
- Propagation: that TaskOutput can then be passed as context into any later task that depends on it
This structured lifecycle is what lets CrewAI treat a chain of tasks as a genuine pipeline rather than a series of disconnected agent calls that happen to run one after another.
What is the very first step in a Task's lifecycle?
What can happen to a Task's TaskOutput after it's produced?
More Related questions...
