Agentic Engineering Roadmap

From software fundamentals to production agent systems. Every node opens its lesson; progress is stored locally.

0 / 77 lessons mastered
  1. 1

    Software Engineering

    prerequisite

    You can design, test, and debug a service with clear interfaces, handle errors deliberately, and reason about state, concurrency, and failure. Agents are ordinary distributed systems with a probabilistic component; the ordinary discipline still applies.

  2. 2

    Python / TypeScript

    prerequisite

    You are fluent in at least one of the two languages the ecosystem is built in: typing (Pydantic / Zod), async, packaging, and reading library source when the docs run out.

  3. 3

    APIs & Async Programming

    prerequisite

    You can call HTTP/JSON APIs with authentication, streaming, timeouts, retries with exponential backoff, and rate limits, and you can run independent calls concurrently without corrupting shared state.

  4. 4

    LLM Fundamentals

    0/2

    You can explain tokens, context windows, temperature, and why model output is probabilistic, and you can place a problem on the ladder from plain code to multi-agent before writing any of it.

  5. 5

    Prompt & Context Engineering

    0/5

    You can construct the exact set of information a model sees on each call, stay inside a token budget, and know why placing a critical fact in the middle of a long prompt reduces the chance it is used.

  6. 6

    Structured Outputs

    0/2

    You can force a model to return schema-conformant JSON, validate it at the boundary, and handle the case where validation fails instead of trusting the shape of the text.

  7. 7

    Tool Calling

    0/7

    You can define tool schemas the model selects correctly, validate arguments, handle errors, timeouts, and retries, make side effects idempotent, and grant each tool the minimum permissions it needs.

  8. 8

    RAG

    0/8

    You can build the full retrieval pipeline (chunking, embeddings, storage, hybrid retrieval, reranking, grounding with citations) and measure retrieval quality separately from answer quality.

  9. 9

    Agent Loops

    0/5

    You can implement the observe-reason-act loop without a framework, choose between direct execution, plan-then-execute, and ReAct, and know when planning only adds latency and cost.

  10. 10

    State & Memory

    0/3

    You can separate context, short-term, and long-term memory, decide what deserves persisting, and explain why storing more makes agents worse rather than better.

  11. 11

    MCP

    0/4

    You can build and consume an MCP server, explain tools, resources, and prompts, handle the connection lifecycle and auth, and argue when a direct integration or plain function calling is the better choice.

  12. 12

    Workflow Orchestration

    0/4

    You can model a multi-step process as an explicit state graph with checkpoints and routing, and can articulate why a deterministic workflow beats an open-ended agent for most business processes.

  13. 13

    Multi-Agent Systems

    0/8

    You can choose between supervisor, pipeline, hierarchical, and swarm topologies, design the messages agents exchange, and recognise the many cases where a single agent with better tools is the right answer.

  14. 14

    Evaluation

    0/6

    You can build a golden dataset, pick metrics that match the failure you care about, combine deterministic evaluators with LLM judges, and run regression evals before every prompt or model change.

  15. 15

    Observability

    0/3

    You can trace every LLM call, tool call, and state change as spans, read a trace to find the step where a run went wrong, and alert on token, cost, latency, and error rates.

  16. 16

    Guardrails & Security

    0/7

    You treat all retrieved and tool-returned content as untrusted data, scope tool permissions to the task, keep secrets out of the context, and put guardrails on both inputs and outputs.

  17. 17

    Human-in-the-Loop

    0/4

    You can classify actions by risk, insert approval gates where reversibility is low, and design escalation with confidence thresholds so humans review the cases that matter instead of every case.

  18. 18

    Reliability

    0/4

    You can enumerate the ways an agent run fails (loops, overflow, provider outage, drifting arguments) and have a named mitigation for each: budgets, termination criteria, fallbacks, caching, routing.

  19. 19

    Production Agent Systems

    0/5

    You can take an agent from demo to production: fallback chains, caching and routing for cost, metrics and alerts, real business-process automation, and a defensible choice of framework or none at all.