The production-grade, evals-first, career-aware roadmap for GenAI engineers in 2026.
From "I can call the OpenAI API" to "I shipped a multi-agent system that runs in production with SLOs and an evals harness."
A rigorously-sourced, file-per-topic, evals-first roadmap for becoming a production GenAI engineer. Every factual claim is cited and dated in LAST_VERIFIED.md. Every topic follows a consistent template. Every project ships with code, tests, and an evals harness.
This is not a link dump. This is not a single 600-line README. This is not LangChain-only. This is the roadmap a principal AI engineer would recommend without caveats.
- Not a tutorial. Topics assume you can read Python and understand HTTP.
- Not exhaustive. We picked one lane — production GenAI engineering — and go deep.
- Not a model leaderboard. We cover architectures and patterns that survive model releases.
| Rung | Topic | Folder | Est. time |
|---|---|---|---|
| 0 | Foundations | foundations/ |
1 week |
| 1 | Applied LLM Calling | llm-calling/ |
1 week |
| 2 | Context Engineering | context-engineering/ |
2 weeks |
| 3 | Modern RAG | rag/ |
3 weeks |
| 4 | Tools & MCP | tools-and-mcp/ |
2 weeks |
| 5 | Single-Agent Engineering | agents/ |
2 weeks |
| 6 | Multi-Agent Orchestration | multi-agent/ |
3 weeks |
| 7 | Evals & Test-Driven LLM Dev | evals/ |
2 weeks |
| 8 | Production & Economics | production/ |
2 weeks |
| 9 | Fine-tuning & Self-Hosting | fine-tuning-and-self-hosting/ |
2 weeks |
| 10 | Safety, Alignment & Red-Teaming | safety/ |
1 week |
| 11 | Real-Time & Voice | realtime-voice/ |
1 week |
| Your background | Recommended path |
|---|---|
| Backend engineer | docs/learning-paths/from-backend-engineer.md |
| Frontend engineer | docs/learning-paths/from-frontend-engineer.md |
| Data engineer | docs/learning-paths/from-data-engineer.md |
| Data scientist | docs/learning-paths/from-data-scientist.md |
| ML engineer | docs/learning-paths/from-ml-engineer.md |
| Starting from zero | docs/learning-paths/from-zero.md |
Career and industry context — separate from the technical curriculum.
field-guide/01-the-ai-engineer-role.mdfield-guide/02-skills-that-get-you-hired.mdfield-guide/03-interview-loop-anatomy.mdfield-guide/04-portfolio-strategy.mdfield-guide/05-salary-bands.mdfield-guide/06-job-market-trends.md
15 portfolio-grade builds, each with README.md, src/, tests/, evals/, DEPLOYMENT.md. See projects/.
When you hit a fork in the road, start here:
docs/decision-guides/choosing-an-agent-sdk.mddocs/decision-guides/choosing-a-vector-db.mddocs/decision-guides/rag-vs-long-context.mddocs/decision-guides/fine-tune-or-not.mddocs/decision-guides/self-host-vs-api.mddocs/decision-guides/open-weight-model-selection.md
awesome/ — papers, books, courses, blogs, tools, communities. One-line reviews, not bare links.
- Read
LAST_VERIFIED.mdto see when every factual claim was last checked. - Pick a learning path based on your background.
- Work the rungs in order. Each rung links to the next.
- Build at least 3 projects as you go. Code beats reading.
- Run the evals that ship with each project. Internalize the evals-first mindset.
See CONTRIBUTING.md. The short version: every factual claim must be sourced and dated, every file must follow the topic template, every project must ship with tests.
MIT — see LICENSE.
alexeygrigorev/ai-engineering-field-guidefor the field-guide playbook and the "data, not filler" philosophy.- Every practitioner who has published a postmortem, evals harness, or agent architecture in public.
If this roadmap helps you, star it. Stars keep the project maintained.